Are you headed to EclipseCon 2011? It’s not too late to make plans to head to Santa Clara, California in March.
EclipseCon is the conference for anyone involved in Eclipse. As a proud member of the Eclipse Foundation, Sonatype is looking forward to another year of great talks, tutorials and BOF’s. We will be hosting a number of talks in the Cypress Room all day on Tuesday, March 22, 2011.
Sonatype founder Jason van Zyl will be giving a presentation on Building Eclipse plugins and RCP applications with Tycho, Nexus & Hudson.
Stay tuned to the Sonatype blog for updates on Sonatype’s talks and presentations at EclipseCon 2011. And for the latest news and updates from the Sonatype team, follow us on Twitter @SonatypeCM.
Today we are releasing m2e 0.12.1. Despite our previous announcement that 0.12.0 would be the last version made available from Sonatype, we have decided to cut this point release to make available new versions of the m2e dependencies.
Most notably, this release includes recently released Maven 3.0.2 embedded runtime and an updated version of Async HTTP Client that resolves all known issues reported against m2e 0.12.0, and thus helps make m2e work better in corporate environments.
As usual this version of m2e is made available from the Eclipse Marketplace and from http://m2eclipse.sonatype.org/sites/m2e/.
Sonatype books are the essential references for anyone working with Apache Maven, repository management, and integrating Maven with Eclipse.
Learn best practices, central concepts, and complete integration for Maven, Nexus Professional, and m2eclipse. Sonatype books offer the latest content for the software development tools you depend on.
The fourth book in our series of books available for downloading is Developing with Eclipse and Maven.
In this book you will learn how to fully integrate Maven with Eclipse, the world’s most widely used IDE for Java development.
Maven is a software build tool, but it is much more than that. Maven is also a project management tool. It is designed to be flexible, easy, and intuitive – to be a more efficient and comprehensive build tool.
Eclipse is the most widely used IDE for Java development today. Eclipse has a huge amount of plugins and an innumerable amount of organizations developing their own software on top of it. Quite simply, Eclipse is ubiquitous. The m2eclipse project provides full integration for Maven within the Eclipse IDE.
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.
Sonatype recently announced the availability of m2eclipse 0.12. This release includes support for Maven 3.0 and many improvements in the HTTP transport code. This should be the last release made available from the Sonatype servers. But not to worry, we are not stopping the development. In fact, quite conversely, we are ramping up our efforts on the m2eclipse core and moving m2e to the Eclipse foundation.
At this point, the move has not been completed as we are still working with the Eclipse IP team to get all our code and dependencies reviewed. If all goes well, we are hoping to have everything moved to the Eclipse Foundation by mid-December. In the meantime the development is still happening on github but under the new org.eclipse.m2e name-space. We will keep you posted when the code has been completed moved.