On 29 Dec 06, at 9:43 PM 29 Dec 06, Brett Porter wrote:
On 30/12/2006, at 1:24 PM, Jason van Zyl wrote:
2) The profile for releases, or any profile, should be put in the
parent POM. It's just completely invisible and people will do
releases differently
agreed
3) Any mojo specified in the lifecycle gets run twice if it's
listed in more then one profile.
I'm still confused - since the source and javadoc definitions are
identical, why do they need to be listed in more than one profile?
Because I didn't use the profile in the Super POM at all.
Putting it in the ASF POM with the same activation and id as the
main one should put them all together fine - it worked for the
plugin tools.
For the staging where I had two definitions of deploy it didn't work.
The source and javadoc mojos are in any lifecycle so no affect there.
I just didn't want to try and mesh them and just created a clean on
outside the super pom.
Perhaps it is something related to the staging that I am missing,
but I was curious why it was added for 'directRelease'.
I just simply by passed the super pom is all.
Anyway, if you can come up with an alternate solution that's even
better.
Will do.
Jason.
- Brett
---------------------------------------------------------------------
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]
