Re: Proper way to setup a features.xml

[John D. Ament]

Perfect, that works.  Let me give it a shot.

John

On Tue, Apr 19, 2016 at 9:21 PM Benson Margulies 
wrote:

> On Tue, Apr 19, 2016 at 9:12 PM, John D. Ament 
> wrote:
> > 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).
>
> A bit more detail:
>
> The aggregating project has many dependences like:
>
> 
> com.basistech.ws
> rosapi-common
> features
> xml
> ${project.version}
> 
>
> Then it has:
>
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 
>   true
> 
> 
>
> and it produces something like:
>
> http://karaf.apache.org/xmlns/features/v1.4.0;
> name="rosapi-features-1.0.100-SNAPSHOT">
>  version="1.0.100.SNAPSHOT">
> The Rosette-API client classes and their Jackson
> dependency.
>
> mvn:com.fasterxml.jackson.core/jackson-annotations/2.6.2
> mvn:com.fasterxml.jackson.core/jackson-core/2.6.2
>
> mvn:com.fasterxml.jackson.core/jackson-databind/2.6.2
> mvn:com.basistech.rosette/rosette-api-json/1.0.100
>
> mvn:com.basistech.rosette/rosette-api-model/1.0.100
> 
>  version="1.0.100.SNAPSHOT">
> Code in common for Rosette API Web Service 1.5
>  dependency="false">bean-validation-support
> mvn:com.basistech.ws/rosapi-common/1.0.100-SNAPSHOT
> 
> mvn:com.basistech/adm-model/1.16.0
>
> 
> 
> 
>
>
>
>
>
>
> >
> > John
> >
> > On Tue, Apr 19, 2016 at 9:09 PM Benson Margulies 
> > 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 
> >> 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
>

Re: Proper way to setup a features.xml

[Benson Margulies]

On Tue, Apr 19, 2016 at 9:12 PM, John D. Ament  wrote:
> 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).

A bit more detail:

The aggregating project has many dependences like:


com.basistech.ws
rosapi-common
features
xml
${project.version}


Then it has:


org.apache.karaf.tooling
karaf-maven-plugin

  true



and it produces something like:

http://karaf.apache.org/xmlns/features/v1.4.0;
name="rosapi-features-1.0.100-SNAPSHOT">

The Rosette-API client classes and their Jackson
dependency.

mvn:com.fasterxml.jackson.core/jackson-annotations/2.6.2
mvn:com.fasterxml.jackson.core/jackson-core/2.6.2
mvn:com.fasterxml.jackson.core/jackson-databind/2.6.2
mvn:com.basistech.rosette/rosette-api-json/1.0.100
mvn:com.basistech.rosette/rosette-api-model/1.0.100


Code in common for Rosette API Web Service 1.5
bean-validation-support
mvn:com.basistech.ws/rosapi-common/1.0.100-SNAPSHOT
mvn:com.basistech/adm-model/1.16.0










>
> John
>
> On Tue, Apr 19, 2016 at 9:09 PM Benson Margulies 
> 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 
>> 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

Re: Proper way to setup a features.xml

[John D. Ament]

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

Re: Proper way to setup a features.xml

[Benson Margulies]

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

Proper way to setup a features.xml

[John D. Ament]

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