[jira] [Commented] (SCM-914) InfoItem.lastChangedDate is leaky abstraction

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567605#comment-17567605 ] 

Michael Osipov commented on SCM-914:
------------------------------------

Still interested in pursuing this?

> InfoItem.lastChangedDate is leaky abstraction
> ---------------------------------------------
>
>                 Key: SCM-914
>                 URL: https://issues.apache.org/jira/browse/SCM-914
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-api
>            Reporter: Tobias Gruetzmacher
>            Priority: Minor
>
> 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:
>  # Fix InfoItem, so that lastChangedDate is a Date
>  # Fix the current providers filling this field (svnexe and svnjava AFAICS - aside: why is svnjava not part of the maven-scm repository?)
>  # Implement this feature for at least gitexe (and maybe jgit) so I can use it for my usecase
> Ideas, comments?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)