First, I’d like to address some misinformation. The use of Github itself was never an issue. It was how the original movement of the sources to Github was executed, and why, that created tension. Github is just a tool and it is a better choice for source control, at least in the short term, for several reasons:
- Rich REST API: Good for IDE and tooling integration and will allow some cool workflows which can empower contributors.
- Known quantity: Developers are very familiar with Github and its workflows. It’s easy for developers to interact with us by forking, making modifications, and submitting pull requests.
- Git repositories are available over HTTPS which makes collaboration at larger organizations easier.
- SVN interoperability: There are still many developers who are comfortable with their SVN tool chain and Github makes working with Git and SVN simultaneously a possibility
We proposed using Github on the Hudson list, and in short order agreement was reached and the move was initiated. Winston did the infrastructure work last night to push the sources for Hudson over to Github. It was really that Simple. It’s amazing how smoothly things go when you clearly communicate your intentions to all stakeholders. We hope to keep improving the infrastructure for Hudson so if you’re interested please join the Hudson Dev list!
You can also keep track of Hudson developments by following us on Twitter!
Today we started rolling out the first of our proposed JSR-330 Dependency Injection changes to Hudson back into the Hudson community. We’re giving it back because we think it is going to make a huge difference for Hudson’s future development. As more and more libraries move to JSR-330, we’re going to see a lot of possibilities open up because of these changes. With today’s donation, we’re making it easier to extend Hudson, we’re reducing the effort required to write a Hudson plugin, and we’re helping to put in a new foundation for the next level of Hudson interoperability and performance.
What does this mean for you as an end-user?
Guice is emerging as a lightweight Dependency Injection standard. We’ve moved the core of Maven to Guice over the past two years and it has dramatically increased performance and opened up possibility for integration with other tools and libraries. Since Guice is implementing JSR-330 standards, what we’re really doing with this effort is moving Hudson to a more standard, more maintainable architecture. As an end-user, you will likely notice increased stability as the core becomes more modular, easier to maintain and test. You should also expect greater integration with other tools that can speak the JSR-330 standard. This includes components that use both Guice and the Spring Framework.
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.
Now the time has come to look to the future for Hudson. To guide our work on the Hudson project, we want to understand how you’re using Hudson and what you might need going forward.
Take a few minutes to fill out the Hudson community survey. To thank you for your time, survey respondents will be entered in a draw to win a 16GB 3G/WiFi Apple iPad.
Official Rules for the Sonatype Hudson Survey iPad drawing can be found here.
Sonatype is pleased to announce the availability of http://mavencentral.sonatype.com, a new website for searching the artifacts in the Maven Central Repository.
What makes this new service different from other sites that index and search the central repository? The new search service is not just a place for quickly and easily researching artifacts on which your project depends, but it is also the most up-to-date source of information on those artifacts other than browsing repo1.maven.org directly.