Yeah! Someone who locks them down!
Summary of what I sent to the user list: If you're locking them down
yourself, this will have no effect. It will also not affect the enforcer
plugin output.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008
This is exactly why we lock down plugins ourself. However, I was just
curious to know how it would impact that and how it would impact the use
of the enforcer plugin to catch plugins not locked down.
Thanks.
-Original Message-
From: Sejal Patel [mailto:[EMAIL PROTECTED]
Sent: Thursday,
Issue Subscription
Filter: Design & Best Practices (29 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
Hmm, well jason, it really is as simple as the super pom (that pom-4.0.0
thingy) listing out all of the plugins and specifying a specific version
number on them. I'm taking a peek at the RC5 version of the superpom (havn't
gotten around to 6, 7, or 8 now) and it looks like it is using the most
rece
I have not enough PMCs votes to launch the release. If some of you can test it.
thx
cheers
arnaud
On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Ok that's right. The prerequisite is intended for tools and isn't
> inherited (making it not good for normal builds) but do
Brian,
Is there any documentation about the new "locked down" plugin in feature
in 2.0.9?
I would like to know how it works, how it impacts not having plugins
locked vs. having them locked down already in your pom and how it would
impact the enforcer plugin as well.
Thanks.
-Original Mess
RC8 posted to solve this regression.
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/
-Original Message-
From: Kaizer H. Sogiawala [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 2:51 PM
To: Maven Users List
Subject: Re: [2.0.9 RC7] Release Cand
Ok that's right. The prerequisite is intended for tools and isn't
inherited (making it not good for normal builds) but does apply at
runtime. In this instance, the prerequisite is the most appropriate way
to require the maven version.
-Original Message-
From: Richard van Nieuwenhoven [mail
This only works on single module builds, the prerequisite field is not
inherited.
-Original Message-
From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 4:33 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
On Wed, Apr
Dear Jolly Maven Users,
After many months of alpha testing we are tickled pink to announce the
1.0-beta-1 release of Nexus. Tamás Cservenák, Brian Fox, Eugene
Kuleshov and Justin Richard have been working very hard to bring Maven
users something we feel will benefit the whole community. In
Dear Jolly Maven Users,
After many months of alpha testing we are tickled pink to announce the
1.0-beta-1 release of Nexus. Tamás Cservenák, Brian Fox, Eugene
Kuleshov and Justin Richard have been working very hard to bring Maven
users something we feel will benefit the whole community. In
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know not for the
runtime. We use the plugin in a lot of projects that are locked to maven
2.0.7.
So please limit it only for the build time.
regards,
Ritchie
Jerom
ok thanks. I'll close the vote this evening and I'll release it.
I'll probably release a version 2.5.2 the next week.
cheers
arnaud
On Thu, Apr 3, 2008 at 10:32 AM, Jerome Lacoste
<[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > Hi Jer
On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi Jerome,
>
> As you noticed, this plugin requires to be build with maven >= 2.0.8
> because of some tests with encodings.
> I'll add an enforcer rule as Benjamin proposed.
I had added a patch to the issue hat use
Are you using beta-6 w/o any problems? I can't get it to generate
proper links at all :-(
--jason
On Apr 3, 2008, at 3:26 AM, Brian E. Fox wrote:
I think it's safer to leave it at beta-6. Most people aren't
expressing any issues and if anyone has trouble, they can manually
lock to beta-
15 matches
Mail list logo
