On Dec 29, 2009, at 7:40 AM, Jason van Zyl wrote: > > On 2009-12-29, at 4:14 AM, Ralph Goers wrote: > >> As I understand it, 3.0 now consists of significant refactoring of the >> internals but no major changes externally. > > This was decided after how much work we've done I figured trying to bring the > community forward on a version of Maven that was a real replacement was more > important. By a real replacement I mean one that can be patched, is easier to > navigate at the source level, have better tests, and remove some of the > architectural problems that would prevent building interesting features that > we want in the future. This took a lot of work and I think pushing out POM > changes and potential interoperability problems just isn't worth it. The > message is Maven 3.x is a drop in replacement and we'll build upon that for > the future.
I didn't mean it as a criticism. Just that 3.0 started out with one target in mind and is now something completely different. At some point we HAVE to do something about making the pom extensible. It just doesn't contain enough information to solve some of the problems. This could be done if Maven would tolerate stuff it doesn't understand. It would be best if this could be done sooner rather than later. i.e., that alone would justify a 2.2 release. Since I haven't done any of the work on 3.0 I'm not going to make a big deal out of what the version number of the release should be. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
