I like the idea of keeping it around to at least assist in the generation
of features.  At that point, I don't mind tweaking and customizing it, it's
just a pain to have to do it all by hand when there are a lot of
dependencies.


On Sun, May 14, 2023 at 3:05 PM Jean-Baptiste Onofré <[email protected]>
wrote:

> Hi Paul,
>
> fair enough, but as soon as you need a "complex/detailed" features
> repo, you need a XML template, so basically writing the repo by hand
> :)
>
> Regards
> JB
>
> On Thu, May 11, 2023 at 8:50 PM Paul Fraser <[email protected]> wrote:
> >
> > Hi JB,
> >
> > "I'm thinking about removing the generate mojo as some point."
> >
> > Please do not remove it, it is most useful when using Vaadin which pulls
> in many bundles.
> >
> > Paul Fraser
> >
> > On 12/05/2023 3:00 am, Jean-Baptiste Onofré wrote:
> > > Hi Ryan
> > >
> > > IMHO, it's always better to create the features XML by hand (and
> verify).
> > >
> > > I'm thinking about removing the generate mojo as some point.
> > >
> > > Regards
> > > JB
> > >
> > > On Tue, May 9, 2023 at 3:58 PM Ryan Moquin <[email protected]> wrote:
> > >> I've been getting the same error as mentioned in KARAF-5999 (
> https://issues.apache.org/jira/browse/KARAF-5999), but I'm just trying to
> generate the features xml for a subproject.  This of course happened after
> I upgraded everything to Camel 3 due to the CXF feature range usage.  Is
> this going to be fixed soon?  I need to decide if I need to either revert
> back to the older Camel or figure out another solution to this error:
> > >>
> > >> Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.16:features-generate-descriptor
> (create-features) on project dp-processor: Unable to create features.xml
> file: org.apache.maven.plugin.MojoExecutionException: Cannot locate file
> for feature: org.apache.cxf.karaf:apache-cxf:xml:features:[3,4) at null ->
> [Help 1]
> > >>
> > >> Hopefully it's something that can be rectified soon.
> > >>
> > >> Thanks!
> > >> Ryan
>

Reply via email to