Sonatype uses GitHub to host a number of projects including all of our books. It has been a very valuable tool for us, and we’ve already seen great benefits. The social, interactive nature of the tool allows people interested in the book to keep up with the development of the content, and we’ve already had a few contributors show up and help us write more content. Contributors can fork our books, add whole sections or correct typod and then make a simple pull request that notifies us of the changes. Because we find it so useful, I thought I’d take some time to detail the process of connecting a new Maven project to GitHub. The following post details the process of creating a new GitHub repository, importing a Maven project, and then configuring the SCM element in your project’s POM. Once you’ve done that, you can start using the Maven Release plugin to automate the SCM operations that accompany a release.
The Nexus 1.2.0.2 release is available for download. This release improves upon the architectural enhancements started in 1.1 for plugins. 1.2.0 also provides for greater manageability and customization of the embedded Jetty server, support for incremenetal Nexus indexes, and support for plugins. To download this 1.2.0 release go to