On 10/04/2008, at 2:11 AM, John Casey wrote:
We cannot change the modelVersion without a fairly major refactor of
one of the most complex classes in Maven - DefaultMavenProjectBuilder.
http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x-terse/maven-project/src/main/java/org/ap
-1
We cannot change the modelVersion without a fairly major refactor of
one of the most complex classes in Maven -
DefaultMavenProjectBuilder. So to make this declaration, we're
basically pinning users to these plugin versions until sometime after
2.1 most likely (I haven't even started o
ailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 9:15 AM
To: Maven Developers List
Subject: Re: plugin versions in super POM and future releases
So just to clarify (with pretend numbers), would this sort of scenario
be fair:
maven-2.0.9 includes:
maven-install-plugi
So just to clarify (with pretend numbers), would this sort of scenario
be fair:
maven-2.0.9 includes:
maven-install-plugin-1.9,
maven-test-plugin-2.2
maven-compile-plugin-2.7
but
maven-2.0.10 includes:
maven-install-plugin-1.9,
maven-test-plugin-2.3
m
ECTED]
Sent: Tuesday, April 08, 2008 11:54 PM
To: Maven Developers List
Subject: plugin versions in super POM and future releases
Hi,
I was wondering if anyone had opinions about what happens in 2.0.10,
2.1, etc with the versions of plugins that are now specified in the
super POM.
My gut fe
-1.
if I recall the discussion about plugin versions in super pom
correctly, the solution was accepted not as a way to have 100%
reprodicible build, but have reproducible builds with one version of
maven for a duration longer than a few weeks (exagerating here a bit).
So it's basically just a way t
Putting (core) plugin versions in the super POM is not a full fix for
projects to be reproductible. Users can still use other non-core
plugins without a version set.
Based on this, I'm +0 to let the superPOM plugins as is as I'd prefer a rule
to have NO plugin with version unset.
Could we move th
Hi,
I was wondering if anyone had opinions about what happens in 2.0.10,
2.1, etc with the versions of plugins that are now specified in the
super POM.
My gut feeling is that we should not upgrade these without a change to
the modelVersion - the POM should be the sole reference for build
