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/apache/maven/project/DefaultMavenProjectBuilder.java?r1=620420&r2=620422&diff_format=h
This isn't that hard if the model hasn't changed significantly - the
difficulty is going to be when behaviour differs or it needs to be
translated.
(I haven't even started on the project-builder refactor...I don't
know about others).
See my other message about setting up regression testing for this -
I'd like to think about how we get started on it.
If users are not specifying plugin versions, then they are
implicitly saying they're okay with some drift WRT plugin versions
in their builds.
I think this is a reasonable argument, in conjunction with the
guidelines Brian set out - the key being sufficient time to identify
any regressions before updating a plugin.Given more time I see the
reasons for updating - it would be good to incorporate the toolchain
enabled plugins, for example.
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
