On 29 Dec 06, at 10:21 PM 29 Dec 06, Brett Porter wrote:
Easier to do than explain. I've just removed half of the plugin
parent POM, and compared the output of help:effective-pom for that
and for version 7. They are identical.
To stage before release:
mvn -Pstaging,release-profile deploy s
Thanks, had no idea this was in that page now.
On 30/12/2006, at 2:11 PM, [EMAIL PROTECTED] wrote:
o update versions of plugins that were released recently
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Easier to do than explain. I've just removed half of the plugin
parent POM, and compared the output of help:effective-pom for that
and for version 7. They are identical.
To stage before release:
mvn -Pstaging,release-profile deploy site-deploy
To prepare:
mvn release:prepare
To perform rele
Ok - I guess I'm interested in the actual mechanics. I was initially
thinking you were customising Maven's profile handling itself, but
I'm seeing now you are talking about the release plugin. so it is
actually not using the profile at all any more, and instead grabbing
sum plugin descripti
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 t
On 29 Dec 06, at 9:39 PM 29 Dec 06, Brett Porter wrote:
I wasn't suggesting the super super POM - I was suggesting the
maven/ASF POM where I think it makes sense?
I'm not sure about sharing a profile in this way, doesn't sound
like the right solution to me.
For the simple type of releas
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 o
I wasn't suggesting the super super POM - I was suggesting the maven/
ASF POM where I think it makes sense?
I'm not sure about sharing a profile in this way, doesn't sound like
the right solution to me.
I think the preferred solution might be for the release plugin to be
able to introduce
On 29 Dec 06, at 4:25 PM 29 Dec 06, Brett Porter wrote:
I don't understand why this is needed - this seems to only augment
the one in the parent POM (except for the specification of explicit
versions for source/javadoc which could be changed using plugin
management). Why was overriding nece
On 29 Dec 06, at 4:11 PM 29 Dec 06, [EMAIL PROTECTED] wrote:
Author: brett
Date: Fri Dec 29 13:11:36 2006
New Revision: 491098
URL: http://svn.apache.org/viewvc?view=rev&rev=491098
Log:
add the release profile for this release. In the future, this will
be in a parent POM and can be removed fr
Brett Porter wrote:
Hi,
Some time back, I think we agreed to vote to release parent POMs too. Am
I misremembering, or have we just lost the habit?
I'd like to get back to that, as I've lost track of the reasons for each
release and don't necessarily agree with one of the last ones (need
fur
I don't understand why this is needed - this seems to only augment
the one in the parent POM (except for the specification of explicit
versions for source/javadoc which could be changed using plugin
management). Why was overriding necessary?
- Brett
On 26/12/2006, at 2:08 PM, [EMAIL PROTEC
Hi,
Some time back, I think we agreed to vote to release parent POMs too.
Am I misremembering, or have we just lost the habit?
I'd like to get back to that, as I've lost track of the reasons for
each release and don't necessarily agree with one of the last ones
(need further clarification
Apache implemented some new rules 11/1 regarding releases that required
changes to many core plugins. I was waiting a little for everything else
to get released and things to calm down. It may be prudent to wait for
the release plugin itself to be done first since I know Jason has been
working thr
4 binding +1 votes, I will proceed with the release.
On 23/12/2006, at 3:16 PM, Brett Porter wrote:
Please vote on maven-plugin-plugin and maven-plugin-tools-2.0.x:
- svn rev. 489850
- plugin snapshot is 2.2-20061223.040931-3, plugin-tools snapshot
is 2.0.5-20061223.041242-4
- documentati
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 29 décembre 2006 09:17
> To: continuum-dev@maven.apache.org
> Subject: Re: selenium tests
>
> Only on clean - which you want to do to clean out the database, etc
> but not the container install.
>
> I w
Hello,
I had a couple of problems with Maven's way to access the internet. For
example, if I wanted to redirect maven to the closest mirror, I would
have to define a whole lot of mirrors in my settings.xml. And it
wouldn't always work because different projects use different IDs.
Then, there are
Hello,
I had a couple of problems with Maven's way to access the internet. For
example, if I wanted to redirect maven to the closest mirror, I would
have to define a whole lot of mirrors in my settings.xml. And it
wouldn't always work because different projects use different IDs.
Then, there are
Jeff Jensen a écrit :
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE tracking system has the details for the
initiated users when desired.
Quoting Stephane Nicoll <[EMAIL PROTECTED]>:
On 12/27/06, Jason van Zyl <[EMAI
Hi,
I have a weird issue with the site plugin. I have built 2.0-SNAPSHOT
from SVN trunk. I have a master pom on two projects. This master pom
extends some corporate pom sitting in some area of the repository
(it's not in the parent directory and the master pom does not have any
relative path of a
20 matches
Mail list logo
