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]
