Stuart McCulloch wrote:
as I understand it, when you use "mvn -Prelease" it will activate the
release profile
in the parent pom (ie. it will enable the various elements there) and those
elements
will then be inherited by the sub-project - that's why profile inheritance
isn't needed,
because you get it for free... in fact inheriting profiles would lead to
duplication
for example, if I run "mvn -Prelease help:effective-pom" for the
bundleplugin, I see
the additional elements relating to packaging and signing the project/bin
artifacts.
Ah, yes - you're right - thanks for the explanation.
However, I had the case that "help:effective-pom" did not show the
plugin configuration; hmm, I have to investigate this further.
however, it appears that Maven doesn't pass the -P setting onto forked
processes,
for example with "mvn release:perform", which is where Niall's suggestion of
adding
-Darguments="-Prelease" comes in.
Ok, thanks!
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
