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
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.
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
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
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
