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]
R: [m2] Generating release POMs
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]
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]
R: R: [m2] Generating release POMs
By a fast look at maven source code, look like a release-pom.xml would be
handled by maven (org.apache.maven.Maven and org.apache.maven.DefaultMaven)
:
String RELEASE_POMv4 = release-pom.xml;
...
if ( RELEASE_POMv4.equals( file.getName() ) )
{
getLogger().info( NOTE: Using release-pom: + file + in
reactor build. );
usingReleasePom = true;
}
if ( usingReleasePom )
{
moduleFile = new File( basedir, name + / +
Maven.RELEASE_POMv4 );
}
else
{
moduleFile = new File( basedir, name + / + Maven.POMv4 );
}
I will try to create an hand-written release-pom.xml to see if maven can
really handle this,
bye
Luca
-Messaggio originale-
Da: Mark Hobson [mailto:[EMAIL PROTECTED]
Inviato: martedì 9 gennaio 2007 19.19
A: Maven Users List
Oggetto: 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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
