[
https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963598#comment-17963598
]
ASF GitHub Bot commented on SCM-914:
------------------------------------
jira-importer opened a new issue, #1134:
URL: https://github.com/apache/maven-scm/issues/1134
**[Tobias
Gruetzmacher](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tgr)**
opened
**[SCM-914](https://issues.apache.org/jira/browse/SCM-914?redirect=false)** and
commented
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:**
-
[DOXIASITETOOLS-329](https://issues.apache.org/jira/browse/DOXIASITETOOLS-329)
Expose SCM lastModification date in addition to publishDate in Velocity Context
**Remote Links:**
- [GitHub Pull Request #193
](https://github.com/apache/maven-scm/pull/193)
> InfoItem.lastChangedDate is leaky abstraction
> ---------------------------------------------
>
> Key: SCM-914
> URL: https://issues.apache.org/jira/browse/SCM-914
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-api
> Reporter: Tobias Gruetzmacher
> Assignee: Konrad Windszus
> Priority: Minor
> Fix For: 2.1.0
>
>
> 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)
