On 29 Oct 07, at 10:47 AM 29 Oct 07, Brett Porter wrote:
Hi,
I noticed that the super POM has changed on trunk (the removal of
the release profile)
Long long time ago.
, but the version hasn't yet - it's still 4.0.0. Also, IT 51 is
excluded which checks the release profile.
For reasons of reproducibility, shouldn't POMs with the current
modelVersion retain the same behaviour, and POMs with a newer
version not receive the profile? Any objections to this being
changed back?
Yes, don't put the release profile back. It's the completely wrong
place for it.
You also don't change the model version didn't change the content did.
The Super POM currently has no version itself which is what changes
when content changes.
Leave it the way it is. It's been like that for a while. Putting the
release information in there was a mistake.
Thanks,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
