Karaf 4.1.0.M2 Feature Verification

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Karaf 4.1.0.M2 Feature Verification

rkmoquin
I decided to try Karaf 4.1.0.M2 again to see if I can figure out why it fails feature validation but passes using Karaf 4.1.0.M1.  The problem is that when it tries to validate the spring feature for camel-spring, it says it can't resolve it, but the spring repo is mentioned in the repos in the pom and the spring feature it mentioned in the feature.xml:

Verification failures:
Feature resolution failed for [rest/1.0.0.SNAPSHOT]
Message: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT; filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))" [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring; type=karaf.feature; version="[4.2.0.M2,4.2.0.M2]"]
Repositories: {
file:C:\dev\project\restul\features\target/feature/feature.xml
mvn:io.hawt/hawtio-karaf/LATEST/xml/features
mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features

My feature.xml where the validation fails is (I don't need the spring feature explicitly mentioned when using 4.1.0.M1):

  <feature name="${project.artifactId}" version="${project.version}">
    <configfile finalname="/etc/org.apache.cxf.osgi.cfg" override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
    <feature>aries-blueprint</feature>
    <feature>camel-blueprint</feature>
    <feature>camel-cxf</feature>
    <feature>cxf-rs-description-swagger2</feature>
  </feature>

Looks like if I don't validate and I try to install the features in Karaf 4.1.0.M2, it also fails on the spring part for some reason.. I'm guessing if it works with M1 that my features are correct, though it seems like the Camel features have been having various issues with various versions of Karaf around feature versions.

Ryan
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

jbonofre
The spring feature version is not 4.2.0.M2: the features repository is 4.2.0.M2,
but the feature version is the spring version.

Regards
JB

On 01/06/2018 05:21 PM, Ryan Moquin wrote:

> I decided to try Karaf 4.1.0.M2 again to see if I can figure out why it fails
> feature validation but passes using Karaf 4.1.0.M1.  The problem is that when it
> tries to validate the spring feature for camel-spring, it says it can't resolve
> it, but the spring repo is mentioned in the repos in the pom and the spring
> feature it mentioned in the feature.xml:
>
> Verification failures:
> Feature resolution failed for [rest/1.0.0.SNAPSHOT]
> Message: Unable to resolve root: missing requirement [root] osgi.identity;
> osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
> filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
> [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement
> [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring; type=karaf.feature;
> version="[4.2.0.M2,4.2.0.M2]"]
> Repositories: {
> file:C:\dev\project\restul\features\target/feature/feature.xml
> mvn:io.hawt/hawtio-karaf/LATEST/xml/features
> mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
> mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
> mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
> mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
> mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
> mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
> mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
> mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>
> My feature.xml where the validation fails is (I don't need the spring feature
> explicitly mentioned when using 4.1.0.M1):
>
>    <feature name="${project.artifactId}" version="${project.version}">
>      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
> override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>      <feature>aries-blueprint</feature>
>      <feature>camel-blueprint</feature>
>      <feature>camel-cxf</feature>
>      <feature>cxf-rs-description-swagger2</feature>
>    </feature>
>
> Looks like if I don't validate and I try to install the features in Karaf
> 4.1.0.M2, it also fails on the spring part for some reason.. I'm guessing if it
> works with M1 that my features are correct, though it seems like the Camel
> features have been having various issues with various versions of Karaf around
> feature versions.
>
> Ryan

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

rkmoquin
Actually, in this case I tried to specify the version, which obviously was wrong, if I don't specify the spring feature, it fails without mentioning that it was looking for any specific feature.  Let me give it another shot since when I was testing with adding the spring feature to my feature.xml I put the wrong version and then took it out of the feature.xml I pasted but it was still in the output.

My bad, this just makes it look like I goofed up (which I certainly did when trying to rectify the problem).

On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]> wrote:
The spring feature version is not 4.2.0.M2: the features repository is 4.2.0.M2,
but the feature version is the spring version.

Regards
JB

On 01/06/2018 05:21 PM, Ryan Moquin wrote:
> I decided to try Karaf 4.1.0.M2 again to see if I can figure out why it fails
> feature validation but passes using Karaf 4.1.0.M1.  The problem is that when it
> tries to validate the spring feature for camel-spring, it says it can't resolve
> it, but the spring repo is mentioned in the repos in the pom and the spring
> feature it mentioned in the feature.xml:
>
> Verification failures:
> Feature resolution failed for [rest/1.0.0.SNAPSHOT]
> Message: Unable to resolve root: missing requirement [root] osgi.identity;
> osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
> filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
> [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement
> [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring; type=karaf.feature;
> version="[4.2.0.M2,4.2.0.M2]"]
> Repositories: {
> file:C:\dev\project\restul\features\target/feature/feature.xml
> mvn:io.hawt/hawtio-karaf/LATEST/xml/features
> mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
> mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
> mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
> mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
> mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
> mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
> mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
> mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>
> My feature.xml where the validation fails is (I don't need the spring feature
> explicitly mentioned when using 4.1.0.M1):
>
>    <feature name="${project.artifactId}" version="${project.version}">
>      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
> override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>      <feature>aries-blueprint</feature>
>      <feature>camel-blueprint</feature>
>      <feature>camel-cxf</feature>
>      <feature>cxf-rs-description-swagger2</feature>
>    </feature>
>
> Looks like if I don't validate and I try to install the features in Karaf
> 4.1.0.M2, it also fails on the spring part for some reason.. I'm guessing if it
> works with M1 that my features are correct, though it seems like the Camel
> features have been having various issues with various versions of Karaf around
> feature versions.
>
> Ryan

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

rkmoquin

JB, I was trying out 4.2.0.M2 again and starting having this same problem.  I finally realized why.  Apache Camel depends on Spring 4.x and Karaf 4.2.0 moved to Spring 5.  This confused me becausefor some reason I though the Karaf spring feature included definitions for multiple spring versions.  Anyhow, Camel won't work with 4.2.0 unless they move to spring 5 or when someone wants to use camel with that Karaf version, they add the latest 4.1.x spring repo to Karaf 4.2.0 and install the Spring 4.x feature.

Ryan


On Sat, Jan 6, 2018, 12:19 PM Ryan Moquin <[hidden email]> wrote:
Actually, in this case I tried to specify the version, which obviously was wrong, if I don't specify the spring feature, it fails without mentioning that it was looking for any specific feature.  Let me give it another shot since when I was testing with adding the spring feature to my feature.xml I put the wrong version and then took it out of the feature.xml I pasted but it was still in the output.

My bad, this just makes it look like I goofed up (which I certainly did when trying to rectify the problem).

On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]> wrote:
The spring feature version is not 4.2.0.M2: the features repository is 4.2.0.M2,
but the feature version is the spring version.

Regards
JB

On 01/06/2018 05:21 PM, Ryan Moquin wrote:
> I decided to try Karaf 4.1.0.M2 again to see if I can figure out why it fails
> feature validation but passes using Karaf 4.1.0.M1.  The problem is that when it
> tries to validate the spring feature for camel-spring, it says it can't resolve
> it, but the spring repo is mentioned in the repos in the pom and the spring
> feature it mentioned in the feature.xml:
>
> Verification failures:
> Feature resolution failed for [rest/1.0.0.SNAPSHOT]
> Message: Unable to resolve root: missing requirement [root] osgi.identity;
> osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
> filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
> [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement
> [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring; type=karaf.feature;
> version="[4.2.0.M2,4.2.0.M2]"]
> Repositories: {
> file:C:\dev\project\restul\features\target/feature/feature.xml
> mvn:io.hawt/hawtio-karaf/LATEST/xml/features
> mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
> mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
> mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
> mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
> mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
> mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
> mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
> mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>
> My feature.xml where the validation fails is (I don't need the spring feature
> explicitly mentioned when using 4.1.0.M1):
>
>    <feature name="${project.artifactId}" version="${project.version}">
>      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
> override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>      <feature>aries-blueprint</feature>
>      <feature>camel-blueprint</feature>
>      <feature>camel-cxf</feature>
>      <feature>cxf-rs-description-swagger2</feature>
>    </feature>
>
> Looks like if I don't validate and I try to install the features in Karaf
> 4.1.0.M2, it also fails on the spring part for some reason.. I'm guessing if it
> works with M1 that my features are correct, though it seems like the Camel
> features have been having various issues with various versions of Karaf around
> feature versions.
>
> Ryan

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

jbonofre
Karaf 4 provides Spring 3, 4 and 5 features.

So:

1. Camel uses the range AFAIR, so it's OK.
2. You can specify the Spring version.

Regards
JB

On 02/10/2018 05:27 PM, Ryan Moquin wrote:

> JB, I was trying out 4.2.0.M2 again and starting having this same problem.  I
> finally realized why.  Apache Camel depends on Spring 4.x and Karaf 4.2.0 moved
> to Spring 5.  This confused me becausefor some reason I though the Karaf spring
> feature included definitions for multiple spring versions.  Anyhow, Camel won't
> work with 4.2.0 unless they move to spring 5 or when someone wants to use camel
> with that Karaf version, they add the latest 4.1.x spring repo to Karaf 4.2.0
> and install the Spring 4.x feature.
>
> Ryan
>
>
> On Sat, Jan 6, 2018, 12:19 PM Ryan Moquin <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Actually, in this case I tried to specify the version, which obviously was
>     wrong, if I don't specify the spring feature, it fails without mentioning
>     that it was looking for any specific feature.  Let me give it another shot
>     since when I was testing with adding the spring feature to my feature.xml I
>     put the wrong version and then took it out of the feature.xml I pasted but
>     it was still in the output.
>
>     My bad, this just makes it look like I goofed up (which I certainly did when
>     trying to rectify the problem).
>
>     On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         The spring feature version is not 4.2.0.M2: the features repository is
>         4.2.0.M2,
>         but the feature version is the spring version.
>
>         Regards
>         JB
>
>         On 01/06/2018 05:21 PM, Ryan Moquin wrote:
>         > I decided to try Karaf 4.1.0.M2 again to see if I can figure out why
>         it fails
>         > feature validation but passes using Karaf 4.1.0.M1.  The problem is
>         that when it
>         > tries to validate the spring feature for camel-spring, it says it
>         can't resolve
>         > it, but the spring repo is mentioned in the repos in the pom and the
>         spring
>         > feature it mentioned in the feature.xml:
>         >
>         > Verification failures:
>         > Feature resolution failed for [rest/1.0.0.SNAPSHOT]
>         > Message: Unable to resolve root: missing requirement [root] osgi.identity;
>         > osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
>         >
>         filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
>         > [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement
>         > [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring;
>         type=karaf.feature;
>         > version="[4.2.0.M2,4.2.0.M2]"]
>         > Repositories: {
>         > file:C:\dev\project\restul\features\target/feature/feature.xml
>         > mvn:io.hawt/hawtio-karaf/LATEST/xml/features
>         > mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
>         > mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
>         > mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
>         > mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
>         > mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
>         > mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
>         > mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>         >
>         > My feature.xml where the validation fails is (I don't need the spring
>         feature
>         > explicitly mentioned when using 4.1.0.M1):
>         >
>         >    <feature name="${project.artifactId}" version="${project.version}">
>         >      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
>         > override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>         >      <feature>aries-blueprint</feature>
>         >      <feature>camel-blueprint</feature>
>         >      <feature>camel-cxf</feature>
>         >      <feature>cxf-rs-description-swagger2</feature>
>         >    </feature>
>         >
>         > Looks like if I don't validate and I try to install the features in Karaf
>         > 4.1.0.M2, it also fails on the spring part for some reason.. I'm
>         guessing if it
>         > works with M1 that my features are correct, though it seems like the Camel
>         > features have been having various issues with various versions of
>         Karaf around
>         > feature versions.
>         >
>         > Ryan
>
>         --
>         Jean-Baptiste Onofré
>         [hidden email] <mailto:[hidden email]>
>         http://blog.nanthrax.net
>         Talend - http://www.talend.com
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

jbonofre
Actually, Camel users should first install spring feature to get Spring 4, or
Camel should use <repository/> to refer Spring 4 Karaf feature.

I will do the change in Camel to be transparent for end-users.

Regards
JB

On 02/10/2018 09:05 PM, Jean-Baptiste Onofré wrote:

> Karaf 4 provides Spring 3, 4 and 5 features.
>
> So:
>
> 1. Camel uses the range AFAIR, so it's OK.
> 2. You can specify the Spring version.
>
> Regards
> JB
>
> On 02/10/2018 05:27 PM, Ryan Moquin wrote:
>> JB, I was trying out 4.2.0.M2 again and starting having this same problem.  I
>> finally realized why.  Apache Camel depends on Spring 4.x and Karaf 4.2.0 moved
>> to Spring 5.  This confused me becausefor some reason I though the Karaf spring
>> feature included definitions for multiple spring versions.  Anyhow, Camel won't
>> work with 4.2.0 unless they move to spring 5 or when someone wants to use camel
>> with that Karaf version, they add the latest 4.1.x spring repo to Karaf 4.2.0
>> and install the Spring 4.x feature.
>>
>> Ryan
>>
>>
>> On Sat, Jan 6, 2018, 12:19 PM Ryan Moquin <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     Actually, in this case I tried to specify the version, which obviously was
>>     wrong, if I don't specify the spring feature, it fails without mentioning
>>     that it was looking for any specific feature.  Let me give it another shot
>>     since when I was testing with adding the spring feature to my feature.xml I
>>     put the wrong version and then took it out of the feature.xml I pasted but
>>     it was still in the output.
>>
>>     My bad, this just makes it look like I goofed up (which I certainly did when
>>     trying to rectify the problem).
>>
>>     On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]
>>     <mailto:[hidden email]>> wrote:
>>
>>         The spring feature version is not 4.2.0.M2: the features repository is
>>         4.2.0.M2,
>>         but the feature version is the spring version.
>>
>>         Regards
>>         JB
>>
>>         On 01/06/2018 05:21 PM, Ryan Moquin wrote:
>>         > I decided to try Karaf 4.1.0.M2 again to see if I can figure out why
>>         it fails
>>         > feature validation but passes using Karaf 4.1.0.M1.  The problem is
>>         that when it
>>         > tries to validate the spring feature for camel-spring, it says it
>>         can't resolve
>>         > it, but the spring repo is mentioned in the repos in the pom and the
>>         spring
>>         > feature it mentioned in the feature.xml:
>>         >
>>         > Verification failures:
>>         > Feature resolution failed for [rest/1.0.0.SNAPSHOT]
>>         > Message: Unable to resolve root: missing requirement [root] osgi.identity;
>>         > osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
>>         >
>>         filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
>>         > [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement
>>         > [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring;
>>         type=karaf.feature;
>>         > version="[4.2.0.M2,4.2.0.M2]"]
>>         > Repositories: {
>>         > file:C:\dev\project\restul\features\target/feature/feature.xml
>>         > mvn:io.hawt/hawtio-karaf/LATEST/xml/features
>>         > mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
>>         > mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
>>         > mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
>>         > mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
>>         > mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
>>         > mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
>>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
>>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
>>         > mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>>         >
>>         > My feature.xml where the validation fails is (I don't need the spring
>>         feature
>>         > explicitly mentioned when using 4.1.0.M1):
>>         >
>>         >    <feature name="${project.artifactId}" version="${project.version}">
>>         >      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
>>         > override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>>         >      <feature>aries-blueprint</feature>
>>         >      <feature>camel-blueprint</feature>
>>         >      <feature>camel-cxf</feature>
>>         >      <feature>cxf-rs-description-swagger2</feature>
>>         >    </feature>
>>         >
>>         > Looks like if I don't validate and I try to install the features in Karaf
>>         > 4.1.0.M2, it also fails on the spring part for some reason.. I'm
>>         guessing if it
>>         > works with M1 that my features are correct, though it seems like the Camel
>>         > features have been having various issues with various versions of
>>         Karaf around
>>         > feature versions.
>>         >
>>         > Ryan
>>
>>         --
>>         Jean-Baptiste Onofré
>>         [hidden email] <mailto:[hidden email]>
>>         http://blog.nanthrax.net
>>         Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

rkmoquin
The Spring feature for Karaf only includes Spring 5 according to http://central.maven.org/maven2/org/apache/karaf/features/spring/4.2.0.M2/spring-4.2.0.M2-features.xml, or am I missing something (my guess is that I'm missing something :))

On Sat, Feb 10, 2018 at 3:17 PM Jean-Baptiste Onofré <[hidden email]> wrote:
Actually, Camel users should first install spring feature to get Spring 4, or
Camel should use <repository/> to refer Spring 4 Karaf feature.

I will do the change in Camel to be transparent for end-users.

Regards
JB

On 02/10/2018 09:05 PM, Jean-Baptiste Onofré wrote:
> Karaf 4 provides Spring 3, 4 and 5 features.
>
> So:
>
> 1. Camel uses the range AFAIR, so it's OK.
> 2. You can specify the Spring version.
>
> Regards
> JB
>
> On 02/10/2018 05:27 PM, Ryan Moquin wrote:
>> JB, I was trying out 4.2.0.M2 again and starting having this same problem.  I
>> finally realized why.  Apache Camel depends on Spring 4.x and Karaf 4.2.0 moved
>> to Spring 5.  This confused me becausefor some reason I though the Karaf spring
>> feature included definitions for multiple spring versions.  Anyhow, Camel won't
>> work with 4.2.0 unless they move to spring 5 or when someone wants to use camel
>> with that Karaf version, they add the latest 4.1.x spring repo to Karaf 4.2.0
>> and install the Spring 4.x feature.
>>
>> Ryan
>>
>>
>> On Sat, Jan 6, 2018, 12:19 PM Ryan Moquin <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     Actually, in this case I tried to specify the version, which obviously was
>>     wrong, if I don't specify the spring feature, it fails without mentioning
>>     that it was looking for any specific feature.  Let me give it another shot
>>     since when I was testing with adding the spring feature to my feature.xml I
>>     put the wrong version and then took it out of the feature.xml I pasted but
>>     it was still in the output.
>>
>>     My bad, this just makes it look like I goofed up (which I certainly did when
>>     trying to rectify the problem).
>>
>>     On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]
>>     <mailto:[hidden email]>> wrote:
>>
>>         The spring feature version is not 4.2.0.M2: the features repository is
>>         4.2.0.M2,
>>         but the feature version is the spring version.
>>
>>         Regards
>>         JB
>>
>>         On 01/06/2018 05:21 PM, Ryan Moquin wrote:
>>         > I decided to try Karaf 4.1.0.M2 again to see if I can figure out why
>>         it fails
>>         > feature validation but passes using Karaf 4.1.0.M1.  The problem is
>>         that when it
>>         > tries to validate the spring feature for camel-spring, it says it
>>         can't resolve
>>         > it, but the spring repo is mentioned in the repos in the pom and the
>>         spring
>>         > feature it mentioned in the feature.xml:
>>         >
>>         > Verification failures:
>>         > Feature resolution failed for [rest/1.0.0.SNAPSHOT]
>>         > Message: Unable to resolve root: missing requirement [root] osgi.identity;
>>         > osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
>>         >
>>         filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
>>         > [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing requirement
>>         > [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring;
>>         type=karaf.feature;
>>         > version="[4.2.0.M2,4.2.0.M2]"]
>>         > Repositories: {
>>         > file:C:\dev\project\restul\features\target/feature/feature.xml
>>         > mvn:io.hawt/hawtio-karaf/LATEST/xml/features
>>         > mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
>>         > mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
>>         > mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
>>         > mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
>>         > mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
>>         > mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
>>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
>>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
>>         > mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>>         >
>>         > My feature.xml where the validation fails is (I don't need the spring
>>         feature
>>         > explicitly mentioned when using 4.1.0.M1):
>>         >
>>         >    <feature name="${project.artifactId}" version="${project.version}">
>>         >      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
>>         > override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>>         >      <feature>aries-blueprint</feature>
>>         >      <feature>camel-blueprint</feature>
>>         >      <feature>camel-cxf</feature>
>>         >      <feature>cxf-rs-description-swagger2</feature>
>>         >    </feature>
>>         >
>>         > Looks like if I don't validate and I try to install the features in Karaf
>>         > 4.1.0.M2, it also fails on the spring part for some reason.. I'm
>>         guessing if it
>>         > works with M1 that my features are correct, though it seems like the Camel
>>         > features have been having various issues with various versions of
>>         Karaf around
>>         > feature versions.
>>         >
>>         > Ryan
>>
>>         --
>>         Jean-Baptiste Onofré
>>         [hidden email] <mailto:[hidden email]>
>>         http://blog.nanthrax.net
>>         Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

jbonofre
Yes, that's why you need spring-legacy feature:

http://repo.maven.apache.org/maven2/org/apache/karaf/features/spring-legacy/4.2.0.M2/spring-legacy-4.2.0.M2-features.xml

Regards
JB

On 02/24/2018 09:57 PM, Ryan Moquin wrote:

> The Spring feature for Karaf only includes Spring 5 according
> to http://central.maven.org/maven2/org/apache/karaf/features/spring/4.2.0.M2/spring-4.2.0.M2-features.xml,
> or am I missing something (my guess is that I'm missing something :))
>
> On Sat, Feb 10, 2018 at 3:17 PM Jean-Baptiste Onofré <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Actually, Camel users should first install spring feature to get Spring 4, or
>     Camel should use <repository/> to refer Spring 4 Karaf feature.
>
>     I will do the change in Camel to be transparent for end-users.
>
>     Regards
>     JB
>
>     On 02/10/2018 09:05 PM, Jean-Baptiste Onofré wrote:
>     > Karaf 4 provides Spring 3, 4 and 5 features.
>     >
>     > So:
>     >
>     > 1. Camel uses the range AFAIR, so it's OK.
>     > 2. You can specify the Spring version.
>     >
>     > Regards
>     > JB
>     >
>     > On 02/10/2018 05:27 PM, Ryan Moquin wrote:
>     >> JB, I was trying out 4.2.0.M2 again and starting having this same problem.  I
>     >> finally realized why.  Apache Camel depends on Spring 4.x and Karaf 4.2.0
>     moved
>     >> to Spring 5.  This confused me becausefor some reason I though the Karaf
>     spring
>     >> feature included definitions for multiple spring versions.  Anyhow, Camel
>     won't
>     >> work with 4.2.0 unless they move to spring 5 or when someone wants to use
>     camel
>     >> with that Karaf version, they add the latest 4.1.x spring repo to Karaf 4.2.0
>     >> and install the Spring 4.x feature.
>     >>
>     >> Ryan
>     >>
>     >>
>     >> On Sat, Jan 6, 2018, 12:19 PM Ryan Moquin <[hidden email]
>     <mailto:[hidden email]>
>     >> <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>     >>
>     >>     Actually, in this case I tried to specify the version, which
>     obviously was
>     >>     wrong, if I don't specify the spring feature, it fails without mentioning
>     >>     that it was looking for any specific feature.  Let me give it another
>     shot
>     >>     since when I was testing with adding the spring feature to my
>     feature.xml I
>     >>     put the wrong version and then took it out of the feature.xml I
>     pasted but
>     >>     it was still in the output.
>     >>
>     >>     My bad, this just makes it look like I goofed up (which I certainly
>     did when
>     >>     trying to rectify the problem).
>     >>
>     >>     On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]
>     <mailto:[hidden email]>
>     >>     <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>     >>
>     >>         The spring feature version is not 4.2.0.M2: the features
>     repository is
>     >>         4.2.0.M2,
>     >>         but the feature version is the spring version.
>     >>
>     >>         Regards
>     >>         JB
>     >>
>     >>         On 01/06/2018 05:21 PM, Ryan Moquin wrote:
>     >>         > I decided to try Karaf 4.1.0.M2 again to see if I can figure
>     out why
>     >>         it fails
>     >>         > feature validation but passes using Karaf 4.1.0.M1.  The problem is
>     >>         that when it
>     >>         > tries to validate the spring feature for camel-spring, it says it
>     >>         can't resolve
>     >>         > it, but the spring repo is mentioned in the repos in the pom
>     and the
>     >>         spring
>     >>         > feature it mentioned in the feature.xml:
>     >>         >
>     >>         > Verification failures:
>     >>         > Feature resolution failed for [rest/1.0.0.SNAPSHOT]
>     >>         > Message: Unable to resolve root: missing requirement [root]
>     osgi.identity;
>     >>         > osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
>     >>         >
>     >>       
>      filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
>     >>         > [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing
>     requirement
>     >>         > [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring;
>     >>         type=karaf.feature;
>     >>         > version="[4.2.0.M2,4.2.0.M2]"]
>     >>         > Repositories: {
>     >>         > file:C:\dev\project\restul\features\target/feature/feature.xml
>     >>         > mvn:io.hawt/hawtio-karaf/LATEST/xml/features
>     >>         > mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
>     >>         > mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
>     >>         > mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
>     >>         > mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
>     >>         > mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
>     >>         > mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
>     >>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
>     >>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
>     >>         > mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>     >>         >
>     >>         > My feature.xml where the validation fails is (I don't need the
>     spring
>     >>         feature
>     >>         > explicitly mentioned when using 4.1.0.M1):
>     >>         >
>     >>         >    <feature name="${project.artifactId}"
>     version="${project.version}">
>     >>         >      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
>     >>         > override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>     >>         >      <feature>aries-blueprint</feature>
>     >>         >      <feature>camel-blueprint</feature>
>     >>         >      <feature>camel-cxf</feature>
>     >>         >      <feature>cxf-rs-description-swagger2</feature>
>     >>         >    </feature>
>     >>         >
>     >>         > Looks like if I don't validate and I try to install the
>     features in Karaf
>     >>         > 4.1.0.M2, it also fails on the spring part for some reason.. I'm
>     >>         guessing if it
>     >>         > works with M1 that my features are correct, though it seems
>     like the Camel
>     >>         > features have been having various issues with various versions of
>     >>         Karaf around
>     >>         > feature versions.
>     >>         >
>     >>         > Ryan
>     >>
>     >>         --
>     >>         Jean-Baptiste Onofré
>     >>         [hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email] <mailto:[hidden email]>>
>     >>         http://blog.nanthrax.net
>     >>         Talend - http://www.talend.com
>     >>
>     >
>
>     --
>     Jean-Baptiste Onofré
>     [hidden email] <mailto:[hidden email]>
>     http://blog.nanthrax.net
>     Talend - http://www.talend.com
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Karaf 4.1.0.M2 Feature Verification

rkmoquin
Ohhhhhhhh, duh.  I knew I had saw a Karaf feature that had the other spring versions in it.  That explains a lot.  I remember seeing that legacy one in the past, my bad.  Thanks for clarifying!

Ryan

On Sat, Feb 24, 2018 at 10:12 PM Jean-Baptiste Onofré <[hidden email]> wrote:
Yes, that's why you need spring-legacy feature:

http://repo.maven.apache.org/maven2/org/apache/karaf/features/spring-legacy/4.2.0.M2/spring-legacy-4.2.0.M2-features.xml

Regards
JB

On 02/24/2018 09:57 PM, Ryan Moquin wrote:
> The Spring feature for Karaf only includes Spring 5 according
> to http://central.maven.org/maven2/org/apache/karaf/features/spring/4.2.0.M2/spring-4.2.0.M2-features.xml,
> or am I missing something (my guess is that I'm missing something :))
>
> On Sat, Feb 10, 2018 at 3:17 PM Jean-Baptiste Onofré <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Actually, Camel users should first install spring feature to get Spring 4, or
>     Camel should use <repository/> to refer Spring 4 Karaf feature.
>
>     I will do the change in Camel to be transparent for end-users.
>
>     Regards
>     JB
>
>     On 02/10/2018 09:05 PM, Jean-Baptiste Onofré wrote:
>     > Karaf 4 provides Spring 3, 4 and 5 features.
>     >
>     > So:
>     >
>     > 1. Camel uses the range AFAIR, so it's OK.
>     > 2. You can specify the Spring version.
>     >
>     > Regards
>     > JB
>     >
>     > On 02/10/2018 05:27 PM, Ryan Moquin wrote:
>     >> JB, I was trying out 4.2.0.M2 again and starting having this same problem.  I
>     >> finally realized why.  Apache Camel depends on Spring 4.x and Karaf 4.2.0
>     moved
>     >> to Spring 5.  This confused me becausefor some reason I though the Karaf
>     spring
>     >> feature included definitions for multiple spring versions.  Anyhow, Camel
>     won't
>     >> work with 4.2.0 unless they move to spring 5 or when someone wants to use
>     camel
>     >> with that Karaf version, they add the latest 4.1.x spring repo to Karaf 4.2.0
>     >> and install the Spring 4.x feature.
>     >>
>     >> Ryan
>     >>
>     >>
>     >> On Sat, Jan 6, 2018, 12:19 PM Ryan Moquin <[hidden email]
>     <mailto:[hidden email]>
>     >> <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>     >>
>     >>     Actually, in this case I tried to specify the version, which
>     obviously was
>     >>     wrong, if I don't specify the spring feature, it fails without mentioning
>     >>     that it was looking for any specific feature.  Let me give it another
>     shot
>     >>     since when I was testing with adding the spring feature to my
>     feature.xml I
>     >>     put the wrong version and then took it out of the feature.xml I
>     pasted but
>     >>     it was still in the output.
>     >>
>     >>     My bad, this just makes it look like I goofed up (which I certainly
>     did when
>     >>     trying to rectify the problem).
>     >>
>     >>     On Sat, Jan 6, 2018 at 11:42 AM Jean-Baptiste Onofré <[hidden email]
>     <mailto:[hidden email]>
>     >>     <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>     >>
>     >>         The spring feature version is not 4.2.0.M2: the features
>     repository is
>     >>         4.2.0.M2,
>     >>         but the feature version is the spring version.
>     >>
>     >>         Regards
>     >>         JB
>     >>
>     >>         On 01/06/2018 05:21 PM, Ryan Moquin wrote:
>     >>         > I decided to try Karaf 4.1.0.M2 again to see if I can figure
>     out why
>     >>         it fails
>     >>         > feature validation but passes using Karaf 4.1.0.M1.  The problem is
>     >>         that when it
>     >>         > tries to validate the spring feature for camel-spring, it says it
>     >>         can't resolve
>     >>         > it, but the spring repo is mentioned in the repos in the pom
>     and the
>     >>         spring
>     >>         > feature it mentioned in the feature.xml:
>     >>         >
>     >>         > Verification failures:
>     >>         > Feature resolution failed for [rest/1.0.0.SNAPSHOT]
>     >>         > Message: Unable to resolve root: missing requirement [root]
>     osgi.identity;
>     >>         > osgi.identity=rest; type=karaf.feature; version=1.0.0.SNAPSHOT;
>     >>         >
>     >>       
>      filter:="(&(osgi.identity=rest)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
>     >>         > [caused by: Unable to resolve rest/1.0.0.SNAPSHOT: missing
>     requirement
>     >>         > [rest/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=spring;
>     >>         type=karaf.feature;
>     >>         > version="[4.2.0.M2,4.2.0.M2]"]
>     >>         > Repositories: {
>     >>         > file:C:\dev\project\restul\features\target/feature/feature.xml
>     >>         > mvn:io.hawt/hawtio-karaf/LATEST/xml/features
>     >>         > mvn:org.apache.camel.karaf/apache-camel/LATEST/xml/features
>     >>         > mvn:org.apache.cxf.karaf/apache-cxf/3.2.1/xml/features
>     >>         > mvn:org.apache.jclouds.karaf/jclouds-karaf/2.0.2/xml/features
>     >>         > mvn:org.apache.karaf.features/framework/4.2.0.M2/xml/features
>     >>         > mvn:org.apache.karaf.features/spring/4.2.0.M2/xml/features
>     >>         > mvn:org.apache.karaf.features/standard/4.2.0.M2/xml/features
>     >>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC1/xml/features
>     >>         > mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
>     >>         > mvn:org.ops4j.pax.web/pax-web-features/6.1.0/xml/features
>     >>         >
>     >>         > My feature.xml where the validation fails is (I don't need the
>     spring
>     >>         feature
>     >>         > explicitly mentioned when using 4.1.0.M1):
>     >>         >
>     >>         >    <feature name="${project.artifactId}"
>     version="${project.version}">
>     >>         >      <configfile finalname="/etc/org.apache.cxf.osgi.cfg"
>     >>         > override="true">mvn:${artifactCoords}/cfg/rest_config</configfile>
>     >>         >      <feature>aries-blueprint</feature>
>     >>         >      <feature>camel-blueprint</feature>
>     >>         >      <feature>camel-cxf</feature>
>     >>         >      <feature>cxf-rs-description-swagger2</feature>
>     >>         >    </feature>
>     >>         >
>     >>         > Looks like if I don't validate and I try to install the
>     features in Karaf
>     >>         > 4.1.0.M2, it also fails on the spring part for some reason.. I'm
>     >>         guessing if it
>     >>         > works with M1 that my features are correct, though it seems
>     like the Camel
>     >>         > features have been having various issues with various versions of
>     >>         Karaf around
>     >>         > feature versions.
>     >>         >
>     >>         > Ryan
>     >>
>     >>         --
>     >>         Jean-Baptiste Onofré
>     >>         [hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email] <mailto:[hidden email]>>
>     >>         http://blog.nanthrax.net
>     >>         Talend - http://www.talend.com
>     >>
>     >
>
>     --
>     Jean-Baptiste Onofré
>     [hidden email] <mailto:[hidden email]>
>     http://blog.nanthrax.net
>     Talend - http://www.talend.com
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com