Hi,

the pom file from Vignesh Kumar Muthuvijayan worked. That version has Camel 
3.7.7 as dependency.
I changed that to Camel 3.11.5 and got the warnings I mentioned in my last mail 
but Karaf could start and the bundles/features where installed.
I will try to add more features to this pom.xml and see if this approach will 
work for us.
Thanks so far for the help.

Regards
Frank

-----Ursprüngliche Nachricht-----
Von: Jean-Baptiste Onofré <j...@nanthrax.net>
Gesendet: Mittwoch, 26. Januar 2022 13:22
An: user@karaf.apache.org
Betreff: EXT:Re: AW: EXT:Re: EXT:Re: AW: EXT:Re: EXT:Re: Karaf Tooling Maven 
Plugin produces strange feature file

Hi,

don't you have an issue with hibernate-validator feature while including Camel ?

Regards
JB

On 21/01/2022 12:59, Zinner, Frank Uwe Alfred wrote:
> Hi,
>
> I’ve also tried using Camel 3.11.5 LTS and Camel 3.14.0 – both latest
> versions fail on build with the same error message.
>
> Regards,
>
> Frank
>
> *Von:* Muthuvijayan, Vignesh Kumar
> <vignesh.kumar.muthuvija...@kalmarglobal.com>
> *Gesendet:* Freitag, 21. Januar 2022 12:09
> *An:* user@karaf.apache.org
> *Betreff:* EXT:Re: EXT:Re: AW: EXT:Re: EXT:Re: Karaf Tooling Maven
> Plugin produces strange feature file
>
> Hi,
>
> I actually meant the feature to be added to the blacklisted repo tag
> in the karaf maven plugin configuration like below
>
> <bootFeatures>
>      ...
>      ...
> </bootFeatures>
> <installedFeatures>
>      ...
> </installedFeatures>
> <startupBundles>
>       ....
> </startupBundles>
> <blacklistedRepositories>
>      <!-- Spring Legacy 4.2.10 features are pulled due to Apache Camel
> 3.7.7 dependency -->
>
> <repository>mvn:org.apache.karaf.features/spring-legacy/4.2.10/xml/fea
> tures</repository>
> </blacklistedRepositories>
>
> Can you try this change and make the custom karaf package. With this
> change the 4.2.10 features should not be pulled. You can check this
> even in the maven logs.
>
>
> *Thanks & Regards*
>
> *Vignesh Kumar Muthuvijayan*
>
> On Fri, 21 Jan 2022 at 16:34, Zinner, Frank Uwe Alfred
> <frank.uwe.alfred.zin...@externe.dfs.de
> <mailto:frank.uwe.alfred.zin...@externe.dfs.de>> wrote:
>
>     Hi,
>
>     thank you for helping me out here.
>
>     The POM I send you was a simplistic one. In our project we will need
>     additional libraries such as netty.io <http://netty.io> 4.1.x, cxf
>     3.4.x, the karaf enterprise features, osgi 6, osgi-compendium 5,
>     Jackson etc. - all these worked with karaf 4.2.10 before.
>
>     Kind regards
>     Frank
>
>     -----Ursprüngliche Nachricht-----
>     Von: Jean-Baptiste Onofré <j...@nanthrax.net <mailto:j...@nanthrax.net>>
>     Gesendet: Freitag, 21. Januar 2022 10:33
>     An: user@karaf.apache.org <mailto:user@karaf.apache.org>
>     Betreff: EXT:Re: AW: EXT:Re: EXT:Re: Karaf Tooling Maven Plugin
>     produces strange feature file
>
>     Hi,
>
>     I will send to you an updated pom.xml that you can try.
>
>     Regards
>     JB
>
>     On 21/01/2022 09:17, Zinner, Frank Uwe Alfred wrote:
>      > Hi,
>      >
>      > thanks for the help.
>      > I added the feature to the blacklisted feature file
>      > org.apache.karaf.features.xml but that didn't help.
>      > I still get duplicate entries and karaf won't start. Here's the
>      > exception I get when I trie to run karaf (bin/karaf):
>      >
>      > org.apache.felix.resolver.reason.ReasonException: Unable to resolve
>      > root: missing requirement [root] osgi.identity;
>      > osgi.identity=0e85693d-2124-40a6-b61c-a00c96465280;
>      > type=karaf.feature; version="[0,0.0.0]";
>      >
>     
> filter:="(&(osgi.identity=0e85693d-2124-40a6-b61c-a00c96465280)(type=karaf.feature)(version>=0.0.0)(version<=0.0.0))"
>      > [caused by: Unable to resolve
>      > 0e85693d-2124-40a6-b61c-a00c96465280/0.0.0: missing requirement
>      > [0e85693d-2124-40a6-b61c-a00c96465280/0.0.0] osgi.identity;
>      > osgi.identity=eventadmin; type=karaf.feature;
>      > version="[4.2.10,4.2.10]"]
>      >          at
>      >
>     org.apache.felix.resolver.Candidates$MissingRequirementError.toExcepti
>      > on(Candidates.java:1343)
>      >          at
>      >
>     org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392
>      > )
>      >          at
>      > org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
>      >          at
>      > org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
>      >          at
>      >
>     org.apache.karaf.features.internal.region.SubsystemResolver.resolve(Su
>      > bsystemResolver.java:257)
>      >          at
>      >
>     org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.ja
>      > va:401)
>      >          at
>      >
>     org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvi
>      > sion(FeaturesServiceImpl.java:1063)
>      >          at
>      >
>     org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$
>      > doProvisionInThread$13(FeaturesServiceImpl.java:998)
>      >          at
>      > java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>      >          at
>      >
>     java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>      > Executor.java:1128)
>      >          at
>      >
>     java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>      > lExecutor.java:628)
>      >          at java.base/java.lang.Thread.run(Thread.java:834)
>      > Caused by: org.apache.felix.resolver.reason.ReasonException:
>     Unable to
>      > resolve 0e85693d-2124-40a6-b61c-a00c96465280/0.0.0: missing
>      > requirement [0e85693d-2124-40a6-b61c-a00c96465280/0.0.0]
>      > osgi.identity; osgi.identity=eventadmin; type=karaf.feature;
>     version="[4.2.10,4.2.10]"
>      >          at
>      >
>     org.apache.felix.resolver.Candidates$MissingRequirementError.toExcepti
>      > on(Candidates.java:1343)
>      >          ... 12 more
>      >
>      > Regards
>      > Frank
>      >
>      >
>     ----------------------------------------------------------------------
>      > --
>      > *Von:* Muthuvijayan, Vignesh Kumar
>      > <vignesh.kumar.muthuvija...@kalmarglobal.com
>     <mailto:vignesh.kumar.muthuvija...@kalmarglobal.com>>
>      > *Gesendet:* Donnerstag, 20. Januar 2022 17:58
>      > *An:* user@karaf.apache.org <mailto:user@karaf.apache.org>
>     <user@karaf.apache.org <mailto:user@karaf.apache.org>>
>      > *Betreff:* EXT:Re: EXT:Re: Karaf Tooling Maven Plugin produces
>     strange
>      > feature file Hi,
>      >
>      > I faced this issue while upgrading to Karaf 4.2.14.
>      >
>      > This occurs due to the Karaf 4.2.10 spring-legacy repository
>      > dependency
>      >
>     <https://github.com/apache/camel-karaf/blob/30eebbf0ea4941733696b786c7
>     <https://github.com/apache/camel-karaf/blob/30eebbf0ea4941733696b786c7>
>      >
>     f0f5efed071657/platforms/karaf/features/src/main/resources/features.xm
>      > l#L24>
>      > in Camel Karaf 3.7.7
>      >
>      > Adding the below to the blacklisted repo helps
>      >
>      >
>     <repository>mvn:org.apache.karaf.features/spring-legacy/4.2.10/xml/fea
>      > tures</repository>
>      >
>      >
>      > *Thanks & Regards*
>      > *Vignesh Kumar Muthuvijayan*
>      >
>      >
>      > On Thu, 20 Jan 2022 at 22:16, Zinner, Frank Uwe Alfred
>      > <frank.uwe.alfred.zin...@externe.dfs.de
>     <mailto:frank.uwe.alfred.zin...@externe.dfs.de>
>      > <mailto:frank.uwe.alfred.zin...@externe.dfs.de
>     <mailto:frank.uwe.alfred.zin...@externe.dfs.de>>> wrote:
>      >
>      >     Hi,
>      >
>      >     shure here it is ...
>      >
>      >     Regards
>      >     Frank
>      >
>       ------------------------------------------------------------------------
>      >     *Von:* Jean-Baptiste Onofré <j...@nanthrax.net
>     <mailto:j...@nanthrax.net> <mailto:j...@nanthrax.net
>     <mailto:j...@nanthrax.net>>>
>      >     *Gesendet:* Donnerstag, 20. Januar 2022 17:23
>      >     *An:* user@karaf.apache.org <mailto:user@karaf.apache.org>
>     <mailto:user@karaf.apache.org <mailto:user@karaf.apache.org>>
>      >     <user@karaf.apache.org <mailto:user@karaf.apache.org>
>     <mailto:user@karaf.apache.org <mailto:user@karaf.apache.org>>>
>      >     *Betreff:* EXT:Re: Karaf Tooling Maven Plugin produces strange
>      >     feature file
>      >     Hi,
>      >
>      >     Can you share the pom.xml ? It looks like you have dual deps
>     maybe in
>      >     dependency sets or plugin dependency sets.
>      >
>      >     Regards
>      >     JB
>      >
>      >     On 20/01/2022 16:25, Zinner, Frank Uwe Alfred wrote:
>      >     > Hi,
>      >     >
>      >     > I need to migrate from Karaf 4.2.10 to 4.2.15 and I use the
>      >     > karaf-maven-plugin for building a custom one.
>      >     >
>      >     > With 4.2.10 this works, but from 4.2.11 onwards the build
>     produces
>      >     > different feature files.
>      >     >
>      >     > Here’s an excerpt from the UUID like feature xml file
>     generated with the
>      >     > 4.2.15 version:
>      >     >
>      >     > <features
>     xmlns=http://karaf.apache.org/xmlns/features/v1.6.0
>     <http://karaf.apache.org/xmlns/features/v1.6.0>
>      >     <http://karaf.apache.org/xmlns/features/v1.6.0
>     <http://karaf.apache.org/xmlns/features/v1.6.0>>
>      >     > <http://karaf.apache.org/xmlns/features/v1.6.0
>     <http://karaf.apache.org/xmlns/features/v1.6.0>
>      >     <http://karaf.apache.org/xmlns/features/v1.6.0
>     <http://karaf.apache.org/xmlns/features/v1.6.0>>>
>      >     > name="c9cb60ab-2f43-4db2-94fe-be232fcadcca">
>      >     >
>      >     >
>      >     >
>     
> <repository>mvn:org.apache.karaf.features/standard/4.2.15/xml/features</repository>
>      >     >
>      >     >
>      >     >
>     
> <repository>mvn:org.apache.karaf.features/framework/4.2.15/xml/features</repository>
>      >     >
>      >     >
>      >     >
>     
> <repository>mvn:org.apache.karaf.features/enterprise/4.2.15/xml/features</repository>
>      >     >
>      >     >
>      >     >
>     
> <repository>mvn:org.apache.camel.karaf/apache-camel/3.7.7/xml/features</repository>
>      >     >
>      >     >
>      >     >
>     
> <repository>mvn:org.apache.activemq/activemq-karaf/5.16.2/xml/features</repository>
>      >     >
>      >     >
>     <repository>mvn:io.hawt/hawtio-karaf/2.14.4/xml/features</repository>
>      >     >
>      >     >      <feature name="4d86dce9-a5be-4263-8dfd-ed8cace10e68"
>     version="0.0.0">
>      >     >
>      >     >          <feature version="4.2.15"
>     dependency="false">framework</feature>
>      >     >
>      >     >          <feature version="4.2.10"
>     dependency="false">eventadmin</feature>
>      >     >
>      >     >          <feature version="4.2.15"
>     dependency="false">eventadmin</feature>
>      >     >
>      >     >          <feature version="4.2.10"
>      >     > dependency="false">aries-blueprint</feature>
>      >     >
>      >     >          <feature version="4.2.15"
>      >     > dependency="false">aries-blueprint</feature>
>      >     >
>      >     >          <feature version="2.6.2"
>     dependency="false">wrap</feature>
>      >     >
>      >     >          <feature version="2.6.7" prerequisite="true"
>      >     > dependency="false">wrap</feature>
>      >     >
>      >     >          <feature version="5.16.2"
>      >     > dependency="false">activemq-broker-noweb</feature>
>      >     >
>      >     >          <feature version="4.2.10"
>     dependency="false">bundle</feature>
>      >     >
>      >     >         <feature version="4.2.15"
>     dependency="false">bundle</feature>
>      >     >
>      >     > *The file contains duplicates which differ in versions,
>     this wasn’t the
>      >     > case in 4.2.10.*
>      >     >
>      >     > Any ideas what causes this problem?
>      >     >
>      >     > Karaf won’t start with such a configuration.
>      >     >
>      >     > **
>      >     >
>      >     > Kind regards,
>      >     >
>      >     > Frank
>      >     >
>      >     > **
>      >     >
>      >     > *Frank Uwe Alfred Zinner (extern)*
>      >     >
>      >     > DFS Deutsche Flugsicherung GmbH
>      >     > SH/AM
>      >     > Am DFS-Campus 7
>      >     > 63225 Langen
>      >     >
>      >     > Mail: frank.uwe.alfred.zin...@externe.dfs.de
>     <mailto:frank.uwe.alfred.zin...@externe.dfs.de>
>      >     <mailto:frank.uwe.alfred.zin...@externe.dfs.de
>     <mailto:frank.uwe.alfred.zin...@externe.dfs.de>>
>      >     > <mailto:frank.uwe.alfred.zin...@externe.dfs.de
>     <mailto:frank.uwe.alfred.zin...@externe.dfs.de>
>      >     <mailto:frank.uwe.alfred.zin...@externe.dfs.de
>     <mailto:frank.uwe.alfred.zin...@externe.dfs.de>>>
>      >     >
>      >     > DFS Deutsche Flugsicherung GmbH • Am DFS-Campus • 63225
>     Langen • Tel.:
>      >     > +49 6103 707-0 • Sitz der Gesellschaft: Langen/Hessen •
>     Zuständiges
>      >     > Registergericht: AG Offenbach am Main, HRB 34977 •
>     Vorsitzende des
>      >     > Aufsichtsrats: Antje Geese • Geschäftsführer: Arndt
>     Schoenemann (Vors.),
>      >     > Dr. Kerstin Böcker, Dirk Mahns, Friedrich-Wilhelm Menge •
>     www.dfs.de <http://www.dfs.de> <http://www.dfs.de <http://www.dfs.de>>
>      >     > <http://www.dfs.de <http://www.dfs.de> <http://www.dfs.de
>     <http://www.dfs.de>>>
>      >     >
>      >     > Sollten Sie nicht der richtige Empfänger dieser E-Mail
>     sein, löschen Sie
>      >     > diese bitte.
>      >     >
>      >
>      >     DFS Deutsche Flugsicherung GmbH • Am DFS-Campus • 63225 Langen •
>      >     Tel.: +49 6103 707-0 • Sitz der Gesellschaft: Langen/Hessen •
>      >     Zuständiges Registergericht: AG Offenbach am Main, HRB 34977 •
>      >     Vorsitzende des Aufsichtsrats: Antje Geese • Geschäftsführer:
>     Arndt
>      >     Schoenemann (Vors.), Dr. Kerstin Böcker, Dirk Mahns,
>      >     Friedrich-Wilhelm Menge • www.dfs.de <http://www.dfs.de>
>     <http://www.dfs.de <http://www.dfs.de>>
>      >
>      >     Sollten Sie nicht der richtige Empfänger dieser E-Mail sein,
>     löschen
>      >     Sie diese bitte.
>      >
>      > DFS Deutsche Flugsicherung GmbH • Am DFS-Campus • 63225 Langen •
>     Tel.:
>      > +49 6103 707-0 • Sitz der Gesellschaft: Langen/Hessen • Zuständiges
>      > Registergericht: AG Offenbach am Main, HRB 34977 • Vorsitzende des
>      > Aufsichtsrats: Antje Geese • Geschäftsführer: Arndt Schoenemann
>      > (Vors.), Dr. Kerstin Böcker, Dirk Mahns, Friedrich-Wilhelm Menge •
>      > www.dfs.de <http://www.dfs.de> <http://www.dfs.de
>     <http://www.dfs.de>>
>      >
>      > Sollten Sie nicht der richtige Empfänger dieser E-Mail sein, löschen
>      > Sie diese bitte.
>      >
>     DFS Deutsche Flugsicherung GmbH • Am DFS-Campus • 63225 Langen •
>     Tel.: +49 6103 707-0 • Sitz der Gesellschaft: Langen/Hessen •
>     Zuständiges Registergericht: AG Offenbach am Main, HRB 34977 •
>     Vorsitzende des Aufsichtsrats: Antje Geese • Geschäftsführer: Arndt
>     Schoenemann (Vors.), Dr. Kerstin Böcker, Dirk Mahns,
>     Friedrich-Wilhelm Menge • www.dfs.de
>     <http://www.dfs.de><http://www.dfs.de <http://www.dfs.de>>
>
>     Sollten Sie nicht der richtige Empfänger dieser E-Mail sein, löschen
>     Sie diese bitte.
>
> DFS Deutsche Flugsicherung GmbH • Am DFS-Campus • 63225 Langen • Tel.:
> +49 6103 707-0 • Sitz der Gesellschaft: Langen/Hessen • Zuständiges
> Registergericht: AG Offenbach am Main, HRB 34977 • Vorsitzende des
> Aufsichtsrats: Antje Geese • Geschäftsführer: Arndt Schoenemann
> (Vors.), Dr. Kerstin Böcker, Dirk Mahns, Friedrich-Wilhelm Menge •
> www.dfs.de <http://www.dfs.de>
>
> Sollten Sie nicht der richtige Empfänger dieser E-Mail sein, löschen
> Sie diese bitte.
>
DFS Deutsche Flugsicherung GmbH • Am DFS-Campus • 63225 Langen • Tel.: +49 6103 
707-0 • Sitz der Gesellschaft: Langen/Hessen • Zuständiges Registergericht: AG 
Offenbach am Main, HRB 34977 • Vorsitzende des Aufsichtsrats: Antje Geese • 
Geschäftsführer: Arndt Schoenemann (Vors.), Dr. Kerstin Böcker, Dirk Mahns, 
Friedrich-Wilhelm Menge • www.dfs.de<http://www.dfs.de>

Sollten Sie nicht der richtige Empfänger dieser E-Mail sein, löschen Sie diese 
bitte.

Reply via email to