karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stuart McCulloch <mccu...@gmail.com>
Subject Re: [DISCUSS] Feature package, feature generation and validation
Date Fri, 21 Oct 2016 12:20:58 GMT
We use the ‘feature’ packaging along with the ‘feature-generate-descriptor’ goal
and it has been working very well for our particular use-case.

So while I’m ok with removing it from the default lifecycle (or better introducing a
flag to control it) I really wouldn’t want to see it totally go away as then we’d have
to maintain the same information twice - both in the Maven pom, and again in the
feature descriptor.

On Thursday, 13 October 2016 at 10:07, Guillaume Nodet wrote:

> The feature packaging is a nice thing, as it allows automatic attachment of
> the feature file.
> However, it always use the feature-generate-descriptor, which produces a
> lot of weird results.
> Afaik, the feature packaging is not much used and all projects i've seen,
> such as pax projects, camel, cxf, and even karaf itself (including
> decanter, cellar, karaf container...).
> I think part of the problem comes from the feature descriptor generation,
> which is difficult to control. I have always found much easier to simply
> write the feature manually.
> Although the generation process rewrites the xml entirely, so that any xml
> comments or license header is lost.
> Overall, I'm not sure that it makes our users life really easier.
> So I'd like to propose to get rid of the feature-generate-descriptor from
> inside the feature packaging and replace it with the verify goal to
> validate the hand-written features instead.
> Thoughts ?
> --  
> ------------------------
> Guillaume Nodet
> ------------------------
> Red Hat, Open Source Integration
> Email: gnodet@redhat.com (mailto:gnodet@redhat.com)
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message