Yeah, that's true, I forgot I could do that. I do create parts of mine by hand, but with how out of control transitive dependencies get due to people using ever library they can possibly find, it can be nice to at least use the generated feature xml as a start.... it might slightly turn certain people off having to create them by hand from scratch... but I'll give it a shot and see how it turns out. :)
On Thu, May 11, 2023 at 1:01 PM Jean-Baptiste Onofré <j...@nanthrax.net> 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 <rkmoq...@gmail.com> 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 >
