[
http://jira.codehaus.org/browse/MOJO-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MOJO-1489.
------------------------------
Resolution: Duplicate
Fix Version/s: buildnumber-maven-plugin-1.0-beta-5
Assignee: Olivier Lamy
> Add git hash as a parameter to the maven build
> ----------------------------------------------
>
> Key: MOJO-1489
> URL: http://jira.codehaus.org/browse/MOJO-1489
> Project: Mojo
> Issue Type: Improvement
> Components: buildnumber
> Affects Versions: buildnumber-maven-plugin-1.0-beta-4
> Reporter: Ben Hood
> Assignee: Olivier Lamy
> Fix For: buildnumber-maven-plugin-1.0-beta-5
>
> Attachments: git-hash-patch.diff
>
>
> This is a patch to the buildnumber plugin.
> The motivation is to be able to put the git hash into the name of the
> build artifact.
> I considered genericizing the create goal to handle git as well as
> svn, but realized that it would may require some refactoring to do so,
> and didn't know whether that would have been considered.
> Having attempted to follow the Maven SCM paradigm, I began to question
> the its design.
> Moreover, the git SCM provider for some reason actually throws away
> the commit hash when it traverses the repository, so that was
> essentially a KO criterion.
> Anyway, I've bumped the plugin version up to 1.0-beta-5 to be able to
> use it from other Maven projects.
> Hope this is of some use to somebody.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
