I said in my original mail that they wouldn't be locked down. But
either way, there's a number of other plugins that aren't locked down
(compiler, resources, jar, etc) - this is a known problem. For any
that we think it's important to lock down the versions for, we should
do so in plugin ma
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.
Where did the directRelease go that locked down the versions?
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
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
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 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
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
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
