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.
Parleys.com has just published my “Maven 3: Reloaded” presentation from Devoxx ’09. In this presentation, I put our current focus on Maven 3 in context and talk about some of the upcoming technologies like Polyglot Maven and Maven Shell. In this video you’ll see me demonstrate POM translation from XML to Groovy, discuss the ways in which Maven 3 changes allow m2eclipse to embed Maven, and some of the work we’ve done in Tycho to provide a path for OSGi developers.
You watch this embedded video, or watch the presentation over on the Parleys.com site.
Note: To switch between the slides and the video of me talking, click on the smaller video in the upper right-hand of this video embed.
From the very beginning we positioned [Tycho] as the tool for doing Eclipse/OSGi development with Maven. Even though Tycho originally focused on build automation, we think it is time to extend its functionality, as well as integrating it with other projects, to support the full Eclipse/OSGi application development lifecycle.
Below is a preliminary list of key features we want to implement. We want to know if it looks useful, or if we’re totally off base. What other features and improvements are needed to make Tycho a turnkey solution for Eclipse/OSGi development?
Target platform management
Build automation has always been considered painful, especially for complex builds. So, it seemed like a good idea to change that and come up with a solution that would be easy to use. I want to introduce you to Tycho, the next generation of Maven plugins and tools for building Eclipse plugins and RCP applications.
Yesterday’s post was in response to a question from Anders Nawroth of the Neo4J effort, and today’s post is no different. On Tuesday (or maybe it was Monday), Anders asked the neo4j-users list whether it made sense to build the neo4j eclipse plugin with Maven.
I have looked into building Neoclipse using Maven, but at the moment I’m not convinced there are more advantages then disadvantages in this case. Building Eclipse plugins and products has quite many quirks. With increasing use of product configuration options, the number of build quirks increases as well.
There seems to be no really automated build system for Eclipse plugins/products, even when using maven you have to install and update the dependencies manually (the Eclipse artifacts are not deployed to a maven repository).
Sonatype is busily working to address these gaps, and we already have some solutions you can use to start building your Eclipse plugins in Maven. Igor Fedorenko has been working on Tycho and Maven to create a system to facilitate OSGi and Eclipse development in Maven, and m2eclipse is currently built using Tycho. To prove that Tycho is a viable path for build the Neoclipse plugin, I took some time yesterday to generate Maven pom.xml files with Tycho and build an update site for Neoclipse. Continue reading