Hi, OK, that’s the problem with Jetty and pax-http-jetty feature.
Most of third party projects (especially CXF and Camel) use the Karaf provided jetty feature. They should NOT do that and use pax-http-jetty. Actually the Karaf jetty feature should be removed. This can lead to two issues: 1. You can have different jetty versions installed if Karaf jetty feature and pax-http-jetty feature are not "aligned" 2. You can have refresh as the resolver see the same resources provided by two features (see https://issues.apache.org/jira/browse/KARAF-6732 <https://issues.apache.org/jira/browse/KARAF-6732> for instance). So, mid term the fix that I gonna do is to change third party projects to use pax-http-jetty and remove the Karaf jetty feature. Short term, you can blacklist jetty feature for instance (as I explain in https://issues.apache.org/jira/browse/KARAF-6732 <https://issues.apache.org/jira/browse/KARAF-6732>). Regards JB > Le 11 juin 2020 à 18:58, Alex Soto <alex.s...@envieta.com> a écrit : > > Hi JB, > > No, it is not Camel 3.3.0. It is Jetty. Here is the output from the Maven > build: > > > [INFO] Feature pax-jetty/9.4.28.v20200408 is defined as a boot feature > [INFO] adding maven artifact: > mvn:org.eclipse.jetty/jetty-util-ajax/9.4.28.v20200408 > [INFO] adding maven artifact: > mvn:javax.annotation/javax.annotation-api/1.3 > [INFO] adding maven artifact: > mvn:org.eclipse.jetty.websocket/javax-websocket-client-impl/9.4.28.v20200408 > > And > > > [INFO] Feature pax-jetty/9.4.20.v20190813 is defined as a boot feature > [INFO] adding maven artifact: > mvn:org.eclipse.jetty/jetty-jaspi/9.4.20.v20190813 > [INFO] adding maven artifact: > mvn:javax.annotation/javax.annotation-api/1.3 > > > I do not explicitly add Jetty, so it must be at a lower level. What would be > nice, though, is to have a flag or something so that Karaf’s plugin can > display the hierarchy so I can easily spot who’s is bringing the dependency. > > > Best regards, > Alex soto > > > > >> On Jun 11, 2020, at 12:34 PM, Jean-Baptiste Onofre <j...@nanthrax.net >> <mailto:j...@nanthrax.net>> wrote: >> >> Hi, >> >> You maybe have a range in another feature using <repository/> ? >> >> If you talk about Camel 3.3.0 and Karaf feature, I already saw the issue and >> created a Jira at Camel to fix that: >> https://issues.apache.org/jira/browse/CAMEL-15166 >> <https://issues.apache.org/jira/browse/CAMEL-15166> >> >> It works fine with Camel 2.25.1 but with the "move" to the new >> feature/repository, it’s weird ;) >> I have to do a cleanup/fix. >> >> Regards >> JB >> >>> Le 11 juin 2020 à 18:31, Alex Soto <alex.s...@envieta.com >>> <mailto:alex.s...@envieta.com>> a écrit : >>> >>> Hello, >>> >>> I have a Karaf custom distribution project, using karaf-maven-plugin >>> plugin. For some reason, 2 versions of the same feature are added to the >>> final distribution as boot features. I’d like to clean it up so only on >>> version is used, but I don’t know why is being added. Is there a way to >>> figure out why a particular feature is added to the distribution? Some >>> tree output of the dependency hierarchy would be nice. Thanks! >>> >>> Best regards, >>> Alex soto >>> >>> >>> >>> >> >
