Re: Feature XML generation
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 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
Re: How to integrate a kar file into existing karaf application
Hi, The best option is probably to use directly features instead of kar. For kar, you can use the deploy folder or directly the kar service. So, IMHO: 1. You app should provide a features repo XML and upload artifacts on a repo 2. You can create a custom karaf distro including your features repo Regards JB On Thu, May 11, 2023 at 4:10 AM jose.garnica.lomeli wrote: > > I have a git project that generate a kar file using jenkins pipelines, when > we deploy the kar file we need move it manually into the deploy folder of our > karaf application(the karaf application use accurev instead git) > > In your opinion, what is the best way to improve the process? > > I have some ideas > > 1- move the existing code of kar project into the same repository of the > karaf application as a maven module > > 2- inject the kar file as a maven dependecy > > I think the last one is better but I getting some issues pulling the > artifactory from our nexus repository > > So besides the options already mentioned, is there another alternative? > > My goal is avoid to deploy/install the kar file manually into my karaf > application. > > > Sent from Proton Mail mobile > >
Re: Feature XML generation
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 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
