I solve this problem by having one feature file and only deliver/install the features required for the different customers from the one core feature file. But y do you want to aggregate them? Isn't it enough for you to simply take only those feature files you require?
kind regards, andreas On Thu, Jan 06, 2011 at 11:40:21AM -0800, karafman wrote: > > My application is divided functionally between a bunch of areas. When we > deploy these, each functional area will have its own dependencies. As a > result, I'd like to maintain features.xml files for each individual area, > and on compiling the application, aggregate all the features.xml files into > a single provisioning file for the entire application. > > Is there a way to do this? > > > > ----- > Karafman > Slayer of the JEE > Pounder of the Perl Programmer > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Aggregating-provisioning-files-tp2207656p2207656.html > Sent from the Karaf - User mailing list archive at Nabble.com.
pgpM65U6FO6Bs.pgp
Description: PGP signature
