Which approach do you use for maintaining your manifest?

| | Comments (0) | TrackBacks (0)

I’ve recently been going over the feature wishlist for Osmorc and I found quite some items regarding support for a “Manifest First” style of developing applications. From my experience it becomes increasingly difficult and complex to maintain a growing set of OSGi manifests in bigger projects by hand. And with tools such as BND or Bundlor available, I have a hard time in understanding why anyone would want to manually manage manifests.

Then again, these feature requests exist and they exist for a reason. To shed some light on these reasons I decided to put up a small survey about “Manifest First” vs. “Code First” and just ask for your feedback. It’s only four questions and it would really help me a lot in deciding which path to go with Osmorc in the future and spend the limited development time on the most important features.

So please take the survey and help improving Osmorc!

0 TrackBacks

Listed below are links to blogs that reference this entry: Which approach do you use for maintaining your manifest?.

TrackBack URL for this entry: http://www.osmorc.org/mt/mt-tb.cgi/16

Leave a comment

About this Entry

This page contains a single entry by Jan Thomä published on July 20, 2010 10:00 AM.

Osmorc 1.2.1 released was the previous entry in this blog.

Coming in 1.2.2 - Settings dialog finally done right is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Powered by Movable Type 5.02