... 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. 

• Maven
• OSGI
• SpringOSGI
• m2eclipse

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.

Finding myself being in the strange position of being a "supporter" or enthusiast for a specific software shop. Mr Anti-Brand goes against pattern?

Well, maybe being a brand enthusiast is an anti-pattern for me personally, but it keeps on making sense for our little shop, regardless. At least in this one situation.

Where Does OSGI fit into Your Daily Routine?