[ http://jira.codehaus.org/browse/MNG-775?page=comments#action_44997 ]
John Casey commented on MNG-775: -------------------------------- If we're to have a single snapshot build-id for artifacts and attachments, then it will have to be generated ahead of the install/deploy process, which means it's a no-brainer to also include in the artifacts themselves, somewhere under META-INF possibly. > Reissue of MNG-251: maven-archiver should be able to include the snapshot > version/build number > ---------------------------------------------------------------------------------------------- > > Key: MNG-775 > URL: http://jira.codehaus.org/browse/MNG-775 > Project: Maven 2 > Type: New Feature > Components: maven-archiver > Versions: 2.0-alpha-3 > Reporter: John Casey > Assignee: John Casey > Fix For: 2.0-beta-1 > > > From MNG-251: > 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
