I said intended, because from memory I wasn't sure if it was still
commented out :)
The problem with the use of this POM for release:perform is that it
will be deployed into the repository - and that's not what you want.
You then get the resolved dependencies instead of the declared ones,
which causes anything that uses it as a dependency to have a more
restrictive situation. It really needs the adjustments to the artifact
system, and the POM, that let you separate the declaration from the
resolved graph to be useful.
Cheers,
Brett
On 03/01/2008, at 8:10 AM, Matt Ryall wrote:
On Jan 1, 2008 1:28 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
FWIW, This is precisely the functionality that the
"generateReleasePoms" flag of the release plugin was intended to
provide.
"Intended to provide"? Does it actually provide it?
The documentation for this flag seems a bit inconsistent. It's
listed as a
property for 'release:prepare' at [1], but the example uses
'release:perform' [2]. Will the perform always use the release-
pom.xml if it
exists?
Cheers,
Matt
[1] http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
[2]
http://maven.apache.org/plugins/maven-release-plugin/examples/generate-release-poms.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
