Talk about lightning responses Benson! What does something like that look like? Is it broken down into multiple features? Basically I'd love to see a single feature file with one feature for our core, and then distinct features for each module. It seems that the default behavior is to create a single aggregated feature (when aggregate is enabled).
John On Tue, Apr 19, 2016 at 9:09 PM Benson Margulies <[email protected]> wrote: > I have the plugin in each of my modules making a feature, and then an > aggregator project that uses the plugin again to combine them into a > single xml file that makes up the library of features. > > > On Tue, Apr 19, 2016 at 9:07 PM, John D. Ament <[email protected]> > wrote: > > I'm looking to get opinions, and figure it makes sense to get an opinion > > from the creators. > > > > I'm trying to figure out what is the best way to create features files. > > There's a maven plugin, or I can have it checked into source control. > > > > The maven plugin will generate a features.xml for each project. If I > > compare to how camel works, for example, there's a single features.xml > that > > describes everything in use, > > > https://github.com/apache/camel/blob/master/platforms/karaf/features/src/main/resources/features.xml > > > > This seems cleaner because its all in one spot, but a problem because of > the > > large overhead of creating and maintaining the file. So is there any > way to > > automate the generation of something like this file? I'm trying to do > the > > equivalent for Apache Tamaya. > > > > John >
