Jason,
I don't entirely agree with all your points below, but agree with the
move out of the super POM by a final 2.1 release so don't feel the
need to go into it any further.
Just two questions remain unanswered:
- are the changes written down anywhere? As I said, I can't find the
page in the wiki that I'm sure used to exist. If not, I will start it.
- I'm also interested in the question Wendy asked about whether the
Clearcase/Perforce issues are already in JIRA?
Thanks,
Brett
On 30/10/2007, at 5:10 PM, Jason van Zyl wrote:
On 29 Oct 07, at 10:42 PM 29 Oct 07, Wendy Smoak wrote:
On 10/29/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I doubt that given my visitation of production environments. But
that
said the portion from our own POM provides the same
functionality, or
it would even be preferable in subsequent versions of the release
plugin to make these goals default. The problem therein is selecting
the right version. Ultimately any sane group of developers wants to
see this information in their face. What is being used to produce
the
release and what version of any tools/plugins being used.
Of course explicit configuration is better, but it's been in the
super
pom for a long time now.
It's been out of the Super POM for quite a while now.
I think all Brett is asking is "How are we
going to help people transition from 2.0 to 2.1?"
To use what's in our own project POM as a working example of a best
practice.
I agree that the release profile shouldn't be in the super pom, but
having it just disappear will be a shock. Is there any way to
"deprecate" this behavior in 2.0, maybe by printing a message when
the
release profile is activated?
Sure, in subsequent versions of the release plugin you can put a
warning saying not to rely on the magic. We are not using it
ourselves anymore, it is explicit in our POMs and has been for the
last few releases.
I'm happily using the Continuum release functionality (but I think
it's the same code) and have used the release plugin for an Archiva
release. It works fine. (Yes, with Subversion.)
It's consistently crapped out for me with the last three releases
of Maven itself. I think the problem is that the bugs fixed are
primarily for Continuum and Archiva. I had to run it several times
and then just reverted to the beta-5 release to get it to work. I
reported the issues and had new ones with the 2.0.7 release, then
had more where it let me go all the way and then died on an SVN
discrepancy. Brian reported and fixed another critical one of late.
Are the issues you
mentioned with Perforce and Clearcase entered in JIRA?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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]
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
