[jira] [Commented] (KARAF-4825) When installing features, order bundles using the wiring
[ https://issues.apache.org/jira/browse/KARAF-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687716#comment-15687716 ] James Carman commented on KARAF-4825: - It's interesting that the microbule-spi module is installed later than all those "decorator" modules. All the decorators implement an interface from "spi". > When installing features, order bundles using the wiring > > > Key: KARAF-4825 > URL: https://issues.apache.org/jira/browse/KARAF-4825 > Project: Karaf > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > The idea would be that "used" bundles are installed before "using" bundles, > sort-of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4819) System Property karaf.clean.all Doesn't Work
[ https://issues.apache.org/jira/browse/KARAF-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15647819#comment-15647819 ] James Carman commented on KARAF-4819: - I believe the implementation of KARAF-4475 may have caused this issue, but not positive. > System Property karaf.clean.all Doesn't Work > > > Key: KARAF-4819 > URL: https://issues.apache.org/jira/browse/KARAF-4819 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 4.0.7 >Reporter: James Carman > > When setting the "karaf.clean.all" setting to true in etc/system.properties, > Karaf doesn't appear to be cleaning the data directory. Any bundles > installed before will still be there. In older versions, it started up > clean. Looking in the code, perhaps KARAF-4475 broke this feature? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4819) System Property karaf.clean.all Doesn't Work
[ https://issues.apache.org/jira/browse/KARAF-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4819: Summary: System Property karaf.clean.all Doesn't Work (was: System Property karaf.clean.all Doesn't Work Anymore) > System Property karaf.clean.all Doesn't Work > > > Key: KARAF-4819 > URL: https://issues.apache.org/jira/browse/KARAF-4819 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 4.0.7 >Reporter: James Carman > > When setting the "karaf.clean.all" setting to true in etc/system.properties, > Karaf doesn't appear to be cleaning the data directory. Any bundles > installed before will still be there. In older versions, it started up > clean. Looking in the code, perhaps KARAF-4475 broke this feature? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4819) System Property karaf.clean.all Doesn't Work Anymore
James Carman created KARAF-4819: --- Summary: System Property karaf.clean.all Doesn't Work Anymore Key: KARAF-4819 URL: https://issues.apache.org/jira/browse/KARAF-4819 Project: Karaf Issue Type: Bug Components: karaf-config Affects Versions: 4.0.7 Reporter: James Carman When setting the "karaf.clean.all" setting to true in etc/system.properties, Karaf doesn't appear to be cleaning the data directory. Any bundles installed before will still be there. In older versions, it started up clean. Looking in the code, perhaps KARAF-4475 broke this feature? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429136#comment-15429136 ] James Carman commented on KARAF-4642: - Why was it reopened? Why was it reassigned? On Fri, Aug 19, 2016 at 4:58 PM Jean-Baptiste Onofré (JIRA)> featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 4.1.0, 4.0.6, 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428673#comment-15428673 ] James Carman commented on KARAF-4642: - This is working. Why the change? On Fri, Aug 19, 2016 at 3:00 PM Jean-Baptiste Onofré (JIRA)> featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 4.1.0, 4.0.6, 3.0.9 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4642: Fix Version/s: (was: 4.0.5) 4.0.6 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Critical > Fix For: 4.1.0, 4.0.6, 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420957#comment-15420957 ] James Carman commented on KARAF-4642: - I think perhaps we set the fix version incorrectly for the 4.0.x branch? Version 4.0.5 shows up with date 18-Apr-2016 in Maven Central. Perhaps we need to cut a 4.0.6 with this in it? > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Critical > Fix For: 4.1.0, 4.0.5, 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4644) Pin Build to CXF 3.1.7
[ https://issues.apache.org/jira/browse/KARAF-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4644: Summary: Pin Build to CXF 3.1.7 (was: Pin 4.0.x Branch to CXF 3.1.7) > Pin Build to CXF 3.1.7 > -- > > Key: KARAF-4644 > URL: https://issues.apache.org/jira/browse/KARAF-4644 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.5 >Reporter: James Carman > Original Estimate: 1h > Remaining Estimate: 1h > > The current build uses CXF 3.1.7-SNAPSHOT in the > org.apache.karaf.jaas.modules' pom.xml file. We should pin that to 3.1.7 > since CXF is now at 3.1.8-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4644) Pin 4.0.x Branch to CXF 3.1.7
[ https://issues.apache.org/jira/browse/KARAF-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4644: Summary: Pin 4.0.x Branch to CXF 3.1.7 (was: Ping 4.0.x Branch to CXF 3.1.7) > Pin 4.0.x Branch to CXF 3.1.7 > - > > Key: KARAF-4644 > URL: https://issues.apache.org/jira/browse/KARAF-4644 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.5 >Reporter: James Carman > Original Estimate: 1h > Remaining Estimate: 1h > > The current build uses CXF 3.1.7-SNAPSHOT in the > org.apache.karaf.jaas.modules' pom.xml file. We should pin that to 3.1.7 > since CXF is now at 3.1.8-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4644) Ping 4.0.x Branch to CXF 3.1.7
James Carman created KARAF-4644: --- Summary: Ping 4.0.x Branch to CXF 3.1.7 Key: KARAF-4644 URL: https://issues.apache.org/jira/browse/KARAF-4644 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.5 Reporter: James Carman The current build uses CXF 3.1.7-SNAPSHOT in the org.apache.karaf.jaas.modules' pom.xml file. We should pin that to 3.1.7 since CXF is now at 3.1.8-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4642: Fix Version/s: 4.0.5 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Critical > Fix For: 4.0.5, 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402670#comment-15402670 ] James Carman commented on KARAF-4642: - Created PR for 4.0.x branch: https://github.com/apache/karaf/pull/219 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Critical > Fix For: 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402559#comment-15402559 ] James Carman commented on KARAF-4642: - Any luck with the PR? > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 3.0.8 > > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399843#comment-15399843 ] James Carman commented on KARAF-4642: - Pull request created: https://github.com/apache/karaf/pull/218 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Priority: Critical > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4642) featuresBoot order is not honored
James Carman created KARAF-4642: --- Summary: featuresBoot order is not honored Key: KARAF-4642 URL: https://issues.apache.org/jira/browse/KARAF-4642 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 3.0.7 Reporter: James Carman Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4642) featuresBoot order is not honored
[ https://issues.apache.org/jira/browse/KARAF-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4642: Description: When starting up a vanilla 3.0.7 installation, the featuresBoot is: config,standard,region,package,kar,ssh,management However, looking at the log files, they are not installed in that order: 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature kar 3.0.7 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature management 3.0.7 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature config 3.0.7 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature standard 3.0.7 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature region 3.0.7 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature ssh 3.0.7 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature package 3.0.7 > featuresBoot order is not honored > - > > Key: KARAF-4642 > URL: https://issues.apache.org/jira/browse/KARAF-4642 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.7 >Reporter: James Carman >Priority: Critical > > When starting up a vanilla 3.0.7 installation, the featuresBoot is: > config,standard,region,package,kar,ssh,management > However, looking at the log files, they are not installed in that order: > 2016-07-29 14:10:57,555 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > kar 3.0.7 > 2016-07-29 14:10:57,562 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > management 3.0.7 > 2016-07-29 14:10:57,574 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > config 3.0.7 > 2016-07-29 14:10:57,579 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > standard 3.0.7 > 2016-07-29 14:10:57,596 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > region 3.0.7 > 2016-07-29 14:10:57,602 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > ssh 3.0.7 > 2016-07-29 14:10:57,610 | INFO | FelixStartLevel | FeaturesServiceImpl > | 20 - org.apache.karaf.features.core - 3.0.7 | Installing feature > package 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4494) FeaturesService Should Support Variable Interpolation in featuresRepositories property
[ https://issues.apache.org/jira/browse/KARAF-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241349#comment-15241349 ] James Carman commented on KARAF-4494: - I just confirmed, with 4.0.x, this is not an issue. I was able to use property expressions in that file with no issue. So, looks like we only need to worry about 3.0.x. Thanks for the heads-up, Guillaume! > FeaturesService Should Support Variable Interpolation in featuresRepositories > property > -- > > Key: KARAF-4494 > URL: https://issues.apache.org/jira/browse/KARAF-4494 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 3.0.6 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Minor > Attachments: KARAF-4494.patch > > > When trying to use system properties (from system.properties) in my > featuresRepositories URLs, I get an exception, because no interpolation is > done on the values before they are turned into a URI object (in the setUrls > method). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4494) FeaturesService Should Support Variable Interpolation in featuresRepositories property
[ https://issues.apache.org/jira/browse/KARAF-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241319#comment-15241319 ] James Carman commented on KARAF-4494: - Even better! > FeaturesService Should Support Variable Interpolation in featuresRepositories > property > -- > > Key: KARAF-4494 > URL: https://issues.apache.org/jira/browse/KARAF-4494 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 3.0.6 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Minor > Attachments: KARAF-4494.patch > > > When trying to use system properties (from system.properties) in my > featuresRepositories URLs, I get an exception, because no interpolation is > done on the values before they are turned into a URI object (in the setUrls > method). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4494) FeaturesService Should Support Variable Interpolation in featuresRepositories property
[ https://issues.apache.org/jira/browse/KARAF-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241293#comment-15241293 ] James Carman commented on KARAF-4494: - Right, I reported this against 3.0.6. I didn't create a patch for the 4.0.x or 4.1.x branches yet. > FeaturesService Should Support Variable Interpolation in featuresRepositories > property > -- > > Key: KARAF-4494 > URL: https://issues.apache.org/jira/browse/KARAF-4494 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 3.0.6 >Reporter: James Carman >Assignee: Jamie goodyear >Priority: Minor > Attachments: KARAF-4494.patch > > > When trying to use system properties (from system.properties) in my > featuresRepositories URLs, I get an exception, because no interpolation is > done on the values before they are turned into a URI object (in the setUrls > method). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4494) FeaturesService Should Support Variable Interpolation in featuresRepositories property
[ https://issues.apache.org/jira/browse/KARAF-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-4494: Attachment: KARAF-4494.patch > FeaturesService Should Support Variable Interpolation in featuresRepositories > property > -- > > Key: KARAF-4494 > URL: https://issues.apache.org/jira/browse/KARAF-4494 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 3.0.6 >Reporter: James Carman >Priority: Minor > Attachments: KARAF-4494.patch > > > When trying to use system properties (from system.properties) in my > featuresRepositories URLs, I get an exception, because no interpolation is > done on the values before they are turned into a URI object (in the setUrls > method). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4494) FeaturesService Should Support Variable Interpolation in featuresRepositories property
James Carman created KARAF-4494: --- Summary: FeaturesService Should Support Variable Interpolation in featuresRepositories property Key: KARAF-4494 URL: https://issues.apache.org/jira/browse/KARAF-4494 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 3.0.6 Reporter: James Carman Priority: Minor When trying to use system properties (from system.properties) in my featuresRepositories URLs, I get an exception, because no interpolation is done on the values before they are turned into a URI object (in the setUrls method). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4006) karaf-maven-plugin does not seem to use the local repository
[ https://issues.apache.org/jira/browse/KARAF-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176742#comment-15176742 ] James Carman commented on KARAF-4006: - Is it necessary to set the localRepository property for it to use it? Or does this "just work"? I'm having failures with 4.0.4 after upgrading from 3.0.5 which worked flawlessly. I am not setting localRepository yet, because we didn't have to before. Regression? > karaf-maven-plugin does not seem to use the local repository > > > Key: KARAF-4006 > URL: https://issues.apache.org/jira/browse/KARAF-4006 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.0.1 >Reporter: Christian Schneider >Assignee: Guillaume Nodet > Fix For: 4.0.2 > > > I am using the karaf-maven-plugin to verify the Aries JPA feature for karaf. > After the release I get a build error on jenkins there. As this was the first > build for this version the artifact is not yet in apache snapshot repo. > For these kinds of build to work we must make sure that the plugin by default > also uses the local repository the build uses. > Also see https://builds.apache.org/job/Aries-JPA-Trunk-JDK7/53/console > [INFO] > > [INFO] Building Apache Aries JPA features 2.3.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jpa-features --- > [INFO] Deleting > /home/jenkins/jenkins-slave/workspace/Aries-JPA-Trunk-JDK7/jpa-features/target > [INFO] > [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ jpa-features > --- > [INFO] > [INFO] --- karaf-maven-plugin:4.0.1:features-generate-descriptor (compile) @ > jpa-features --- > [INFO] Generating feature descriptor file > /home/jenkins/jenkins-slave/workspace/Aries-JPA-Trunk-JDK7/jpa-features/target/feature/feature.xml > [INFO] ...done! > [INFO] > [INFO] --- karaf-maven-plugin:4.0.1:verify (verify) @ jpa-features --- > [INFO] Using repositories: > http://repository.apache.org/snapshots@id=Nexus@noreleases@snapshots,https://repo.maven.apache.org/maven2@id=central > [INFO] Verification of feature persistence-api/2.0.0 succeeded > [INFO] Verification of feature persistence-api/2.1.0 succeeded > [WARNING] Error resolving > artifactorg.apache.aries.jpa:org.apache.aries.jpa.blueprint:jar:2.3.0-SNAPSHOT:Could > not find artifact > org.apache.aries.jpa:org.apache.aries.jpa.blueprint:jar:2.3.0-SNAPSHOT in > Nexus (http://repository.apache.org/snapshots/) > shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not > find artifact > org.apache.aries.jpa:org.apache.aries.jpa.blueprint:jar:2.3.0-SNAPSHOT in > Nexus (http://repository.apache.org/snapshots/) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) > at > shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) > at > shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:573) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:528) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:506) > at > org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:481) > at > org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:34) > at > org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:58) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Caused by:
[jira] [Created] (KARAF-3729) Maven Plugin Doesn't Support Filtered Resources
James Carman created KARAF-3729: --- Summary: Maven Plugin Doesn't Support Filtered Resources Key: KARAF-3729 URL: https://issues.apache.org/jira/browse/KARAF-3729 Project: Karaf Issue Type: Bug Components: karaf-tooling Affects Versions: 3.0.3 Reporter: James Carman When trying to include resources in a custom distribution using the karaf-maven-plugin, it doesn't include the filtered version of the resources. It grabs them straight from the src/main/resources directory, not the target/classes directory. I've created a pull request to fix this: https://github.com/apache/karaf/pull/61 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-1545) Jar files in lib directory require karaf- prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026529#comment-14026529 ] James Carman commented on KARAF-1545: - How about just fix the documentation? The intended behavior was that only karaf-prefixed jars would be loaded, so the docs are obviously wrong. Jar files in lib directory require karaf- prefix in order to be loaded Key: KARAF-1545 URL: https://issues.apache.org/jira/browse/KARAF-1545 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 2.2.2 Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_32/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman Assignee: Jean-Baptiste Onofré Fix For: 2.2.12, 2.4.0, 3.0.2, 2.3.6 Attachments: karaf-3.0_1545.diff I was trying to configure JDBC fail-over, so I put my mysql driver jar in the KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the advice of someone on IRC, I changed the name to karaf-mysql-connector-java.jar and it started working. Why the karaf- prefix requirement? If that's the intended behavior, then please update the README file in the lib directory. It says: Any jar in this folder will be part of the main classloader used to load Karaf. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-1545) Jar files in lib directory require karaf- prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656009#comment-13656009 ] James Carman commented on KARAF-1545: - The failover is a Karaf feature, *not* an app feature. Jar files in lib directory require karaf- prefix in order to be loaded Key: KARAF-1545 URL: https://issues.apache.org/jira/browse/KARAF-1545 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 2.2.2 Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_32/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman Assignee: Jean-Baptiste Onofré Fix For: 2.2.12, 2.3.2, 2.4.0, 3.0.0 Attachments: karaf-3.0_1545.diff I was trying to configure JDBC fail-over, so I put my mysql driver jar in the KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the advice of someone on IRC, I changed the name to karaf-mysql-connector-java.jar and it started working. Why the karaf- prefix requirement? If that's the intended behavior, then please update the README file in the lib directory. It says: Any jar in this folder will be part of the main classloader used to load Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1545) Jar files in lib directory require karaf- prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655013#comment-13655013 ] James Carman commented on KARAF-1545: - It will only surprise folks who put jars in the lib directory and counted on them not being picked up because they didn't have the karaf- prefix. The documentation says that *any* jar in that directory should be picked up, so they would have to be taking advantage of this bug in order to be surprised. Jar files in lib directory require karaf- prefix in order to be loaded Key: KARAF-1545 URL: https://issues.apache.org/jira/browse/KARAF-1545 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 2.2.2 Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_32/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman Assignee: Jean-Baptiste Onofré Fix For: 2.2.12, 2.3.2, 2.4.0, 3.0.0 Attachments: karaf-3.0_1545.diff I was trying to configure JDBC fail-over, so I put my mysql driver jar in the KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the advice of someone on IRC, I changed the name to karaf-mysql-connector-java.jar and it started working. Why the karaf- prefix requirement? If that's the intended behavior, then please update the README file in the lib directory. It says: Any jar in this folder will be part of the main classloader used to load Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1545) Jar files in lib directory require karaf- prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653485#comment-13653485 ] James Carman commented on KARAF-1545: - Nice work, Heath! Thanks, man. Jar files in lib directory require karaf- prefix in order to be loaded Key: KARAF-1545 URL: https://issues.apache.org/jira/browse/KARAF-1545 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 2.2.2 Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_32/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman Assignee: Jean-Baptiste Onofré Fix For: 2.2.12, 2.3.2, 2.4.0, 3.0.0 Attachments: karaf-3.0_1545.diff I was trying to configure JDBC fail-over, so I put my mysql driver jar in the KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the advice of someone on IRC, I changed the name to karaf-mysql-connector-java.jar and it started working. Why the karaf- prefix requirement? If that's the intended behavior, then please update the README file in the lib directory. It says: Any jar in this folder will be part of the main classloader used to load Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1823) Memory leak on windows in SSHD ServerSession
[ https://issues.apache.org/jira/browse/KARAF-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455718#comment-13455718 ] James Carman commented on KARAF-1823: - Is this Windows as a host or client? Memory leak on windows in SSHD ServerSession Key: KARAF-1823 URL: https://issues.apache.org/jira/browse/KARAF-1823 Project: Karaf Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet We use apache-karaf-2.2.9 in windows 2008 server R2. I've run a lot of Ssh Echo in a short time. And the karaf memory peaked, and we receive out of memory as exception.(see the attached picture http://karaf.922171.n3.nabble.com/file/n4026025/Jconsole_Karaf.png ) Running jhat shows some classes that should consume such memory: class org.apache.activemq.command.ProducerId 21706 955064 class org.apache.felix.gogo.runtime.Token 46536 930720 class org.apache.felix.gogo.runtime.Closure 9972 717984 *class org.apache.sshd.server.session.ServerSession 1662 563418 class org.apache.mina.transport.socket.nio.NioSocketSession 1662 511896 * class [Lorg.apache.activemq.command.DataStructure; 48 393984 The memory leak seems to lie around unclosed ssh server session. To reproduce the problem, you have just to run this script loopsshecho.bat that will allow to reproduce rapidly the bug http://karaf.922171.n3.nabble.com/file/n4026025/probes.zip probes.zip : {code} @echo ON :again CALL launch-javaprobe.bat com.eurofins.nagios.probe.ssh.SSHEcho --hostname Localhost --login karaf --password karaf --sshport 8101 ECHO . goto again {code} You have to change the parametrs of : --hostname --login --password --sshport -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-1548) The features-maven-plugin is dependent upon the order of the declaration of the dependencies.
James Carman created KARAF-1548: --- Summary: The features-maven-plugin is dependent upon the order of the declaration of the dependencies. Key: KARAF-1548 URL: https://issues.apache.org/jira/browse/KARAF-1548 Project: Karaf Issue Type: Bug Components: karaf-tooling Affects Versions: 2.2.2 Environment: Java version: 1.6.0_31, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_31/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman When declaring your dependencies in your pom.xml file, the order of the dependencies changes the generated file quite dramatically. For instance, if I declare: {code:xml} dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.camel/artifactId version1.0.0-SNAPSHOT/version /dependency dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.service/artifactId version1.0.0-SNAPSHOT/version /dependency {code} I get: {code:xml} feature name='com.carmanconsulting.smx.example.camel' version='1.0.0-SNAPSHOT' feature version='1.3.1'com.springsource.com.thoughtworks.xstream/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.camel/1.0.0-SNAPSHOT/bundle /feature feature name='com.carmanconsulting.smx.example.service' version='1.0.0-SNAPSHOT' feature version='1.5'domdrides-core/feature feature version='2.4'commons-lang/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.service/1.0.0-SNAPSHOT/bundle /feature {code} However, if I do: {code:xml} dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.service/artifactId version1.0.0-SNAPSHOT/version /dependency dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.camel/artifactId version1.0.0-SNAPSHOT/version /dependency {code} I get: {code:xml} feature name='com.carmanconsulting.smx.example.service' version='1.0.0-SNAPSHOT' feature version='1.5'domdrides-core/feature feature version='2.4'commons-lang/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.service/1.0.0-SNAPSHOT/bundle /feature feature name='com.carmanconsulting.smx.example.camel' version='1.0.0-SNAPSHOT' feature version='1.3.1'com.springsource.com.thoughtworks.xstream/feature feature version='1.0.0-SNAPSHOT'com.carmanconsulting.smx.example.service/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.camel/1.0.0-SNAPSHOT/bundle /feature {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1548) The features-maven-plugin is dependent upon the order of the declaration of the dependencies.
[ https://issues.apache.org/jira/browse/KARAF-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated KARAF-1548: Affects Version/s: (was: 2.2.2) 2.2.7 The features-maven-plugin is dependent upon the order of the declaration of the dependencies. - Key: KARAF-1548 URL: https://issues.apache.org/jira/browse/KARAF-1548 Project: Karaf Issue Type: Bug Components: karaf-tooling Affects Versions: 2.2.7 Environment: Java version: 1.6.0_31, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_31/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman When declaring your dependencies in your pom.xml file, the order of the dependencies changes the generated file quite dramatically. For instance, if I declare: {code:xml} dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.camel/artifactId version1.0.0-SNAPSHOT/version /dependency dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.service/artifactId version1.0.0-SNAPSHOT/version /dependency {code} I get: {code:xml} feature name='com.carmanconsulting.smx.example.camel' version='1.0.0-SNAPSHOT' feature version='1.3.1'com.springsource.com.thoughtworks.xstream/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.camel/1.0.0-SNAPSHOT/bundle /feature feature name='com.carmanconsulting.smx.example.service' version='1.0.0-SNAPSHOT' feature version='1.5'domdrides-core/feature feature version='2.4'commons-lang/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.service/1.0.0-SNAPSHOT/bundle /feature {code} However, if I do: {code:xml} dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.service/artifactId version1.0.0-SNAPSHOT/version /dependency dependency groupId${project.groupId}/groupId artifactIdcom.carmanconsulting.smx.example.camel/artifactId version1.0.0-SNAPSHOT/version /dependency {code} I get: {code:xml} feature name='com.carmanconsulting.smx.example.service' version='1.0.0-SNAPSHOT' feature version='1.5'domdrides-core/feature feature version='2.4'commons-lang/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.service/1.0.0-SNAPSHOT/bundle /feature feature name='com.carmanconsulting.smx.example.camel' version='1.0.0-SNAPSHOT' feature version='1.3.1'com.springsource.com.thoughtworks.xstream/feature feature version='1.0.0-SNAPSHOT'com.carmanconsulting.smx.example.service/feature bundlemvn:com.carmanconsulting.smx/com.carmanconsulting.smx.example.camel/1.0.0-SNAPSHOT/bundle /feature {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-1545) Jar files in lib directory require karaf- prefix in order to be loaded
James Carman created KARAF-1545: --- Summary: Jar files in lib directory require karaf- prefix in order to be loaded Key: KARAF-1545 URL: https://issues.apache.org/jira/browse/KARAF-1545 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 2.2.2 Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_32/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman I was trying to configure JDBC fail-over, so I put my mysql driver jar in the KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the advice of someone on IRC, I changed the name to karaf-mysql-connector-java.jar and it started working. Why the karaf- prefix requirement? If that's the intended behavior, then please update the README file in the lib directory. It says: Any jar in this folder will be part of the main classloader used to load Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1545) Jar files in lib directory require karaf- prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294601#comment-13294601 ] James Carman commented on KARAF-1545: - I don't like the idea of having to muck with the CLASSPATH environment variable. Nobody really does that anymore, do they? Perhaps adding a new folder third-party in the lib directory and put that README in there? That wouldn't change the functionality, really. It would only break anyone who put a third-party folder in their lib directory manually. Jar files in lib directory require karaf- prefix in order to be loaded Key: KARAF-1545 URL: https://issues.apache.org/jira/browse/KARAF-1545 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 2.2.2 Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. Java home: /home/jcarman/Programs/jdk1.6.0_32/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-24-generic, arch: amd64, family: unix Reporter: James Carman I was trying to configure JDBC fail-over, so I put my mysql driver jar in the KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the advice of someone on IRC, I changed the name to karaf-mysql-connector-java.jar and it started working. Why the karaf- prefix requirement? If that's the intended behavior, then please update the README file in the lib directory. It says: Any jar in this folder will be part of the main classloader used to load Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira