You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/04/11 14:45:49 UTC
[jira] Updated: (MNG-251) maven-archiver should be able to include the snapshot version/build number
[ http://jira.codehaus.org/browse/MNG-251?page=history ]
Brett Porter updated MNG-251:
-----------------------------
Fix Version: (was: 2.0-alpha-2)
2.0-alpha-3
> maven-archiver should be able to include the snapshot version/build number
> --------------------------------------------------------------------------
>
> Key: MNG-251
> URL: http://jira.codehaus.org/browse/MNG-251
> Project: m2
> Type: New Feature
> Reporter: Brett Porter
> Fix For: 2.0-alpha-3
>
>
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org