A look at Maven 3 alpha
March 22nd, 2010 by Micha KopsWe are all waiting for a stable release of Maven3 with following updates ..
- faster, more performant .. save us time building our software and some precious memory ;)
- improved artifact resolution api and plugin api
- better osgi integration
- a few bugfixes
- no mixing of application dependencies and tooling dependencies
- though it does not matter that much to me: polyglot features .. e.g.: “Writing your pom files in Groovy”
- version-less parent elements for multi-module or multi-pom projects, no need to define the parent version in every submodule
- better artifact resolution, which dependency or pom supplied which artifact to the outcome .. got that information from: “Splitter from the world of Java”
With the current alpha build there are some known problems with Maven2 projects and old maven plugins – some of them made me qq
- AntRun Plugin: AntRun Tasks do not work anymore – some problems with class loader isolation exist in version 1.3
- Site Plugin: Maven3 propagates the need for external documentation software and decouples this feature from the core functions
- Selenium Plugin: Byebye automated front-end testing ;) The GMaven runtime and the new IoC container in Maven3 don’t like each other..
- For a long, detailed list take a look here: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginCompatibilityMatrix
Compatability List with Maven2:
http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
Issue List:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=16087&styleName=Text&projectId=10500
Some information from the Sonatype guys:
http://www.sonatype.com/people/2009/11/maven-3x-paving-the-desire-lines-part-one-2/
http://www.sonatype.com/people/2009/11/maven-30-alpha-3-released/
Tags: Api, ASF, deployment, Development, integration, m2e, maven, maven2, maven3, sonatype