Hi guys, Here is a summary of Jason's presentation at Devoxx 2009!
Maven 3.0 is very focused on end users requests. One important point is that Maven 3.x is backward compatible. It also ensures that plugins and reports written against the Maven 2.x APIs remains visible in 3.x. They spent a big amount of time creating integration tests (more than 500). Change the ModelBuilder to support XML POMs of version 4.0 as well as any other source (Groovy, JRuby, Python,...). So you can plug your own model reader. Mechanism to extend POMs in a compositional way. It is achieved using mixins. DSLs friendly (Groovy, Ruby, Scala, Python). They will - have access lifecycle extensions points, - be able to modify the execution plan, - be able to decorate the lifecycle. The most important change internally is that you can actually query Maven for the complete execution plan before it happens. Another important point for me: Maven 3.x supports incremental build support. Yet, we have a better integration with m2eclipse to provide deadly fast execution in Eclipse where most of the phases in the default Maven lifecycle don't need to execute. Maven 3.x provides lifecycle extension points at the beginning/end of the lifecycle. It's required to get a nice OSGi integration cause we need to adjust version with real OSGi resolution. Heavy use of Tycho http://docs.codehaus.org/display/M2ECLIPSE/Tycho+project+overview http://docs.codehaus.org/display/M2ECLIPSE/Tycho+project+overview to get better OSGi/Eclipse integration. New Maven Shell Fast and better artifact download/deployments using Jetty Client (connection pooling and parallelization). Get rid of Plexus and use Guice (equivalent to Spring IOC) + peaberry (equivalent to Spring DM) instead. Finally, code base will be reduced and simpler to get more people involved ;-) Jean-Louis -- View this message in context: http://n4.nabble.com/Maven3-tweaks-Re-svn-commit-r903588-tp1311616p1459750.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
