Are you going to EclipseCon 2011?
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.
Event details:
- Date: March 21-24, 2011
- Location: Hyatt Regency Santa Clara, CA
- Event website: http://www.eclipsecon.org/2011/
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.
Take the Hudson survey
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.
New Service to Search for Artifacts in Maven Central
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. (more…)
Hudson's Bright Future
We believe that Hudson users can look forward to a long, bright future.
Working with the community, Oracle and Sonatype are each putting a number of full-time engineering resources on Hudson. The Hudson lead, Winston Prakash from Oracle, is highly skilled, very thoughtful, and he cares about the community. He is also the first person to create detailed, comprehensive architectural documentation.
This kind of documentation (which has never been available in the past) is required to understand how Hudson can be improved. The lack of architectural documentation, along with how decisions were made, left the Hudson community mostly dependent on a single individual for core changes. Let’s be honest about where this led: (more…)
Maven Tip: Project Directories Should Match the Artifact ID
I almost called this post a Maven “Pet Peeve”, but I’ll stick with “Tip” (and I’ll keep it brief). Here’s a new rule, and I’d really like to hear what the community thinks about this.
Here’s the rule:
Name your project’s directory after the artifactId of your project. It is much easier for everyone to quickly recognize and comprehend multi-module project structure, and it will more closely resemble the experience for developers working with IDEs.
Why do this?
Because it leads to simpler, easier to understand project structure. Some of you might be reading this and asking why we need to remind people of such an obvious rule. Others might take issue with the proposed rule, but I’ll try to detail why I think it is so important. Take the following collection of projects as an example:
Which one do you prefer? Left or right, and why?
On the one hand it is less typing for people on the command line to use simple directory names for Maven modules.
But, on the other hand, if you import these projects with m2eclipse you are going to end up with projects named after the artifactId. The same is true if you import these projects into IntelliJ.
I would suggest always opting for the option on the right. It is clearer than the alternative, and requires less hands-on investigation to track down a culprit project if you are debugging build errors.
An Important Note from Brian Fox: Naming the folder after the artifactId is critical if you expect inherited urls (scm/site) to work. It always appends the artifactId to the url as it’s inherited. And for the same reason, you want them to match what’s in the scm.
