Andreas, That's what I'm currently doing, personally creating one master features.xml file for the application. The problem is, as the functionality of the application grows, and/or as the dependencies within each functional area grows, maintaining a single file becomes a burdensome task.
Borrowing a page from Agile, I'm thinking about pushing down the task of maintaining each functional area's provisioning file to the folks who are actually developing that area of functionality. Then, during compile-time, aggregate them all into a master provisioning file for the application. The folks who know best what technologies are needed are the implementers, so doing this seems a logical thing. As small OSGi applications grow in complexity, this kind of functionality seems like something we'd want to provide (assuming it isn't already present). ----- Karafman Slayer of the JEE Pounder of the Perl Programmer -- View this message in context: http://karaf.922171.n3.nabble.com/Aggregating-provisioning-files-tp2207656p2208537.html Sent from the Karaf - User mailing list archive at Nabble.com.
