Tobias Gruetzmacher created SCM-914:
---------------------------------------
Summary: 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
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
(v7.6.3#76005)
