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.
Sonatype helps open source projects by providing free Maven repository hosting and Maven central repository sync. There are hundreds of projects using this great service. As a result, I’ve received many questions from users, and a large amount of them is about ’401′. It is sometimes the case that when people try to deploy artifacts into Nexus using Maven, the deployment fails and they receive a 401 error.
The general definition of ’401′ can be bound at the HTTP RFC. Briefly speaking, a ’401′ error occurs when the server asks for user authentication but the client can not provide it. In Nexus, this means the Nexus server asks you log in first before doing things like deploying artifacts. So when you get a 401 on deploying artifacts to Nexus, you need to make sure you provide correct credentials.
Here is a check list you can follow:
The latest release of Nexus, 18.104.22.168 has been released. In this blog post you will find some of the new functionality and fixes. Click here to download the latest version of Nexus.
64bit Windows Wrapper Support
JIRA Ticket: https://issues.sonatype.org/browse/NEXUS-3844
We have compiled the 64 bit windows libraries for jsw 3.2.3 and now include them in our distributions of Nexus.
Maven 3 Metadata
JIRA Ticket: https://issues.sonatype.org/browse/NEXUS-3806
Maven 3 generates Maven-metadata with extra content that prior versions of Nexus wouldn’t accept. Nexus now handles this metadata change, without complaining.
Also, if you find yourself stuck on an older release of Nexus for some particular reason, you can download this patched jar file to make your Nexus (back to version 1.3.6) work with Maven 3 deployed metadata:
Simply install this jar file in (install-dir)/runtime/app/nexus/lib
Make sure to remove the existing mercury-md-shared-1.0-alpha-6.jar file.
Continuous Integration is a label for a set of tools and techniques that constantly build and report on the health of your applications, preventing developers from checking in broken code, and allowing your development teams to focus on continual improvement overall code quality. It lets you spot problems early in the development process, before testers or end users discover them and fixes become more costly.
Our Senior Systems Engineer, Blaine Mincey, will be presenting at Chariot Solutions Continuous Integration for the Enterprise in Philadelphia on December 1, 2010.
The presentation will focus on:
- Outlining 7 tips for running Maven builds in a CI system
- Introducing Hudson
- A demonstration of Matrix, a component of Sonatype’s latest product suite Sonatype Professional, which features Hudson Integration with Eclipse-based tooling.
If you want to find out how the competition is moving ahead because they don’t have to keep looking behind, this seminar is for you.
Seats are filling up quickly, be sure to register today.
While Maven 3 is a dramatic improvement over Maven 2 from the perspective of performance, extensibility, and architecture, most end-users are motivated by plugins. This has been true about Maven from the beginning, while the framework has value, it is the plugins that make the difference. This blog focuses on the changes that are of interest to plugin authors.