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> 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 > > > >
