[SCM-914] InfoItem.lastChangedDate is leaky abstraction

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Component/s: maven-scm-api
• Assignee: Konrad Windszus
• Reporter: Tobias Gruetzmacher
• Created: 10/Dec/18 15:47
• Updated: 14/Apr/24 09:32
• Resolved: 08/Apr/24 08:06

Description

I was looking into implementing https://github.com/mojohaus/buildnumber-maven-plugin/pull/16 in a sane way, but had to conclude that InfoItem.lastChangedDate is unfortunately just a string and not a Data, so will leak the console output of different providers to the user.

Does anybody see a sane way to fix this API and create a sane abstraction for different SCMs? If yes, I would try to go ahead with the following tasks:

1. Fix InfoItem, so that lastChangedDate is a Date
2. Fix the current providers filling this field (svnexe and svnjava AFAICS - aside: why is svnjava not part of the maven-scm repository?)
3. Implement this feature for at least gitexe (and maybe jgit) so I can use it for my usecase

Ideas, comments?

Issue Links

• is related to: DOXIASITETOOLS-329 Expose lastModification date in addition to publishDate in Velocity Context
• links to: GitHub Pull Request #193