JAXenter talked to Sonatype’s Jason van Zyl about the future of Maven, and what users can expect when migrating from Maven 2 to Maven 3. In this interview, van Zyl and Sonatype’s Brian Fox outline Maven 3, it’s backward compatibility with Maven 2, the introduction of POM mixins, and repository management with Nexus.
The primary goal is a way forward for all Maven users, efficient embedding, increased performance, synchronizing the Maven 3.0 code base with m2eclipse, and adding extension points for tools like Tycho, Polyglot Maven, and the Maven Shell.
To read the full JAXenter interview, click here.
In the next few articles of the “Plexus to Guice” series I will look at the modular design of our replacement Plexus container and show how you can configure a POB (Plain Old Bean) from Guice with a simple code example. In the first article of this series, Jason discussed the need to move to a more widely used and support container, and the reasons why we chose to standardize on Guice. As we migrate more Plexus-based applications (such as Maven) to Guice, we still to maintain backward-compatibility for all of the plugins and extensions which were developed using Plexus. In this post, I start to discuss the scope and initial efforts to create something we’re calling the Guice/Plexus “shim”. It is a library, a “container” that was developed to allow existing Plexus components to use Guice under the hood without any modification. Continue reading