On 30/10/2007, at 7:48 AM, Jason van Zyl wrote:
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.
Yes, I know we discussed it briefly at the time, but I wanted to look
at the actual implications for 2.0.x users now.
, 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.
Mistake as it may be, all I'm looking for is a solution that sees
builds made with 2.0.x (that's everything up until today and for some
time yet) build the same way with 2.1 when someone adds the flags for
these that their now tagged projects expect.
What alternative are you proposing? Is it simply going to be
documented in the release notes as something like "you will no longer
get source and javadoc when you build using the release profile and
will need to add them to the build yourself"?
Thanks,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
