Last week saw the release of Eclipse Indigo, which is the annual release of Eclipse projects. This year 62 projects were included in the release, including m2eclipse from Sonatype. However, since Indigo’s release there have been some questions as to where users can find m2eclipse.
Sonatype software developer Pascal Rapicault recently answered those questions on his blog, and we’re passing the information on to you.
At the time we made the decision regarding where to include m2e, the future of the m2e/WTP integration was uncertain. However, since then the situation has changed, with Fred Bricon being hired by JBoss in order to focus on this piece of technology.
As mentioned earlier on the Sonatype blog, we’re taking some of our most popular sessions from EclipseCon 2011, and releasing them to the wider developer community. The second installment from EclipseCon 2011 is m2eclipse: The collaboration of the Maven & Eclipse Platforms.
Software developer Igor Fedorenko details the new features and changes to m2eclipse 1.0, including pom.xml editor enhancements and reworked build lifecycle mapping.
Sonatype is pleased to announce the launch of Sonatype Professional, the only integrated development suite for Maven-centric Java development. Sonatype Professional integrates and enhances a range of popular open source technologies to streamline Java software development and is specifically designed to improve both the speed and quality of your Java builds. Sonatype Professional integrates the m2eclipse, Nexus Professional, and Matrix Professional (Hudson-based continuous integration) and adds unique developer onboarding functionality to get you productive fast.
Sonatype Professional is tightly integrated with the Eclipse development environment to streamline builds, artifact search and reuse, defect detection, and bug fixes. From within Eclipse, users can:
Visually manage Maven
Browse and search Nexus repositories
Submit Hudson continuous integration jobs
Receive real-time build and continuous integration alerts
As previously mentioned we are in the process of moving m2e to the Eclipse Foundation. Currently we are going over the implications of this move from an end-user perspective and an m2e extension developer’s perspective.
From an end-user perspective this means a wider availability of m2eclipse, but more importantly it means an alignment of m2e with the main Eclipse components and also with the Eclipse releases. m2e will be participating in the Indigo release train and we have asked for its inclusion in the Java Developer Package.
Eclipse is known for IP cleanliness. Through its very thorough IP review process, the Eclipse Foundation has been known to only make available code with a very clear pedigree. In fact, it is this very process that prevented us from moving our code to Eclipse a couple years ago. We now have addressed all the issues uncovered in this initial attempt.
You may wonder, how does this help me? It does not make m2e run faster, or better? You are right, but it helps where you can’t see. It helps making someone in your management chain more comfortable with the usage of m2e, but also enables m2e for inclusion into more Eclipse-based products and to some extent favor the creation of m2e extensions.
From an extender perspective, this move means work. In fact, since m2e namespace will now be org.eclipse.m2e instead of org.maven.ide, m2e extension developers will to be forced to change their code to have their extensions work with the new m2e. Despite our commitment to work in Eclipse 3.7 (Indigo), m2e is still targeted to work on Eclipse 3.5, 3.6 and 3.7, which means that you should not have to maintain two branches of your code one for the “old” Sonatype m2e and one for the new Eclipse m2e.
Overall despite the initial hurdle that can result from this sort of move, we are deeply convinced that it is a great opportunity for the m2e community at large.