Re: R: [m2] Generating release POMs
On 15/01/07, Gabriele Contini [EMAIL PROTECTED] wrote: Some time ago i opened a jira issue about this missing feature: http://jira.codehaus.org/browse/MRELEASE-177 Since this is a key feature for our company (we heavily use version ranges and releases are not reproducible), we would like to submit a patch to uncomment and fix the existing code. Does anyone see any reason not to do this? I'd certainly be interested in this - I was going to do the same when I get a chance. Brett (if you're out there!), can you shed any light on why this code was commented-out? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: R: [m2] Generating release POMs
Some time ago i opened a jira issue about this missing feature: http://jira.codehaus.org/browse/MRELEASE-177 Since this is a key feature for our company (we heavily use version ranges and releases are not reproducible), we would like to submit a patch to uncomment and fix the existing code. Does anyone see any reason not to do this? Gabriele Mark Hobson wrote: On 10/01/07, Yann Le Du [EMAIL PROTECTED] wrote: The answer is yes. If your project contains a pom.xml and a release-pom.xml, then the release-pom.xml gets used. That's good news. The problem is about release-plugin not generating the release-pom.xml :( Brett - any insight into why this functionality was commented out? Mark - 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]
Re: R: [m2] Generating release POMs
Thanks for that - I hadn't noticed that part of that document. I guess this invites the question: does Maven currently recognise release-pom.xml's and use them in preference to pom.xml's? Mark The answer is yes. If your project contains a pom.xml and a release-pom.xml, then the release-pom.xml gets used. The problem is about release-plugin not generating the release-pom.xml :( - Yann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: R: [m2] Generating release POMs
On 10/01/07, Yann Le Du [EMAIL PROTECTED] wrote: The answer is yes. If your project contains a pom.xml and a release-pom.xml, then the release-pom.xml gets used. That's good news. The problem is about release-plugin not generating the release-pom.xml :( Brett - any insight into why this functionality was commented out? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: R: [m2] Generating release POMs
On 09/01/07, Luca Dall'Olio [EMAIL PROTECTED] wrote: 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. ... Thanks for that - I hadn't noticed that part of that document. I guess this invites the question: does Maven currently recognise release-pom.xml's and use them in preference to pom.xml's? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
