Just in case I can add something helpful, I would like to cite this maven requirements document (don't know if its too old to be still of any use...) :
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Res olution (see the "Reproducibility" Chapter) Citing : ... This means that the presence of release-pom.xml indicates a released version, and it should be present on a tag and in a distribution bundle. Maven should recognise its existence and use it instead, disabling transitive dependencies. This behaviour could potentially be changed by a CLI parameter. ... Hope this helps, bye Luca Dall'Olio -----Messaggio originale----- Da: Mark Hobson [mailto:[EMAIL PROTECTED] Inviato: martedì 9 gennaio 2007 16.22 A: Maven Users List Oggetto: Re: [m2] Generating release POMs On 09/01/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > Thanks for the link, that'll teach me not to search the archives first ;) > > Looks like this thread was hijacked by an unrelated issue and never > got answered, so the question still stands. Seeing as I've never seen this in action, I assume the idea is for the released POM to contain the resolved versions? If so, why does [1] state "resolved values will be saved in release-pom.xml", and how does this 'release-pom.xml' come into play once released? Pointers to any docs about this would be appreciated. Mark [1] http://maven.apache.org/plugins/maven-release-plugin/examples/generate-relea se-poms.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
