Team $$$ Efficiency Through Modularity

Any veteran developer knows that integration and maintenence is where all the time and money goes, writing a simple module can be a few days work once the requirements, interfaces, and dependencies are set in stone. Modularity (OSGi) promises to eliminate much of that cost, by never fully integrating a module into the rest of the code base. Every module stands on it's own, lives in it's own classpath, and develops in it's own tested, versioned process. Read more »

... from the "Can't We All Just Get Along?" department, you may feel as I do... You want to be lazy where you can, and let these specific Java tools do your work for you. 

And of course, you want it to happen without them fighting each other, and without keeping multiple layers of duplicate metadata synched up in pom.xml, MANIFEST.MF, and gosh knows what other files. In other words, you want DRY.

Sounds great huh? Consider Tycho, if that's your situation. This is Sonatype's work in progress, which neither supports nor fights Spring OSGI, and lets you use the MANIFEST.MF file as your configuration instead of your pom.xml. Even works with p2, if that's you thing.

So I decided to take it for a spin, even though it isn't supposed to be ready yet. Read more »