[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.0.9) 4.0.10 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.2, 4.0.10 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.1.1) 4.1.2 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.2 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.1.0) 4.1.1 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.0.8) 4.0.9 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.9 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.0.7) 4.0.8 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.8 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4274) feature bundles not found even though they are in required version range
[ https://issues.apache.org/jira/browse/KARAF-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4274: Fix Version/s: (was: 4.0.6) 4.0.7 > feature bundles not found even though they are in required version range > > > Key: KARAF-4274 > URL: https://issues.apache.org/jira/browse/KARAF-4274 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.7 > > > When attempting to install the cxf-http-jetty/3.1.1 feature on Karaf 4.0.4 > (offline), it fails. This feature is comprised of the features cxf-http [3,4) > and jetty [7,10), and bundle > mvn:org.apache.cxf/cxf-rt-transports-http-jetty/3.1.1. > All three of these can be installed and started separately with no probelm, > yet if I try to install the cxf-http-jetty feature itself, there are errors > about missing bundles, which appear to belong to the older jetty 8.1.14 > feature. > So if I understand correctly, it should be using the installed jetty > 9.2.10.v20150310 which is in the required range, but instead it's still > trying to look for the 8.1.14.v20131031 bundles which are not there. > Perhaps related, when configuring karaf-maven-plugin's > features-add-to-repository goal to include the activemq-broker-noweb feature, > and then trying to run karaf with the created offline repo, it gives errors > about missing spring/3.1.4.RELEASE bundles. > activemq-broker-noweb feature (5.13.0) depends on activemq feature depends on > activemq-client feature depends on spring [3.2,4) feature, but at runtime it > fails claiming it's missing spring 3.1.4.RELEASE (even though > 3.2.14.RELEASE_1 is available, installed and started). > So in both cases, it seems to be looking for the wrong (older) unavailable > version at runtime even though the newer version is within the required range > and available. Note that in the jetty case both version are within the > required range, whereas in the activemq case the older version that it claims > is missing is not even in the required range (and the new version that is > within the range and installed is being ignored). > It may be a coincidence, but both problematic dependency features have > arbitrary strings added as part of the version number. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
