[jira] [Commented] (KARAF-4360) FrameworkEvent ERROR in the karaf.log when install cxf-core feature

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220898#comment-15220898
 ] 

Jean-Baptiste Onofré commented on KARAF-4360:
-

There's no problem if you install the cxf feature instead of cxf-core.

I'm postponing this issue for the next release cycle to give time to 
investigate.

> FrameworkEvent ERROR in the karaf.log when install cxf-core feature
> ---
>
> Key: KARAF-4360
> URL: https://issues.apache.org/jira/browse/KARAF-4360
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.4
> Environment: Java 8
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> When trying to install cxf-core feature into Karaf 4.0.4, there is 
> FrameworkEvent ERROR in the karaf.log, but the bundles can be started and in 
> the Active status.
> {code}
> 2016-02-25 12:09:57,529 | ERROR | 8d8-961af9b70a25 | cxf-core 
> | 53 - org.apache.cxf.cxf-core - 3.1.5 | FrameworkEvent ERROR - 
> org.apache.cxf.cxf-core
> org.osgi.framework.BundleException: Could not resolve module: 
> org.apache.cxf.cxf-core [53]
>   Unresolved requirement: Import-Package: com.ctc.wstx.msv; 
> version="[4.4.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.ctc.wstx.stax; 
> version="[4.4.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.codehaus.stax2; 
> version="[3.1.0,4.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.codehaus.stax2.validation; 
> version="[3.1.0,4.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.grammar; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.grammar.xmlschema; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.reader; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.reader.xmlschema; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.xml.bind.marshaller; 
> version="[2.2.0,3.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.xml.fastinfoset.stax; 
> version="[1.2.0,2.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: net.sf.cglib.proxy; 
> version="[2.1.3,3.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.osgi.io; 
> version="[1.2.0,2.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.osgi.util; 
> version="[1.2.0,2.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.aop; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.aop.framework; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.aop.support; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.beans; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.beans.factory; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.config; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.support; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.wiring; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.xml; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.context; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.context.event; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.context.support; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.core; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.core.io; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.core.io.support; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: 

[jira] [Updated] (KARAF-4360) FrameworkEvent ERROR in the karaf.log when install cxf-core feature

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4360:

Fix Version/s: (was: 4.0.5)
   4.0.6

> FrameworkEvent ERROR in the karaf.log when install cxf-core feature
> ---
>
> Key: KARAF-4360
> URL: https://issues.apache.org/jira/browse/KARAF-4360
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.4
> Environment: Java 8
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> When trying to install cxf-core feature into Karaf 4.0.4, there is 
> FrameworkEvent ERROR in the karaf.log, but the bundles can be started and in 
> the Active status.
> {code}
> 2016-02-25 12:09:57,529 | ERROR | 8d8-961af9b70a25 | cxf-core 
> | 53 - org.apache.cxf.cxf-core - 3.1.5 | FrameworkEvent ERROR - 
> org.apache.cxf.cxf-core
> org.osgi.framework.BundleException: Could not resolve module: 
> org.apache.cxf.cxf-core [53]
>   Unresolved requirement: Import-Package: com.ctc.wstx.msv; 
> version="[4.4.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.ctc.wstx.stax; 
> version="[4.4.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.codehaus.stax2; 
> version="[3.1.0,4.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.codehaus.stax2.validation; 
> version="[3.1.0,4.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.grammar; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.grammar.xmlschema; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.reader; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.msv.reader.xmlschema; 
> version="[2013.6.0,2014.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.xml.bind.marshaller; 
> version="[2.2.0,3.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: com.sun.xml.fastinfoset.stax; 
> version="[1.2.0,2.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: net.sf.cglib.proxy; 
> version="[2.1.3,3.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.osgi.io; 
> version="[1.2.0,2.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.osgi.util; 
> version="[1.2.0,2.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.aop; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.aop.framework; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.aop.support; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.beans; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.beans.factory; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.config; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.support; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.wiring; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.beans.factory.xml; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.context; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.context.event; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.context.support; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.core; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.core.io; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> org.springframework.core.io.support; version="[3.1.0,5.0.0)"; 
> resolution:="optional"
>   Unresolved requirement: Import-Package: org.springframework.core.type; 
> version="[3.1.0,5.0.0)"; resolution:="optional"
>   Unresolved requirement: Import-Package: 
> 

[jira] [Updated] (KARAF-4192) java.lang.ClassCastException in org.apache.karaf.features.internal.region.CandidateComparator

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4192:

Fix Version/s: (was: 4.0.5)
   4.0.6

> java.lang.ClassCastException in 
> org.apache.karaf.features.internal.region.CandidateComparator
> -
>
> Key: KARAF-4192
> URL: https://issues.apache.org/jira/browse/KARAF-4192
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Per Kristian Söreide
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> The system bundle will return a String[] {"org.apache.felix.framework", 
> "system.bundle"} on line 57 in CandidateComparator:
> {noformat}
> c = ((Comparable) 
> cap1.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE))
> 
> .compareTo(cap2.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE));{noformat}
> This is causing a ClassCastException being thrown.
> Equinox will return an ArrayList (seen in the stacktrace)
> Stacktrace:
> {noformat}
> java.lang.ClassCastException: java.util.ArrayList cannot be cast to 
> java.lang.Comparable
>   at 
> org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:57)
>   at 
> org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:31)
>   at java.util.TimSort.binarySort(TimSort.java:265)
>   at java.util.TimSort.sort(TimSort.java:208)
>   at java.util.TimSort.sort(TimSort.java:173)
>   at java.util.Arrays.sort(Arrays.java:659)
>   at java.util.Collections.sort(Collections.java:217)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:260)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:272)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> 

[jira] [Updated] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4260:

Fix Version/s: (was: 4.0.5)
   4.0.6

> Setting karaf.clean.all = true breaks service wrapper service script
> 
>
> Key: KARAF-4260
> URL: https://issues.apache.org/jira/browse/KARAF-4260
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> The Karaf service wrapper script is generated such that the PID file is 
> created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then 
> the PID file created by the service script gets deleted together with the 
> data directory. As a result of this the service script reports Karaf as not 
> running and it is not possible to stop the process via the script.
> The PID file location probably should be outside the data directory by 
> default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4280) Feature config overwrites existing values

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220876#comment-15220876
 ] 

ASF subversion and git services commented on KARAF-4280:


Commit 7fb258ab571f2c722e0a727678241531a3933c04 in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7fb258a ]

KARAF-4280 - In case of update, use the actual property for the storage


> Feature config overwrites existing values
> -
>
> Key: KARAF-4280
> URL: https://issues.apache.org/jira/browse/KARAF-4280
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config, karaf-feature
>Affects Versions: 4.0.4
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The feature configuration (KARAF-3100) seems to have conflicting rules when 
> appending new feature configuration values to an existing configuration. If 
> the feature file contains a new config key, then all values are taken from 
> the feature config keys. But the code before it puts only new values to 
> component configuration.
> So the FeatureConfigInstaller flow is:
> 1.   installFeatureConfigs uses existing values and only appends new ones 
> (lines 114-118)
> 2.   updateStorage overwrites all values from the ones in feature 
> configuration (lines 266-275)
> I think this is a bug: it seems that the intention is to keep the existing 
> configuration as is and only append new values. Which makes more sense to me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4280) Feature config overwrites existing values

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4280.
-
Resolution: Fixed

> Feature config overwrites existing values
> -
>
> Key: KARAF-4280
> URL: https://issues.apache.org/jira/browse/KARAF-4280
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config, karaf-feature
>Affects Versions: 4.0.4
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The feature configuration (KARAF-3100) seems to have conflicting rules when 
> appending new feature configuration values to an existing configuration. If 
> the feature file contains a new config key, then all values are taken from 
> the feature config keys. But the code before it puts only new values to 
> component configuration.
> So the FeatureConfigInstaller flow is:
> 1.   installFeatureConfigs uses existing values and only appends new ones 
> (lines 114-118)
> 2.   updateStorage overwrites all values from the ones in feature 
> configuration (lines 266-275)
> I think this is a bug: it seems that the intention is to keep the existing 
> configuration as is and only append new values. Which makes more sense to me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4280) Feature config overwrites existing values

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220855#comment-15220855
 ] 

ASF subversion and git services commented on KARAF-4280:


Commit 522d61b7fda4da44b5bade9ef917826f489c7757 in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=522d61b ]

KARAF-4280 - In case of update, use the actual property for the storage


> Feature config overwrites existing values
> -
>
> Key: KARAF-4280
> URL: https://issues.apache.org/jira/browse/KARAF-4280
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config, karaf-feature
>Affects Versions: 4.0.4
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The feature configuration (KARAF-3100) seems to have conflicting rules when 
> appending new feature configuration values to an existing configuration. If 
> the feature file contains a new config key, then all values are taken from 
> the feature config keys. But the code before it puts only new values to 
> component configuration.
> So the FeatureConfigInstaller flow is:
> 1.   installFeatureConfigs uses existing values and only appends new ones 
> (lines 114-118)
> 2.   updateStorage overwrites all values from the ones in feature 
> configuration (lines 266-275)
> I think this is a bug: it seems that the intention is to keep the existing 
> configuration as is and only append new values. Which makes more sense to me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (KARAF-4280) Feature config overwrites existing values

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on KARAF-4280 started by Jean-Baptiste Onofré.
---
> Feature config overwrites existing values
> -
>
> Key: KARAF-4280
> URL: https://issues.apache.org/jira/browse/KARAF-4280
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config, karaf-feature
>Affects Versions: 4.0.4
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The feature configuration (KARAF-3100) seems to have conflicting rules when 
> appending new feature configuration values to an existing configuration. If 
> the feature file contains a new config key, then all values are taken from 
> the feature config keys. But the code before it puts only new values to 
> component configuration.
> So the FeatureConfigInstaller flow is:
> 1.   installFeatureConfigs uses existing values and only appends new ones 
> (lines 114-118)
> 2.   updateStorage overwrites all values from the ones in feature 
> configuration (lines 266-275)
> I think this is a bug: it seems that the intention is to keep the existing 
> configuration as is and only append new values. Which makes more sense to me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (KARAF-4443) Create default dahboards in Decanter Kibana 4.x

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reopened KARAF-4443:
-

The current approach is not efficient: we can do much better.

The Kibana 4 feature can install a bundle acting as a FeatureListener: when a 
decanter collector is installed/started, the bundle can automatically push the 
corresponding dashboards into elasticsearch.
Similarly when this bundle starts, it can also automatically create the default 
configuration with the index in elasticsearch.

> Create default dahboards in Decanter Kibana 4.x
> ---
>
> Key: KARAF-4443
> URL: https://issues.apache.org/jira/browse/KARAF-4443
> Project: Karaf
>  Issue Type: New Feature
>  Components: decanter
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: decanter-1.1.0
>
>
> As we do in Decanter Kibana 3.x, we should provide "out of the box" 
> dashboards in Decanter Kibana 4.x.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4109) For backward compatibility, support the resolver attribute in features XML

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4109:

Fix Version/s: (was: 4.0.5)
   4.0.6

> For backward compatibility, support the resolver attribute in features XML
> --
>
> Key: KARAF-4109
> URL: https://issues.apache.org/jira/browse/KARAF-4109
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-archetypes, karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> The resolver attribute in features XML is not supported anymore throwing 
> errors at installation time.
> We have to:
> 1. fix the feature archetype to remove the reference to the resolver attribute
> 2. for backward compatibility, it makes sense to support the resolver 
> attribute even if we don't really use it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4311) karaf maven plugin does not respect -s setting on maven

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220384#comment-15220384
 ] 

ASF subversion and git services commented on KARAF-4311:


Commit 0475a016244dd0104926710fcb284d0562d6a460 in karaf's branch 
refs/heads/karaf-4.0.x from [~slawekjaranowski]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0475a01 ]

[KARAF-4311] propagate current maven settings to to pax.MavenResolver


> karaf maven plugin does not respect -s setting on maven
> ---
>
> Key: KARAF-4311
> URL: https://issues.apache.org/jira/browse/KARAF-4311
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Raman Gupta
>Assignee: Jean-Baptiste Onofré
>  Labels: maven
> Fix For: 4.1.0, 4.0.5
>
>
> The karaf maven plugin uses the pax maven resolver for some things, like 
> verification for example.
> However, mvn has the -s switch to specify a particular settings.xml at build 
> time, which is often used by CI systems. Since the karaf-maven-plugin is 
> running from a maven command, it should call or configure pax so that it uses 
> the settings.xml specified by the user at the command line, if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220385#comment-15220385
 ] 

ASF subversion and git services commented on KARAF-4415:


Commit f2a5c4b5de271331d5d4fcc4363b73299a7949a0 in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f2a5c4b ]

KARAF-4415 - Update the documentation about the verify goal


> karaf-maven-plugin - The feature validate goal is missing
> -
>
> Key: KARAF-4415
> URL: https://issues.apache.org/jira/browse/KARAF-4415
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> According to this guide
> http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin-features-validate-descriptor.html
> You can run this goal to validate your features file, which we do at Apache 
> Camel. But we have been using the older Karaf 2.x plugin to do that. But when 
> upgrading to 4.x the goal is missing.
> {code}
> davsclaus:~/workspace/camel/platforms/karaf/features (master)/$ mvn -Pvalidate
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Camel :: Platforms :: Apache Karaf :: Features 2.17-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.038 s
> [INFO] Finished at: 2016-03-13T09:23:21+01:00
> [INFO] Final Memory: 12M/155M
> [INFO] 
> 
> [ERROR] Could not find goal 'features-validate-descriptor' in plugin 
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.3 among available goals 
> archive, assembly, commands-generate-help, features-add-to-repository, 
> features-export-meta-data, features-generate-descriptor, kar, verify -> [Help 
> 1]
> {code}
> When using
> {code}
>   
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.3
> 
>   
> 
>   
> 
>   
> 
> 
>   
> validate
> process-resources
> 
>   features-validate-descriptor
> 
>   
> 
> 
>   
> org.apache.maven.wagon
> wagon-http-lightweight
> 2.6
>   
>
>   
> {code}
> Where is that goal or has it been removed entirely?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4415.
-
Resolution: Fixed

> karaf-maven-plugin - The feature validate goal is missing
> -
>
> Key: KARAF-4415
> URL: https://issues.apache.org/jira/browse/KARAF-4415
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> According to this guide
> http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin-features-validate-descriptor.html
> You can run this goal to validate your features file, which we do at Apache 
> Camel. But we have been using the older Karaf 2.x plugin to do that. But when 
> upgrading to 4.x the goal is missing.
> {code}
> davsclaus:~/workspace/camel/platforms/karaf/features (master)/$ mvn -Pvalidate
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Camel :: Platforms :: Apache Karaf :: Features 2.17-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.038 s
> [INFO] Finished at: 2016-03-13T09:23:21+01:00
> [INFO] Final Memory: 12M/155M
> [INFO] 
> 
> [ERROR] Could not find goal 'features-validate-descriptor' in plugin 
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.3 among available goals 
> archive, assembly, commands-generate-help, features-add-to-repository, 
> features-export-meta-data, features-generate-descriptor, kar, verify -> [Help 
> 1]
> {code}
> When using
> {code}
>   
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.3
> 
>   
> 
>   
> 
>   
> 
> 
>   
> validate
> process-resources
> 
>   features-validate-descriptor
> 
>   
> 
> 
>   
> org.apache.maven.wagon
> wagon-http-lightweight
> 2.6
>   
>
>   
> {code}
> Where is that goal or has it been removed entirely?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4311) karaf maven plugin does not respect -s setting on maven

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4311.
-
Resolution: Fixed

> karaf maven plugin does not respect -s setting on maven
> ---
>
> Key: KARAF-4311
> URL: https://issues.apache.org/jira/browse/KARAF-4311
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Raman Gupta
>Assignee: Jean-Baptiste Onofré
>  Labels: maven
> Fix For: 4.1.0, 4.0.5
>
>
> The karaf maven plugin uses the pax maven resolver for some things, like 
> verification for example.
> However, mvn has the -s switch to specify a particular settings.xml at build 
> time, which is often used by CI systems. Since the karaf-maven-plugin is 
> running from a maven command, it should call or configure pax so that it uses 
> the settings.xml specified by the user at the command line, if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4311) karaf maven plugin does not respect -s setting on maven

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220379#comment-15220379
 ] 

ASF subversion and git services commented on KARAF-4311:


Commit e577d629a480ee506bf7a92939ea5c8a380f686d in karaf's branch 
refs/heads/master from [~slawekjaranowski]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e577d62 ]

[KARAF-4311] propagate current maven settings to to pax.MavenResolver


> karaf maven plugin does not respect -s setting on maven
> ---
>
> Key: KARAF-4311
> URL: https://issues.apache.org/jira/browse/KARAF-4311
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Raman Gupta
>Assignee: Jean-Baptiste Onofré
>  Labels: maven
> Fix For: 4.1.0, 4.0.5
>
>
> The karaf maven plugin uses the pax maven resolver for some things, like 
> verification for example.
> However, mvn has the -s switch to specify a particular settings.xml at build 
> time, which is often used by CI systems. Since the karaf-maven-plugin is 
> running from a maven command, it should call or configure pax so that it uses 
> the settings.xml specified by the user at the command line, if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4311) karaf maven plugin does not respect -s setting on maven

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220382#comment-15220382
 ] 

ASF GitHub Bot commented on KARAF-4311:
---

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/163


> karaf maven plugin does not respect -s setting on maven
> ---
>
> Key: KARAF-4311
> URL: https://issues.apache.org/jira/browse/KARAF-4311
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Raman Gupta
>Assignee: Jean-Baptiste Onofré
>  Labels: maven
> Fix For: 4.1.0, 4.0.5
>
>
> The karaf maven plugin uses the pax maven resolver for some things, like 
> verification for example.
> However, mvn has the -s switch to specify a particular settings.xml at build 
> time, which is often used by CI systems. Since the karaf-maven-plugin is 
> running from a maven command, it should call or configure pax so that it uses 
> the settings.xml specified by the user at the command line, if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220381#comment-15220381
 ] 

ASF subversion and git services commented on KARAF-4415:


Commit ac5f52ee16ab155a8ff6fd9cb2c4b11e5fa647ee in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=ac5f52e ]

KARAF-4415 - Update the documentation about the verify goal


> karaf-maven-plugin - The feature validate goal is missing
> -
>
> Key: KARAF-4415
> URL: https://issues.apache.org/jira/browse/KARAF-4415
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> According to this guide
> http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin-features-validate-descriptor.html
> You can run this goal to validate your features file, which we do at Apache 
> Camel. But we have been using the older Karaf 2.x plugin to do that. But when 
> upgrading to 4.x the goal is missing.
> {code}
> davsclaus:~/workspace/camel/platforms/karaf/features (master)/$ mvn -Pvalidate
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Camel :: Platforms :: Apache Karaf :: Features 2.17-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.038 s
> [INFO] Finished at: 2016-03-13T09:23:21+01:00
> [INFO] Final Memory: 12M/155M
> [INFO] 
> 
> [ERROR] Could not find goal 'features-validate-descriptor' in plugin 
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.3 among available goals 
> archive, assembly, commands-generate-help, features-add-to-repository, 
> features-export-meta-data, features-generate-descriptor, kar, verify -> [Help 
> 1]
> {code}
> When using
> {code}
>   
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.3
> 
>   
> 
>   
> 
>   
> 
> 
>   
> validate
> process-resources
> 
>   features-validate-descriptor
> 
>   
> 
> 
>   
> org.apache.maven.wagon
> wagon-http-lightweight
> 2.6
>   
>
>   
> {code}
> Where is that goal or has it been removed entirely?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4311) karaf maven plugin does not respect -s setting on maven

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220380#comment-15220380
 ] 

ASF subversion and git services commented on KARAF-4311:


Commit 7be3611c80271013d2186c18d652050b412d197c in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7be3611 ]

Merge branch 'KARAF-4311' of https://github.com/slawekjaranowski/karaf


> karaf maven plugin does not respect -s setting on maven
> ---
>
> Key: KARAF-4311
> URL: https://issues.apache.org/jira/browse/KARAF-4311
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Raman Gupta
>Assignee: Jean-Baptiste Onofré
>  Labels: maven
> Fix For: 4.1.0, 4.0.5
>
>
> The karaf maven plugin uses the pax maven resolver for some things, like 
> verification for example.
> However, mvn has the -s switch to specify a particular settings.xml at build 
> time, which is often used by CI systems. Since the karaf-maven-plugin is 
> running from a maven command, it should call or configure pax so that it uses 
> the settings.xml specified by the user at the command line, if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on KARAF-4415 started by Jean-Baptiste Onofré.
---
> karaf-maven-plugin - The feature validate goal is missing
> -
>
> Key: KARAF-4415
> URL: https://issues.apache.org/jira/browse/KARAF-4415
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> According to this guide
> http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin-features-validate-descriptor.html
> You can run this goal to validate your features file, which we do at Apache 
> Camel. But we have been using the older Karaf 2.x plugin to do that. But when 
> upgrading to 4.x the goal is missing.
> {code}
> davsclaus:~/workspace/camel/platforms/karaf/features (master)/$ mvn -Pvalidate
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Camel :: Platforms :: Apache Karaf :: Features 2.17-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.038 s
> [INFO] Finished at: 2016-03-13T09:23:21+01:00
> [INFO] Final Memory: 12M/155M
> [INFO] 
> 
> [ERROR] Could not find goal 'features-validate-descriptor' in plugin 
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.3 among available goals 
> archive, assembly, commands-generate-help, features-add-to-repository, 
> features-export-meta-data, features-generate-descriptor, kar, verify -> [Help 
> 1]
> {code}
> When using
> {code}
>   
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.3
> 
>   
> 
>   
> 
>   
> 
> 
>   
> validate
> process-resources
> 
>   features-validate-descriptor
> 
>   
> 
> 
>   
> org.apache.maven.wagon
> wagon-http-lightweight
> 2.6
>   
>
>   
> {code}
> Where is that goal or has it been removed entirely?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220357#comment-15220357
 ] 

Jean-Baptiste Onofré commented on KARAF-4415:
-

Agree, I'm updating the documentation.

> karaf-maven-plugin - The feature validate goal is missing
> -
>
> Key: KARAF-4415
> URL: https://issues.apache.org/jira/browse/KARAF-4415
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> According to this guide
> http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin-features-validate-descriptor.html
> You can run this goal to validate your features file, which we do at Apache 
> Camel. But we have been using the older Karaf 2.x plugin to do that. But when 
> upgrading to 4.x the goal is missing.
> {code}
> davsclaus:~/workspace/camel/platforms/karaf/features (master)/$ mvn -Pvalidate
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Camel :: Platforms :: Apache Karaf :: Features 2.17-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.038 s
> [INFO] Finished at: 2016-03-13T09:23:21+01:00
> [INFO] Final Memory: 12M/155M
> [INFO] 
> 
> [ERROR] Could not find goal 'features-validate-descriptor' in plugin 
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.3 among available goals 
> archive, assembly, commands-generate-help, features-add-to-repository, 
> features-export-meta-data, features-generate-descriptor, kar, verify -> [Help 
> 1]
> {code}
> When using
> {code}
>   
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.3
> 
>   
> 
>   
> 
>   
> 
> 
>   
> validate
> process-resources
> 
>   features-validate-descriptor
> 
>   
> 
> 
>   
> org.apache.maven.wagon
> wagon-http-lightweight
> 2.6
>   
>
>   
> {code}
> Where is that goal or has it been removed entirely?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4314) karaf-maven-plugin issue when parsing feature xmls with entries that contain a newline and/or whitespaces

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4314:

Fix Version/s: (was: 4.0.5)
   4.0.6

> karaf-maven-plugin issue when parsing feature xmls with  entries 
> that contain a newline and/or whitespaces
> --
>
> Key: KARAF-4314
> URL: https://issues.apache.org/jira/browse/KARAF-4314
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Andy Schmidt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> The karaf-maven-plugin (tested with 4.0.3 and 4.0.4) has an issue when 
> parsing feature xmls with  entries that contain a newline and/or 
> whitespaces.
> Having an (eclipse auto-formatted) entry like
> mvn:org.apache.karaf.features/enterprise/${karaf.version}/xml/features
>   
> causes the plugin to try and create a lock file with the name  maven-repository>\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features.xml.part.lock
> which in turn causes the following exception to be thrown:
> shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
> transfer artifact org.apache.karaf.features:enterprise:xml:features
> :4.0.4 from/to maven-srv 
> (http://maven-srv:8080/nexus/content/groups/kisters-central/): 
> C:\Users\jfrank\.m2\repository\org\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features
> .xml.part.lock (Die Syntax f▒r den Dateinamen, Verzeichnisnamen oder 
> die Datentr▒gerbezeichnung ist falsch)
> 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:615)
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:570)
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:548)
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:523)
> 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:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: shaded.org.eclipse.aether.transfer.ArtifactTransferException: 
> Could not transfer artifact org.apache.karaf.features:enterprise:xml:features
> :4.0.4 from/to maven-srv 
> (http://maven-srv:8080/nexus/content/groups/kisters-central/): 
> C:\Users\jfrank\.m2\repository\org\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features
> .xml.part.lock (Die Syntax f▒r den Dateinamen, Verzeichnisnamen oder 
> die Datentr▒gerbezeichnung ist falsch)
> at 
> shaded.org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)
> at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
> at 
> shaded.org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
> at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)
> at 
> shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
> at 
> 

[jira] [Updated] (KARAF-4314) karaf-maven-plugin issue when parsing feature xmls with entries that contain a newline and/or whitespaces

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4314:

Priority: Minor  (was: Major)

> karaf-maven-plugin issue when parsing feature xmls with  entries 
> that contain a newline and/or whitespaces
> --
>
> Key: KARAF-4314
> URL: https://issues.apache.org/jira/browse/KARAF-4314
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Andy Schmidt
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> The karaf-maven-plugin (tested with 4.0.3 and 4.0.4) has an issue when 
> parsing feature xmls with  entries that contain a newline and/or 
> whitespaces.
> Having an (eclipse auto-formatted) entry like
> mvn:org.apache.karaf.features/enterprise/${karaf.version}/xml/features
>   
> causes the plugin to try and create a lock file with the name  maven-repository>\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features.xml.part.lock
> which in turn causes the following exception to be thrown:
> shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
> transfer artifact org.apache.karaf.features:enterprise:xml:features
> :4.0.4 from/to maven-srv 
> (http://maven-srv:8080/nexus/content/groups/kisters-central/): 
> C:\Users\jfrank\.m2\repository\org\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features
> .xml.part.lock (Die Syntax f▒r den Dateinamen, Verzeichnisnamen oder 
> die Datentr▒gerbezeichnung ist falsch)
> 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:615)
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:570)
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:548)
> at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:523)
> 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:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: shaded.org.eclipse.aether.transfer.ArtifactTransferException: 
> Could not transfer artifact org.apache.karaf.features:enterprise:xml:features
> :4.0.4 from/to maven-srv 
> (http://maven-srv:8080/nexus/content/groups/kisters-central/): 
> C:\Users\jfrank\.m2\repository\org\apache\karaf\features\enterprise\4.0.4\enterprise-4.0.4-features
> .xml.part.lock (Die Syntax f▒r den Dateinamen, Verzeichnisnamen oder 
> die Datentr▒gerbezeichnung ist falsch)
> at 
> shaded.org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)
> at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
> at 
> shaded.org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
> at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)
> at 
> shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
> at 
> 

[jira] [Commented] (KARAF-4147) karaf-maven-plugin: Add description of configuration property "libraries"

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220344#comment-15220344
 ] 

ASF subversion and git services commented on KARAF-4147:


Commit 855e082b00080a26b988c325b5647205f7c60450 in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=855e082 ]

KARAF-4147 - Add note about  element


> karaf-maven-plugin: Add description of configuration property "libraries"
> -
>
> Key: KARAF-4147
> URL: https://issues.apache.org/jira/browse/KARAF-4147
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.3
>Reporter: Jochen Kraushaar
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> When I upgraded my Karaf 3.0.3 Assembly to Karaf 4.0.3, I had problems to 
> install libraries to the lib/endorsed directory. After some digging through 
> the code, I found the "libraries" configuration property, which does exactly 
> what I was looking for. It took me even more time to figure out how it works.
> It would be nice, if the description of this property is added to the 
> http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
>  manual.
> For those, who have the same problem an example: To install a PostgreSQL 
> driver at lib/endorsed, add the following configuration entry at your 
> karaf-maven-plugin definition:
> {code}
> 
> 
> mvn:org.postgresql/postgresql/9.3-1102-jdbc41;type:=endorsed
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4290) karaf-maven-plugin uses inactive proxies from settings.xml

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4290:

Fix Version/s: (was: 4.0.5)
   4.0.6

> karaf-maven-plugin uses inactive proxies from settings.xml
> --
>
> Key: KARAF-4290
> URL: https://issues.apache.org/jira/browse/KARAF-4290
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Michael Prescott
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
> Attachments: karaf-4290-stack-trace.txt
>
>
> My maven settings.xml has a  server defined, but it's inactive:
> 
>   charles-proxy
>   false
>   http
>   localhost
>   
>   www.google.com|*.example.com
> 
> Nevertheless, when runs, I get IOExceptions related to attempting to contact 
> the proxy server (which isn't running):
> Connect to localhost: [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] 
> failed: Connection refused: connect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4147) karaf-maven-plugin: Add description of configuration property "libraries"

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4147.
-
Resolution: Fixed

> karaf-maven-plugin: Add description of configuration property "libraries"
> -
>
> Key: KARAF-4147
> URL: https://issues.apache.org/jira/browse/KARAF-4147
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.3
>Reporter: Jochen Kraushaar
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> When I upgraded my Karaf 3.0.3 Assembly to Karaf 4.0.3, I had problems to 
> install libraries to the lib/endorsed directory. After some digging through 
> the code, I found the "libraries" configuration property, which does exactly 
> what I was looking for. It took me even more time to figure out how it works.
> It would be nice, if the description of this property is added to the 
> http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
>  manual.
> For those, who have the same problem an example: To install a PostgreSQL 
> driver at lib/endorsed, add the following configuration entry at your 
> karaf-maven-plugin definition:
> {code}
> 
> 
> mvn:org.postgresql/postgresql/9.3-1102-jdbc41;type:=endorsed
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4147) karaf-maven-plugin: Add description of configuration property "libraries"

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220343#comment-15220343
 ] 

ASF subversion and git services commented on KARAF-4147:


Commit f33bc0925c54dc795f6f64a5b88bae81c8f5f9a3 in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f33bc09 ]

KARAF-4147 - Add note about  element


> karaf-maven-plugin: Add description of configuration property "libraries"
> -
>
> Key: KARAF-4147
> URL: https://issues.apache.org/jira/browse/KARAF-4147
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.3
>Reporter: Jochen Kraushaar
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> When I upgraded my Karaf 3.0.3 Assembly to Karaf 4.0.3, I had problems to 
> install libraries to the lib/endorsed directory. After some digging through 
> the code, I found the "libraries" configuration property, which does exactly 
> what I was looking for. It took me even more time to figure out how it works.
> It would be nice, if the description of this property is added to the 
> http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
>  manual.
> For those, who have the same problem an example: To install a PostgreSQL 
> driver at lib/endorsed, add the following configuration entry at your 
> karaf-maven-plugin definition:
> {code}
> 
> 
> mvn:org.postgresql/postgresql/9.3-1102-jdbc41;type:=endorsed
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4124) feature config installer adds property to config

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4124:

Fix Version/s: (was: 4.0.5)
   4.0.6

> feature config installer adds property to config
> 
>
> Key: KARAF-4124
> URL: https://issues.apache.org/jira/browse/KARAF-4124
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> The  element in a feature XML allows a feature to create and/or 
> populate a configuration (identified by a configuration PID).
> The "FeatureConfigInstaller" adds a custom property to the configuration.
> key = "org.apache.karaf.features.configKey"
> value = result of function call "createConfigurationKey(pid[0], pid[1])"
> There are bundles that cannot handle additional properties in the 
> configuration.
> For example:
> * using Aries JPA + Hiberante + h2
> * the configuration is installed by a feature and a realted config entry
> * this will result in a non working setup
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting 
> "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at 
> org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266)
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90)
> at org.h2.Driver.connect(Driver.java:73)
> at 
> org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187)
> at 
> org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323)
> at 
> org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112)
> at 
> org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at 
> org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127)
> ... 132 more
> {noformat}
> There is a conditional branch in the "findExistingConfiguration" function to 
> filter (find) the configuration using that property instead of the 
> service.pid (this is another conditional branch).
> Is there any reason for using that property?
> I changed the "FeatureConfigInstaller" to not append that property and the 
> above example is working now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4124) feature config installer adds property to config

[JIRA]

[ 
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220325#comment-15220325
 ] 

Jean-Baptiste Onofré commented on KARAF-4124:
-

The org.apache.karaf.features.configKey property is used by the features 
service only in the case of configuration factory to avoid to create bunch of 
configuration (as some application may create a lot).

I think that Pax JDBC should ignore this key. I would consider more an 
enhancement/fix on Pax JDBC more than in Karaf.

> feature config installer adds property to config
> 
>
> Key: KARAF-4124
> URL: https://issues.apache.org/jira/browse/KARAF-4124
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> The  element in a feature XML allows a feature to create and/or 
> populate a configuration (identified by a configuration PID).
> The "FeatureConfigInstaller" adds a custom property to the configuration.
> key = "org.apache.karaf.features.configKey"
> value = result of function call "createConfigurationKey(pid[0], pid[1])"
> There are bundles that cannot handle additional properties in the 
> configuration.
> For example:
> * using Aries JPA + Hiberante + h2
> * the configuration is installed by a feature and a realted config entry
> * this will result in a non working setup
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting 
> "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at 
> org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266)
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90)
> at org.h2.Driver.connect(Driver.java:73)
> at 
> org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187)
> at 
> org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323)
> at 
> org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112)
> at 
> org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at 
> org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127)
> ... 132 more
> {noformat}
> There is a conditional branch in the "findExistingConfiguration" function to 
> filter (find) the configuration using that property instead of the 
> service.pid (this is another conditional branch).
> Is there any reason for using that property?
> I changed the "FeatureConfigInstaller" to not append that property and the 
> above example is working now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4056) Developer-guide/extending: replace mvn archetype:create by generate

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220300#comment-15220300
 ] 

ASF subversion and git services commented on KARAF-4056:


Commit 675112d3450c23dbe4a23d14285398a1dc79d6b8 in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=675112d ]

KARAF-4056 - Use archetype:generate instead of archetype:create (deprecated)


> Developer-guide/extending: replace mvn archetype:create by generate
> ---
>
> Key: KARAF-4056
> URL: https://issues.apache.org/jira/browse/KARAF-4056
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.1, 4.0.2
>Reporter: Arnaud Vandyck
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
>  Labels: documentation
> Fix For: 4.1.0, 4.0.5
>
> Attachments: 
> 0001-KARAF-4056-Developers-guide-extending-use-mvn-archet.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The command mvn archetype:create has been deprecated in favour of mvn 
> archetype:generate.
> See http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4105) karaf-assembly fails when used Maven versions do not match derived OSGi versions

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4105:

Fix Version/s: (was: 4.0.5)
   4.0.6

> karaf-assembly fails when used Maven versions do not match derived OSGi 
> versions
> 
>
> Key: KARAF-4105
> URL: https://issues.apache.org/jira/browse/KARAF-4105
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.3
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> e.g. {{$\{project.version\}}} {{0.1.1-SNAPSHOT}} and {{0.1.1.SNAPSHOT}} do 
> not match in {{org.apache.karaf.profile.assembly.Builder}}
> See mail thread [\[K4.0.3\] custom distribution and 
> kar|http://mail-archives.apache.org/mod_mbox/karaf-user/201511.mbox/%3c7781910.EKNrsAyV2X@madness%3e]
>  for more.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4056) Developer-guide/extending: replace mvn archetype:create by generate

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220301#comment-15220301
 ] 

ASF subversion and git services commented on KARAF-4056:


Commit d3778268c803718b7f7c83a40b2624f057c38fda in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d377826 ]

KARAF-4056 - Use archetype:generate instead of archetype:create (deprecated)


> Developer-guide/extending: replace mvn archetype:create by generate
> ---
>
> Key: KARAF-4056
> URL: https://issues.apache.org/jira/browse/KARAF-4056
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.1, 4.0.2
>Reporter: Arnaud Vandyck
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
>  Labels: documentation
> Fix For: 4.1.0, 4.0.5
>
> Attachments: 
> 0001-KARAF-4056-Developers-guide-extending-use-mvn-archet.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The command mvn archetype:create has been deprecated in favour of mvn 
> archetype:generate.
> See http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4056) Developer-guide/extending: replace mvn archetype:create by generate

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4056.
-
Resolution: Fixed

> Developer-guide/extending: replace mvn archetype:create by generate
> ---
>
> Key: KARAF-4056
> URL: https://issues.apache.org/jira/browse/KARAF-4056
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.1, 4.0.2
>Reporter: Arnaud Vandyck
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
>  Labels: documentation
> Fix For: 4.1.0, 4.0.5
>
> Attachments: 
> 0001-KARAF-4056-Developers-guide-extending-use-mvn-archet.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The command mvn archetype:create has been deprecated in favour of mvn 
> archetype:generate.
> See http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4343) Upgrade to Xalan 2.7.2_3

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4343.
-
Resolution: Fixed

> Upgrade to Xalan 2.7.2_3
> 
>
> Key: KARAF-4343
> URL: https://issues.apache.org/jira/browse/KARAF-4343
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 3.0.5, 2.4.4, 4.0.4
>Reporter: Tadayoshi Sato
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5, 3.0.7
>
>
> Xalan ServiceMix bundle 2.7.2_3 will be released in March 2016, which should 
> include the bug fix SM-2880.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4343) Upgrade to Xalan 2.7.2_3

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220287#comment-15220287
 ] 

ASF subversion and git services commented on KARAF-4343:


Commit 0e88a2932b688329ecb17df605880536cffc195d in karaf's branch 
refs/heads/karaf-3.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0e88a29 ]

[KARAF-4343] Upgrade to Xalan 2.7.2_3


> Upgrade to Xalan 2.7.2_3
> 
>
> Key: KARAF-4343
> URL: https://issues.apache.org/jira/browse/KARAF-4343
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 3.0.5, 2.4.4, 4.0.4
>Reporter: Tadayoshi Sato
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5, 3.0.7
>
>
> Xalan ServiceMix bundle 2.7.2_3 will be released in March 2016, which should 
> include the bug fix SM-2880.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4343) Upgrade to Xalan 2.7.2_3

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KARAF-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220243#comment-15220243
 ] 

ASF subversion and git services commented on KARAF-4343:


Commit 392d04c9c1a090c85aa97b876a22359c10ce494a in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=392d04c ]

KARAF-4343 - Upgrade to Xalan 2.7.2_3


> Upgrade to Xalan 2.7.2_3
> 
>
> Key: KARAF-4343
> URL: https://issues.apache.org/jira/browse/KARAF-4343
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 3.0.5, 2.4.4, 4.0.4
>Reporter: Tadayoshi Sato
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5, 3.0.7
>
>
> Xalan ServiceMix bundle 2.7.2_3 will be released in March 2016, which should 
> include the bug fix SM-2880.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3518) JDK9: endorsed directories not working any longer

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3518:

Fix Version/s: 4.1.0

> JDK9: endorsed directories not working any longer
> -
>
> Key: KARAF-3518
> URL: https://issues.apache.org/jira/browse/KARAF-3518
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core, karaf-os-integration
>Affects Versions: 4.0.0.M3
> Environment: OS X, 
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b49)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b49, mixed mode)
>Reporter: Achim Nierbeck
>  Labels: java9
> Fix For: 4.1.0
>
>
> following message is caught with JDK 1.9: 
> {code}
> -Djava.endorsed.dirs=/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/jre/lib/endorsed:/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/lib/endorsed:/Users/anierbeck/Development/server/apache-karaf-4.0.0.M2/lib/endorsed
>  is not supported. Endorsed standards and standalone APIs
> in modular form will be supported via the concept of upgradeable modules.
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3748) Installing activemq-blueprint feature sometimes fails with uses constraint violation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3748:

Fix Version/s: 4.0.6
   4.1.0

> Installing activemq-blueprint feature sometimes fails with uses constraint 
> violation
> 
>
> Key: KARAF-3748
> URL: https://issues.apache.org/jira/browse/KARAF-3748
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.0.M3
>Reporter: Achim Finke
> Fix For: 4.1.0, 4.0.6
>
>
> From time to time you get the following exception when installing 
> activemq-blueprint feature. 
> {code}
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. 
> Unable to resolve resource org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.11.1] because it is exposed to 
> package 'org.apache.aries.blueprint' from resources 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] and 
> org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] via 
> two dependency chains.
> Chain 1:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import: 
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package: org.apache.aries.blueprint
>   org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
> Chain 2:
>   org.apache.activemq.activemq-blueprint 
> [org.apache.activemq.activemq-blueprint/5.11.1]
> import: 
> (&(osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version>=3.13.0)(!(version>=4.0.0)))
>  |
> export: osgi.wiring.package=org.apache.xbean.blueprint.context.impl; 
> uses:=org.apache.aries.blueprint
>   org.apache.xbean.blueprint [org.apache.xbean.blueprint/3.18.0]
> import: 
> (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package: org.apache.aries.blueprint
>   org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
>   at 
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1410)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:289)[org.apache.felix.framework-5.0.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:185)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:261)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1061)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:960)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> {code}
> The behaviour is not predictable. Installation worked x times, afterwards 
> installation failed y times so you may need some trys to reproduce.
> To reproduce execute:
> {code}
> feature:repo-add activemq 5.11.1
> feature:install activemq-blueprint
> {code}
> if you don't get the exception stop the container, delete data folder and try 
> again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3779) Be able to define the copied location of the kar files

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3779:

Fix Version/s: 4.0.6
   4.1.0

> Be able to define the copied location of the kar files
> --
>
> Key: KARAF-3779
> URL: https://issues.apache.org/jira/browse/KARAF-3779
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-kar
>Affects Versions: 2.3.8, 3.0.4, 4.0.0, 2.4.3
>Reporter: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> On Karaf 2.3.x, the kar files are copied into the system folder. It would be 
> great to configure where Karaf copies the kar files (in the kar service 
> blueprint xml) using a property in etc/org.apache.karaf.kar.cfg.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3770) Add support for installing libraries from the features service

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3770:

Fix Version/s: 4.0.6
   4.1.0

> Add support for installing libraries from the features service
> --
>
> Key: KARAF-3770
> URL: https://issues.apache.org/jira/browse/KARAF-3770
> Project: Karaf
>  Issue Type: Improvement
>Affects Versions: 4.0.0.M3
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0, 4.0.6
>
>
> Libraries are currently only supported by the assembly builder.
> CXF in particular requires quite a few libraries to work properly (those are 
> added in the apache-karaf distribution, but not in the minimal one).
> Those libraries should be referenced in the CXF features instead, and the 
> features service should support installing the libraries and restarting the 
> framework. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3810) Feature verify goal fail on Windows (for standard features)

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3810:

Fix Version/s: 4.0.6
   4.1.0

> Feature verify goal fail on Windows (for standard features)
> ---
>
> Key: KARAF-3810
> URL: https://issues.apache.org/jira/browse/KARAF-3810
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.0
>Reporter: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> On Windows, the verify goal fails on some standard features.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-3874) Apparently valid feature.xml results in silent kar install failure

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3874.
-
Resolution: Incomplete

It should work by removing the resolver attribute.

> Apparently valid feature.xml results in silent kar install failure
> --
>
> Key: KARAF-3874
> URL: https://issues.apache.org/jira/browse/KARAF-3874
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
> Attachments: feature.xml, oops.txt
>
>
> Using the karaf-maven-plugin 4.0.0 with kar packaging, I created a kar.
> The kar contains a feature.xml that aggregates the CXF 3.1.1 feature.xml. It 
> contains elements like:
> {code}
> 
> ...
> 
> {code}
> According to the XSD on the web site, this should be OK.
> Unfortunately, schema validation throws on kar:install.
> Extremely unfortunately, kar:install does not print any error, and the kar is 
> 'installed', but none of its features are installed.
> The trouble is only to be seen in the log.
> I will attach the feature.xml and the relevant log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3878) Update and fix documentation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3878:

Fix Version/s: 4.1.0

> Update and fix documentation
> 
>
> Key: KARAF-3878
> URL: https://issues.apache.org/jira/browse/KARAF-3878
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-documentation
>Affects Versions: 4.0.0
>Reporter: Jean-Baptiste Onofré
> Fix For: 4.1.0
>
>
> The dev guide contains not up to date details. For instance:
> * the custom distribution refers to standard feature which doesn't exist 
> anymore
> Regarding the user guide:
> * the jdbc commands have changed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3938) NPE in Felix when installing camel-spark-rest feature

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3938:

Fix Version/s: 4.0.6
   4.1.0

> NPE in Felix when installing camel-spark-rest feature
> -
>
> Key: KARAF-3938
> URL: https://issues.apache.org/jira/browse/KARAF-3938
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Use Java 8
> Install Camel 2.16-SNAPSHOT
> When installing the camel-spark-rest feature you get this NPE
> {code}
> 2015-08-20 07:48:59,907 | ERROR | nsole user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.0.1 | Exception caught while 
> executing command
> java.lang.NullPointerException
>   at 
> org.apache.felix.framework.capabilityset.CapabilitySet.match(CapabilitySet.java:197)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.framework.capabilityset.CapabilitySet.match(CapabilitySet.java:187)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.framework.StatefulResolver.findProvidersInternal(StatefulResolver.java:229)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.framework.ResolveContextImpl.findProviders(ResolveContextImpl.java:89)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:288)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.resolver.Candidates.populate(Candidates.java:177)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:168)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.framework.StatefulResolver.resolve(StatefulResolver.java:431)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.framework.Felix.resolveBundles(Felix.java:4073)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.felix.framework.FrameworkWiringImpl.resolveBundles(FrameworkWiringImpl.java:133)[org.apache.felix.framework-5.0.1.jar:]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.resolveBundles(FeaturesServiceImpl.java:1267)[8:org.apache.karaf.features.core:4.0.1]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:823)[8:org.apache.karaf.features.core:4.0.1]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)[8:org.apache.karaf.features.core:4.0.1]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)[8:org.apache.karaf.features.core:4.0.1]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> karaf@root()> feature:install camel-spark-rest
> Error executing command: java.lang.NullPointerException
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3952) Be able to provide full ObjectName to registerMBean()

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3952:

Fix Version/s: 4.0.6
   4.1.0

> Be able to provide full ObjectName to registerMBean()
> -
>
> Key: KARAF-3952
> URL: https://issues.apache.org/jira/browse/KARAF-3952
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-util
>Affects Versions: 4.0.1
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Karaf util provides the convenient registerMBean() method. However, when you 
> want to provide a full ObjectName, the workaround is to use:
> {code}
> Hashtable props = new Hashtable();
> props.put("jmx.objectname", "org.apache.karaf.cellar:type=core,name=" 
> + System.getProperty("karaf.name"));
> coreMBeanRegistration = 
> bundleContext.registerService(getInterfaceNames(cellarMBean), cellarMBean, 
> props);
> {code}
> To simplify the writing, it would be great that the registerMBean() method 
> accept the complete ObjectName (instead of only type as currently).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3942) Using ' and " symbols with commands completion

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3942:

Fix Version/s: 4.0.6
   4.1.0

> Using ' and " symbols with commands completion
> --
>
> Key: KARAF-3942
> URL: https://issues.apache.org/jira/browse/KARAF-3942
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.1
>Reporter: Pavlo Vasylchenko
> Fix For: 4.1.0, 4.0.6
>
>
> I need to use command completion with parameter, surrounded by quotes.
> But when I type 
> {code}
> test:mycommand ' + TAB 
> {code}
> I will have an exception.
> The same for default commands:
> {code}
> kar:create ‘ + TAB  = Error executing command: String index out of range: 13
> {code}
> If I pass QName without quotes like: 
> {code}
> {http://talend.org/greeter}Greeter
> {code}
> karaf thinks that it is two different arguments 
> {code}
> {http://talend.org/greeter}
> {code} 
> and 
> {code}
> Greeter
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4060) Display a warning when we remove a repo containing installed features

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4060:

Fix Version/s: 4.0.6
   4.1.0

> Display a warning when we remove a repo containing installed features
> -
>
> Key: KARAF-4060
> URL: https://issues.apache.org/jira/browse/KARAF-4060
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> When we add a feature repo, and we install features from this repo, if after 
> that, we remove the repo, the features are not displayed anymore (but the 
> bundles are still installed). It's not obvious for the user in which state 
> the features are.
> We should display a warning when doing feature:repo-remove while we have some 
> features from this repo installed (or even don't allow to remove the repo).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3997) Subsystem feature does not save regions state after install of a subsystem causing a startup issue.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3997:

Fix Version/s: 4.0.6
   4.1.0

> Subsystem feature does not save regions state after install of a subsystem 
> causing a startup issue.
> ---
>
> Key: KARAF-3997
> URL: https://issues.apache.org/jira/browse/KARAF-3997
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.1
> Environment: java 1.7
>Reporter: Bas
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
> Attachments: application.esa, features-core.patch, 
> karaf-subsystem-restart-exception.txt
>
>
> Problem:
> Subsystem feature does not save digraph state after install of a subsystem 
> causing a startup issue showing the exception added as an attachment.
> Reproduce:
> Install karaf 4.0.1
> Install the subsystem feature
> Install the attached application.esa file
> Kill the osgi process (in an ungraceful way like kill -9)
> Startup karaf
> The above is a problem in the way features.core has encapsulated the region 
> bundle and changed the persistence (it is now saved in the file 
> 'digraph.json' which cannot be triggered by the class 
> 'StandardRegionDigraphPersistence'). When the region implementation was an 
> external bundle for karaf, it was possible to gain access to the persistence 
> logic by the use of and access to the class 
> 'StandardRegionDigraphPersistence' and save the file yourself if you changed 
> it. This is not possible anymore in karaf version 4.0.1. We would like to be 
> able to do so.
> The feature.core functionality itself does save the state of the digraph on 
> install of a new feature but in a different file 'digraph.json'.
> The subsystems feature and other features/bundles might want to persist the 
> digraph and get stability on ungraceful shutdowns in the same way as 
> installing a feature.
> I made a patch where I am exporting an interface that can trigger 
> feature.core region persistence logic. It is a workaround for our code that 
> also uses the region functionality. So it is not that I'm advising to do it 
> like this.
> Probably short term the patch could help, or a different solution like change 
> the persistence by making an own version of 'RegionDigraphPersistence'. This 
> class is exposed so others can use it (still there is trouble with the name 
> of the file and access to the bundle where the file is stored).
> Long term, maybe move aries subsystem implementation to the core framework 
> and re-implement features support to use aries subsystems.
> But also aries subsystems has trouble saving the digraph correctly, it is 
> depending on a higher level logic to take that responsibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3976) Broken compatibility with 3.x jdbc DataSources

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3976:

Fix Version/s: 4.0.6
   4.1.0

> Broken compatibility with 3.x jdbc DataSources
> --
>
> Key: KARAF-3976
> URL: https://issues.apache.org/jira/browse/KARAF-3976
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-jdbc
>Affects Versions: 4.0.1
>Reporter: Sergey 
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> 1st of all, current documentaion is wrong, because command names was changed 
> to jdbc:ds-info, for example, but 
> http://karaf.apache.org/manual/latest/users-guide/jdbc.html still contains 
> jdbc:info command names.
> Most important compatibility breaking change was another one: in karaf 3.x I 
> was able to deploy DataSource using spring-dm xml or blueprint, and it was 
> registered as a service and in jndi, and was listed using jdbc:datasources 
> command. Right now no datasources are listed.
> {code}
> karaf@root()> jndi:names
> JNDI Name | Class Name
> --
> osgi:service/jdbc/zeusDataSource  | 
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/arenaDS | 
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/tomsDS  | 
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/cofDS   | 
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/fidbDataSource  | 
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/murexDS | 
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/gpDataSource| 
> org.postgresql.ds.PGPoolingDataSource
> karaf@root()> jdbc:ds-info jdbc/fidbDataSource
> Property   | Value
> -
> driver.version | 1.2.2
> db.version | 10.50.4000
> db.product | Microsoft SQL Server
> url| jdbc:jtds:sqlserver:
> driver.name| jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
> username   | ...
> karaf@root()> jdbc:ds-list
> Name | Product | Version | URL | Status
> ---
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3973) Bundles refresh doesn't work (bundles not resolved)

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3973:

Fix Version/s: 4.0.6
   4.1.0

> Bundles refresh doesn't work (bundles not resolved)
> ---
>
> Key: KARAF-3973
> URL: https://issues.apache.org/jira/browse/KARAF-3973
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.1
>Reporter: Amichai Rothman
>Priority: Critical
> Fix For: 4.1.0, 4.0.6
>
>
> I have a bunch of bundles copied into the deploy folder of a fresh karaf 
> 4.0.1 installation. The first time karaf runs, the bundles are not properly 
> resolved, and apparently this has to do with the order in which they are 
> loaded, i.e. if A depends on B and A is loaded first, then when B is loaded 
> it is properly resolved but A never gets resolved. running the refresh 
> command from console does not help either. However, if karaf itself is 
> restarted, then everything is resolved and activated with no problem.
> In Karaf up to 3.0.3 this was not an issue - the moment B was loaded, even on 
> the first time Karaf is run, A would automatically get resolved/activated as 
> well. on 3.0.4 I get a deadlock on startup, so can't really tell if it works 
> (see KARAF-3941). on 4.0.0 I haven't tried. 4.0.1 is the current reported 
> issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-3989) Manual broken because images can't be loaded.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3989:

Component/s: (was: website)
 karaf-documentation

> Manual broken because images can't be loaded.
> -
>
> Key: KARAF-3989
> URL: https://issues.apache.org/jira/browse/KARAF-3989
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-documentation
>Affects Versions: 4.0.1
>Reporter: Tobias Hochgürtel
>Priority: Minor
>  Labels: documentation
> Fix For: 4.1.0, 4.0.6
>
> Attachments: 2015-09-13 12_31_20-Greenshot.png
>
>
> Webpage: http://karaf.apache.org/index/community/download.html
> - HTML Version of the Manuel can't load the images.
> - PDF Version has also no images.
> I think that the PDF Version is generated from the HTML Version and so this 
> affects also to pdf.
> I reported this as first to Karaf User Mailing List [Karaf 4.0.1 Manual 
> HTML/PDF can not be accessed. (404 
> Error)|http://karaf.922171.n3.nabble.com/Karaf-4-0-1-Manual-HTML-PDF-can-not-be-accessed-404-Error-td4042543.html].
> !2015-09-13 12_31_20-Greenshot.png|title=Screenshot shows the Issue side by 
> side for PDF and HTML Version, width=800!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4056) Developer-guide/extending: replace mvn archetype:create by generate

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4056:

Fix Version/s: 4.0.5
   4.1.0

> Developer-guide/extending: replace mvn archetype:create by generate
> ---
>
> Key: KARAF-4056
> URL: https://issues.apache.org/jira/browse/KARAF-4056
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.1, 4.0.2
>Reporter: Arnaud Vandyck
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
>  Labels: documentation
> Fix For: 4.1.0, 4.0.5
>
> Attachments: 
> 0001-KARAF-4056-Developers-guide-extending-use-mvn-archet.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The command mvn archetype:create has been deprecated in favour of mvn 
> archetype:generate.
> See http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4099) Karaf 4.0.2 with cave 4.0.0: obr:deploy not deploying dependencies

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4099:

Affects Version/s: (was: 4.0.2)
   cave-4.0.0

> Karaf 4.0.2 with cave 4.0.0: obr:deploy not deploying dependencies
> --
>
> Key: KARAF-4099
> URL: https://issues.apache.org/jira/browse/KARAF-4099
> Project: Karaf
>  Issue Type: Bug
>  Components: cave-repository
>Affects Versions: cave-4.0.0
> Environment: Windows 7 with java 1.8 running Karaf 4.0.2 and Cave 
> 4.0.0
>Reporter: Matt Jones
> Fix For: cave-4.0.1
>
>
> Karaf 4.0.2 using a Cave 4.0.0 repository is not installing the dependencies 
> for a bundle.
> Here are the steps to reproduce. When I run this with Karaf 3.0.5 and Cave 
> 3.0.0, it works.
> 1. Install Karaf 4.0.2 
> 2. Ran feature:install obr 
> 3. Ran feature:repo-add 
> mvn:org.apache.karaf.cave/apache-karaf-cave/4.0.0/xml/features 
> 4. Ran feature:install cave-server 
> 5. Created my cave repository: cave:repository-create acct_service 
> 6. Uploaded 3 bundles, 1 implementation bundle, 1 API bundle, and 1 
> additional dependency. 
> 7. Viewed the repository.xml in the cave repository and everything looked 
> good. 
> 8. Ran obr:url-add with the repository.xml 
> 9. Ran obr:url-refresh 
> 10. Ran obr:list. I can see all three bundles. 
> 11. Ran obr:deploy -s com.matt.accountservice.impl (this is the 
> implementation bundle that has the two other dependencies) 
> The obr:deploy command fails and gives me a message that I have unsatified 
> requirements. The two requirements that are missing show when I run the 
> obr:list command. 
> When I run obr:resolve, I get the following error in the logs:
> java.lang.IllegalArgumentException 
> at 
> org.apache.felix.bundlerepository.impl.RequirementImpl.setFilter(RequirementImpl.java:101)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.bundlerepository.impl.DataModelHelperImpl.requirement(DataModelHelperImpl.java:72)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.karaf.obr.command.ObrCommandSupport.parseRequirement(ObrCommandSupport.java:211)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.obr.command.ObrCommandSupport.parseRequirements(ObrCommandSupport.java:217)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.obr.command.ResolveCommand.doExecute(ResolveCommand.java:69)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.obr.command.ObrCommandSupport.execute(ObrCommandSupport.java:58)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:268)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_60] 
> Caused by: org.osgi.framework.InvalidSyntaxException: Invalid operator: ): 
> (com.matt.accountservice.impl) 
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse_item(FilterImpl.java:1357)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse_filtercomp(FilterImpl.java:1233)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse_filter(FilterImpl.java:1198)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse(FilterImpl.java:1172)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> 

[jira] [Updated] (KARAF-4099) Karaf 4.0.2 with cave 4.0.0: obr:deploy not deploying dependencies

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4099:

Fix Version/s: cave-4.0.1

> Karaf 4.0.2 with cave 4.0.0: obr:deploy not deploying dependencies
> --
>
> Key: KARAF-4099
> URL: https://issues.apache.org/jira/browse/KARAF-4099
> Project: Karaf
>  Issue Type: Bug
>  Components: cave-repository
>Affects Versions: cave-4.0.0
> Environment: Windows 7 with java 1.8 running Karaf 4.0.2 and Cave 
> 4.0.0
>Reporter: Matt Jones
> Fix For: cave-4.0.1
>
>
> Karaf 4.0.2 using a Cave 4.0.0 repository is not installing the dependencies 
> for a bundle.
> Here are the steps to reproduce. When I run this with Karaf 3.0.5 and Cave 
> 3.0.0, it works.
> 1. Install Karaf 4.0.2 
> 2. Ran feature:install obr 
> 3. Ran feature:repo-add 
> mvn:org.apache.karaf.cave/apache-karaf-cave/4.0.0/xml/features 
> 4. Ran feature:install cave-server 
> 5. Created my cave repository: cave:repository-create acct_service 
> 6. Uploaded 3 bundles, 1 implementation bundle, 1 API bundle, and 1 
> additional dependency. 
> 7. Viewed the repository.xml in the cave repository and everything looked 
> good. 
> 8. Ran obr:url-add with the repository.xml 
> 9. Ran obr:url-refresh 
> 10. Ran obr:list. I can see all three bundles. 
> 11. Ran obr:deploy -s com.matt.accountservice.impl (this is the 
> implementation bundle that has the two other dependencies) 
> The obr:deploy command fails and gives me a message that I have unsatified 
> requirements. The two requirements that are missing show when I run the 
> obr:list command. 
> When I run obr:resolve, I get the following error in the logs:
> java.lang.IllegalArgumentException 
> at 
> org.apache.felix.bundlerepository.impl.RequirementImpl.setFilter(RequirementImpl.java:101)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.bundlerepository.impl.DataModelHelperImpl.requirement(DataModelHelperImpl.java:72)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.karaf.obr.command.ObrCommandSupport.parseRequirement(ObrCommandSupport.java:211)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.obr.command.ObrCommandSupport.parseRequirements(ObrCommandSupport.java:217)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.obr.command.ResolveCommand.doExecute(ResolveCommand.java:69)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.obr.command.ObrCommandSupport.execute(ObrCommandSupport.java:58)[130:org.apache.karaf.obr.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:268)[43:org.apache.karaf.shell.core:4.0.2]
>  
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_60] 
> Caused by: org.osgi.framework.InvalidSyntaxException: Invalid operator: ): 
> (com.matt.accountservice.impl) 
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse_item(FilterImpl.java:1357)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse_filtercomp(FilterImpl.java:1233)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse_filter(FilterImpl.java:1198)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> org.apache.felix.utils.filter.FilterImpl$Parser.parse(FilterImpl.java:1172)[129:org.apache.felix.bundlerepository:2.0.6]
>  
> at 
> 

[jira] [Updated] (KARAF-4084) Only one flag could be used in list command

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4084:

Fix Version/s: 4.0.6
   3.0.7
   4.1.0

> Only one flag could be used in list command
> ---
>
> Key: KARAF-4084
> URL: https://issues.apache.org/jira/browse/KARAF-4084
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 3.0.5, 4.0.2
>Reporter: Sergey 
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> For bundle:list command we have -r to list revisons, -u to list update 
> locations, etc. 
> But why revisions *or* update locations only?
> We can't use -r -u, or even -ru, as it possible for unix-like systems. It 
> should be possible to specify any valid set of flags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4104) NPE in Felix FileInstall

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4104:

Fix Version/s: 4.0.6
   4.1.0

> NPE in Felix FileInstall
> 
>
> Key: KARAF-4104
> URL: https://issues.apache.org/jira/browse/KARAF-4104
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> Got this from a custom karaf assembly (using the karaf maven plugin)
> {code}
> 2015-11-12 09:54:15,019 | INFO  | nd.bundle.watch) | fileinstall  
> | 6 - org.apache.felix.fileinstall - 3.5.0 | Unable to save 
> configuration
> java.lang.NullPointerException
>   at 
> org.apache.felix.fileinstall.internal.ConfigInstaller.configurationEvent(ConfigInstaller.java:106)[6:org.apache.felix.fileinstall:3.5.0]
>   at 
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[5:org.apache.felix.configadmin:1.8.4]
>   at 
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[5:org.apache.felix.configadmin:1.8.4]
>   at 
> org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[5:org.apache.felix.configadmin:1.8.4]
>   at java.lang.Thread.run(Thread.java:744)[:1.7.0_45]
> {code}
> That is all there is in the log and its repeated endless.
> I guess its the felix file watcher that fails somehow. But nevertheless would 
> be good to get the felix guys to fix a potential NPE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4109) For backward compatibility, support the resolver attribute in features XML

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4109:

Fix Version/s: 4.0.5
   4.1.0

> For backward compatibility, support the resolver attribute in features XML
> --
>
> Key: KARAF-4109
> URL: https://issues.apache.org/jira/browse/KARAF-4109
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-archetypes, karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The resolver attribute in features XML is not supported anymore throwing 
> errors at installation time.
> We have to:
> 1. fix the feature archetype to remove the reference to the resolver attribute
> 2. for backward compatibility, it makes sense to support the resolver 
> attribute even if we don't really use it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4124) feature config installer adds property to config

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4124:
---

Assignee: Jean-Baptiste Onofré

> feature config installer adds property to config
> 
>
> Key: KARAF-4124
> URL: https://issues.apache.org/jira/browse/KARAF-4124
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The  element in a feature XML allows a feature to create and/or 
> populate a configuration (identified by a configuration PID).
> The "FeatureConfigInstaller" adds a custom property to the configuration.
> key = "org.apache.karaf.features.configKey"
> value = result of function call "createConfigurationKey(pid[0], pid[1])"
> There are bundles that cannot handle additional properties in the 
> configuration.
> For example:
> * using Aries JPA + Hiberante + h2
> * the configuration is installed by a feature and a realted config entry
> * this will result in a non working setup
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting 
> "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at 
> org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266)
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90)
> at org.h2.Driver.connect(Driver.java:73)
> at 
> org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187)
> at 
> org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323)
> at 
> org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112)
> at 
> org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at 
> org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127)
> ... 132 more
> {noformat}
> There is a conditional branch in the "findExistingConfiguration" function to 
> filter (find) the configuration using that property instead of the 
> service.pid (this is another conditional branch).
> Is there any reason for using that property?
> I changed the "FeatureConfigInstaller" to not append that property and the 
> above example is working now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4147) karaf-maven-plugin: Add description of configuration property "libraries"

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4147:

Component/s: karaf-documentation

> karaf-maven-plugin: Add description of configuration property "libraries"
> -
>
> Key: KARAF-4147
> URL: https://issues.apache.org/jira/browse/KARAF-4147
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.3
>Reporter: Jochen Kraushaar
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> When I upgraded my Karaf 3.0.3 Assembly to Karaf 4.0.3, I had problems to 
> install libraries to the lib/endorsed directory. After some digging through 
> the code, I found the "libraries" configuration property, which does exactly 
> what I was looking for. It took me even more time to figure out how it works.
> It would be nice, if the description of this property is added to the 
> http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
>  manual.
> For those, who have the same problem an example: To install a PostgreSQL 
> driver at lib/endorsed, add the following configuration entry at your 
> karaf-maven-plugin definition:
> {code}
> 
> 
> mvn:org.postgresql/postgresql/9.3-1102-jdbc41;type:=endorsed
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4124) feature config installer adds property to config

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4124:

Fix Version/s: 4.0.5
   4.1.0

> feature config installer adds property to config
> 
>
> Key: KARAF-4124
> URL: https://issues.apache.org/jira/browse/KARAF-4124
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Markus Rathgeb
> Fix For: 4.1.0, 4.0.5
>
>
> The  element in a feature XML allows a feature to create and/or 
> populate a configuration (identified by a configuration PID).
> The "FeatureConfigInstaller" adds a custom property to the configuration.
> key = "org.apache.karaf.features.configKey"
> value = result of function call "createConfigurationKey(pid[0], pid[1])"
> There are bundles that cannot handle additional properties in the 
> configuration.
> For example:
> * using Aries JPA + Hiberante + h2
> * the configuration is installed by a feature and a realted config entry
> * this will result in a non working setup
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting 
> "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at 
> org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266)
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90)
> at org.h2.Driver.connect(Driver.java:73)
> at 
> org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187)
> at 
> org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323)
> at 
> org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112)
> at 
> org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at 
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at 
> org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127)
> ... 132 more
> {noformat}
> There is a conditional branch in the "findExistingConfiguration" function to 
> filter (find) the configuration using that property instead of the 
> service.pid (this is another conditional branch).
> Is there any reason for using that property?
> I changed the "FeatureConfigInstaller" to not append that property and the 
> above example is working now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4156) Set 'karaf.clean.all' as true will cause data folder cleaned while checking status

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4156:

Fix Version/s: 4.1.0

> Set 'karaf.clean.all' as true will cause data folder cleaned while checking 
> status
> --
>
> Key: KARAF-4156
> URL: https://issues.apache.org/jira/browse/KARAF-4156
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 3.0.5, 4.0.3
> Environment: Running on Mac OS X 10.11
>Reporter: Jerry Meng
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> Scenario
> ===
> In etc/system.properties, it describes
> \# Deletes the entire karaf.data directory at every start
> karaf.clean.all = false
> When I set the property as true, I expect it will clean data folder ONLY at 
> karaf start; however it also causes the command 'stop' and 'status' to delete 
> data folder so that the command complains "shutdown port file doesn't exist. 
> The container is not running."
> Root Cause
> =
> The class 'org.apache.karaf.main.ConfigProperties' checks the property 
> 'karaf.clean.all' in the constructor and deletes the data folder if it's set 
> as true.
> In  'org.apache.karaf.main.Stop' and 'org.apache.karaf.main.Status', they 
> will instantiate ConfigProperties at the very beginning. They will never get 
> port file correctly in this case and even cause working directory being 
> deleted.
> It seams that to delete data folder in the constructor of ConfigProperties 
> does not make sense to me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4147) karaf-maven-plugin: Add description of configuration property "libraries"

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4147:

Fix Version/s: 4.0.5
   4.1.0

> karaf-maven-plugin: Add description of configuration property "libraries"
> -
>
> Key: KARAF-4147
> URL: https://issues.apache.org/jira/browse/KARAF-4147
> Project: Karaf
>  Issue Type: Documentation
>Affects Versions: 4.0.3
>Reporter: Jochen Kraushaar
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> When I upgraded my Karaf 3.0.3 Assembly to Karaf 4.0.3, I had problems to 
> install libraries to the lib/endorsed directory. After some digging through 
> the code, I found the "libraries" configuration property, which does exactly 
> what I was looking for. It took me even more time to figure out how it works.
> It would be nice, if the description of this property is added to the 
> http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
>  manual.
> For those, who have the same problem an example: To install a PostgreSQL 
> driver at lib/endorsed, add the following configuration entry at your 
> karaf-maven-plugin definition:
> {code}
> 
> 
> mvn:org.postgresql/postgresql/9.3-1102-jdbc41;type:=endorsed
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4158) Unexpected behavior on first startup

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4158:

Fix Version/s: 4.0.6
   4.1.0

> Unexpected behavior on first startup
> 
>
> Key: KARAF-4158
> URL: https://issues.apache.org/jira/browse/KARAF-4158
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.3
> Environment: RHEL 6.2 x32, Java 1.8.0_72-ea-b05
>Reporter: Jean-Philippe CLEMENT
> Fix For: 4.1.0, 4.0.6
>
>
> This problem only occurs on the very first startup of a custom assembly. This 
> means unpacking the assembly .tar.gz then run karaf. This issue is not 100% 
> reproducible. Several untar/run might be necessary to reproduce the issue.
> The problem comes with Blueprint property-placeholders. User bundles might be 
> started and not get .cfg replaced properties but the "$(PARAM_NAME)" itself 
> (String property).
> I suspect user bundles to be started before the .cfg files are populated in 
> the /etc directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4174) nullpointerexception when running obr:info on a bundle served by cave

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4174:

Fix Version/s: 4.0.6
   cave-4.0.1
   4.1.0

> nullpointerexception when running obr:info on a bundle served by cave
> -
>
> Key: KARAF-4174
> URL: https://issues.apache.org/jira/browse/KARAF-4174
> Project: Karaf
>  Issue Type: Bug
>  Components: cave-server, karaf-repository
>Affects Versions: 4.0.4
>Reporter: Marton Papp
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, cave-4.0.1, 4.0.6
>
>
> Hello,
> I am using Cave 4.0.0 with Karaf 4.0.4-SNAPSHOT (after having the same 
> problem with 4.0.3) and I get a NullPointerException when running the 
> obr:info command on a bundle. 
> To reproduce:
> __ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
>   Apache Karaf (4.0.4-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> feature:repo-add cave 4.0.0
> Adding feature url 
> mvn:org.apache.karaf.cave/apache-karaf-cave/4.0.0/xml/features
> karaf@root()> feature:install cave-server
> karaf@root()> cave:repository-create my-repository
> karaf@root()> cave:repository-upload my-repository 
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_5
> karaf@root()> feature:install obr
> karaf@root()> obr:url-add 
> http://localhost:8181/cave/http/my-repository-repository.xml
> karaf@root()> obr:list
> Name | Symbolic Name | Version
> --
>  | org.apache.servicemix.bundles.ant | 1.7.0.5
> karaf@root()> obr:info org.apache.servicemix.bundles.ant
> Error executing command: java.lang.NullPointerException
> karaf@root()> display -n 3
> 2015-12-05 18:40:26,319 | INFO  | pool-50-thread-1 | bundle   
> | 56 - org.apache.aries.spifly.dynamic.bundle - 1.0.1 | No 
> 'SPI-Provider' Manifest header. Skipping bundle: org.apache.karaf.obr.core
> 2015-12-05 18:40:26,319 | INFO  | pool-50-thread-1 | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.0.4.SNAPSHOT | Done.
> 2015-12-05 18:40:40,518 | ERROR | nsole user karaf | ShellUtil
> | 44 - org.apache.karaf.shell.core - 4.0.4.SNAPSHOT | Exception 
> caught while executing command
> java.lang.NullPointerException
>   at 
> org.apache.karaf.obr.command.InfoCommand.printResource(InfoCommand.java:65)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.karaf.obr.command.InfoCommand.doExecute(InfoCommand.java:57)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.karaf.obr.command.ObrCommandSupport.execute(ObrCommandSupport.java:58)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:270)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
> karaf@root()> 
> Regards



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4162) Wrap deployer does not add default versions to exported packages

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4162:

Fix Version/s: 4.0.6
   4.1.0

> Wrap deployer does not add default versions to exported packages
> 
>
> Key: KARAF-4162
> URL: https://issues.apache.org/jira/browse/KARAF-4162
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Aleksei Lissitsin
> Fix For: 4.1.0, 4.0.6
>
> Attachments: export-package-actual.txt, export-package-expected.txt, 
> spring-beans-4.1.7.RELEASE.jar
>
>
> Wrap deployer does not add default versions to exported packages but should. 
> Try, e.g., with the provided spring-beans jar.
> My attempts to override this behaviour by using bundle:install with wrap url 
> containing '-nodefaultversion=false' failed too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4192) java.lang.ClassCastException in org.apache.karaf.features.internal.region.CandidateComparator

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4192:
---

Assignee: Jean-Baptiste Onofré

> java.lang.ClassCastException in 
> org.apache.karaf.features.internal.region.CandidateComparator
> -
>
> Key: KARAF-4192
> URL: https://issues.apache.org/jira/browse/KARAF-4192
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Per Kristian Söreide
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> The system bundle will return a String[] {"org.apache.felix.framework", 
> "system.bundle"} on line 57 in CandidateComparator:
> {noformat}
> c = ((Comparable) 
> cap1.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE))
> 
> .compareTo(cap2.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE));{noformat}
> This is causing a ClassCastException being thrown.
> Equinox will return an ArrayList (seen in the stacktrace)
> Stacktrace:
> {noformat}
> java.lang.ClassCastException: java.util.ArrayList cannot be cast to 
> java.lang.Comparable
>   at 
> org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:57)
>   at 
> org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:31)
>   at java.util.TimSort.binarySort(TimSort.java:265)
>   at java.util.TimSort.sort(TimSort.java:208)
>   at java.util.TimSort.sort(TimSort.java:173)
>   at java.util.Arrays.sort(Arrays.java:659)
>   at java.util.Collections.sort(Collections.java:217)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:260)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:272)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> 

[jira] [Updated] (KARAF-4192) java.lang.ClassCastException in org.apache.karaf.features.internal.region.CandidateComparator

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4192:

Fix Version/s: 4.0.5
   4.1.0

> java.lang.ClassCastException in 
> org.apache.karaf.features.internal.region.CandidateComparator
> -
>
> Key: KARAF-4192
> URL: https://issues.apache.org/jira/browse/KARAF-4192
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Per Kristian Söreide
> Fix For: 4.1.0, 4.0.5
>
>
> The system bundle will return a String[] {"org.apache.felix.framework", 
> "system.bundle"} on line 57 in CandidateComparator:
> {noformat}
> c = ((Comparable) 
> cap1.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE))
> 
> .compareTo(cap2.getAttributes().get(BundleNamespace.BUNDLE_NAMESPACE));{noformat}
> This is causing a ClassCastException being thrown.
> Equinox will return an ArrayList (seen in the stacktrace)
> Stacktrace:
> {noformat}
> java.lang.ClassCastException: java.util.ArrayList cannot be cast to 
> java.lang.Comparable
>   at 
> org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:57)
>   at 
> org.apache.karaf.features.internal.region.CandidateComparator.compare(CandidateComparator.java:31)
>   at java.util.TimSort.binarySort(TimSort.java:265)
>   at java.util.TimSort.sort(TimSort.java:208)
>   at java.util.TimSort.sort(TimSort.java:173)
>   at java.util.Arrays.sort(Arrays.java:659)
>   at java.util.Collections.sort(Collections.java:217)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:260)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:272)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> org.apache.felix.resolver.Candidates.processCandidates(Candidates.java:637)
>   at 
> org.apache.felix.resolver.Candidates.populateResource(Candidates.java:273)
>   at 
> 

[jira] [Updated] (KARAF-4181) blacklist.properties is not a properties file

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4181:

Fix Version/s: 4.0.6
   4.1.0

> blacklist.properties is not a properties file
> -
>
> Key: KARAF-4181
> URL: https://issues.apache.org/jira/browse/KARAF-4181
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-profile
>Affects Versions: 4.0.3
>Reporter: Benson Margulies
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> It's confusing that a file named 'blacklist.properties' does not, in fact, 
> contain a properties file. Rather, it's just a list of blacklisted bundles. 
> It seems to me that the name 'blacklist.properties' might be deprecated and 
> the name 'bundle-blacklist.txt' would be more informative.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4199) Privacy Violation: Heap Inspection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4199:

Assignee: (was: Jean-Baptiste Onofré)

> Privacy Violation: Heap Inspection
> --
>
> Key: KARAF-4199
> URL: https://issues.apache.org/jira/browse/KARAF-4199
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify and SciTools Understand were used to perform an application 
> security scan on the karaf source code.
> The method interactive() in Main.java stores sensitive data in a String 
> object on line 127, making it impossible to reliably purge the data from 
> memory.
> Main.java, lines 120-137:
> {code}
> 120 public String[] interactive(String destination, String name, String 
> instruction, String[] prompt, boolean[] echo) {
> 121 String[] answers = new String[prompt.length];
> 122 try {
> 123 for (int i = 0; i < prompt.length; i++) {
> 124 if (echo[i]) {
> 125 answers[i] = console.readLine(prompt[i] + " ");
> 126 } else {
> 127 answers[i] = new String(console.readPassword(prompt[i] + 
> " "));
> 128 }
> 129 if (answers[i] == null) {
> 130 return null;
> 131 }
> 132 }
> 133 return answers;
> 134 } catch (IOError e) {
> 135 return null;
> 136 }
> 137 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4199) Privacy Violation: Heap Inspection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4199:

Fix Version/s: 4.0.6
   4.1.0

> Privacy Violation: Heap Inspection
> --
>
> Key: KARAF-4199
> URL: https://issues.apache.org/jira/browse/KARAF-4199
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify and SciTools Understand were used to perform an application 
> security scan on the karaf source code.
> The method interactive() in Main.java stores sensitive data in a String 
> object on line 127, making it impossible to reliably purge the data from 
> memory.
> Main.java, lines 120-137:
> {code}
> 120 public String[] interactive(String destination, String name, String 
> instruction, String[] prompt, boolean[] echo) {
> 121 String[] answers = new String[prompt.length];
> 122 try {
> 123 for (int i = 0; i < prompt.length; i++) {
> 124 if (echo[i]) {
> 125 answers[i] = console.readLine(prompt[i] + " ");
> 126 } else {
> 127 answers[i] = new String(console.readPassword(prompt[i] + 
> " "));
> 128 }
> 129 if (answers[i] == null) {
> 130 return null;
> 131 }
> 132 }
> 133 return answers;
> 134 } catch (IOError e) {
> 135 return null;
> 136 }
> 137 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4203) Access Specifier Manipulation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4203:

Fix Version/s: 4.0.6
   4.1.0

> Access Specifier Manipulation
> -
>
> Key: KARAF-4203
> URL: https://issues.apache.org/jira/browse/KARAF-4203
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security of the karaf source code.
> The call to method setAccessible() on line 355 changes an access specifier. 
> See the external issue link for more information on the subject.
> File: client/src/main/java/org/apache/karaf/client/Main.java
> Line: 355
> Main.java, lines 353-362:
> {code}
> 353 try {
> 354 Field field = 
> terminal.getClass().getSuperclass().getDeclaredField("settings");
> 355 field.setAccessible(true);
> 356 Object settings = field.get(terminal);
> 357 field = settings.getClass().getDeclaredField("configLastFetched");
> 358 field.setAccessible(true);
> 359 field.setLong(settings, 0L);
> 360 } catch (Throwable t) {
> 361 // Ignore
> 362 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4211) Portability Flaw: Locale Dependent Comparison

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4211:

Fix Version/s: 4.0.6
   4.1.0

> Portability Flaw: Locale Dependent Comparison
> -
>
> Key: KARAF-4211
> URL: https://issues.apache.org/jira/browse/KARAF-4211
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> The call to compareTo() on line 109 causes portability problems because it 
> has different locales which may lead to unexpected output. This may also 
> circumvent custom validation routines.
> File: 
> features/command/src/main/java/org/apache/karaf/features/command/ListFeaturesCommand.java
> Line: 109
> ListFeaturesCommand.java, lines 107-111:
> 107 class FeatureComparator implements Comparator {
> 108 public int compare(Feature o1, Feature o2) {
> 109 return o1.getName().toLowerCase().compareTo( 
> o2.getName().toLowerCase() );
> 110 }
> 111 }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4201) Often Misused: Authentication

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4201:

Fix Version/s: 4.0.6
   4.1.0

> Often Misused: Authentication
> -
>
> Key: KARAF-4201
> URL: https://issues.apache.org/jira/browse/KARAF-4201
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify and SciTools Understand were used to perform an application 
> security scan on the karaf source code.
> The information returned by the call to getByName() on line 150 is not 
> trustworthy. Attackers can spoof DNS entries. 
> File: main/src/main/java/org/apache/karaf/main/InstanceHelper.java
> Line: 150
> InstanceHelper.java, lines 142-166:
> {code}
> 142 static void setupShutdown(ConfigProperties config, Framework framework) {
> 143 writePid(config.pidFile);
> 144 try {
> 145 int port = config.shutdownPort;
> 146 String host = config.shutdownHost;
> 147 String portFile = config.portFile;
> 148 final String shutdown = config.shutdownCommand;
> 149 if (port >= 0) {
> 150 ServerSocket shutdownSocket = new ServerSocket(port, 1, 
> InetAddress.getByName(host));
> 151 if (port == 0) {
> 152 port = shutdownSocket.getLocalPort();
> 153 }
> 154 if (portFile != null) {
> 155 Writer w = new OutputStreamWriter(new 
> FileOutputStream(portFile));
> 156 w.write(Integer.toString(port));
> 157 w.close();
> 158 }
> 159 Thread thread = new ShutdownSocketThread(shutdown, 
> shutdownSocket, framework);
> 160 thread.setDaemon(true);
> 161 thread.start();
> 162 }
> 163 } catch (Exception e) {
> 164 e.printStackTrace();
> 165 }
> 166 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4200) Privacy Violation: Heap Inspection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4200:

Fix Version/s: 4.0.6
   4.1.0

> Privacy Violation: Heap Inspection
> --
>
> Key: KARAF-4200
> URL: https://issues.apache.org/jira/browse/KARAF-4200
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify and SciTools Understand were used to perform an application 
> security scan on the karaf source code.
> The method login() in JDBCLoginModule.java stores sensitive data in a String 
> object on line 95, making it impossible to reliably purge the data from 
> memory.
> JDBCLoginModule.java, lines 88-96:
> {code}
> 88 user = ((NameCallback) callbacks[0]).getName();
> 89 
> 90 char[] tmpPassword = ((PasswordCallback) callbacks[1]).getPassword();
> 91 if (tmpPassword == null) {
> 92 tmpPassword = new char[0];
> 93 }
> 94 
> 95 String password = new String(tmpPassword);
> 96 principals = new HashSet<>();
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4217) XML External Entity Injection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4217:

Fix Version/s: 4.0.6
   4.1.0

> XML External Entity Injection
> -
>
> Key: KARAF-4217
> URL: https://issues.apache.org/jira/browse/KARAF-4217
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> XML parser configured in MavenConfigService.java:74 does not prevent nor 
> limit external entities resolution. This can expose the parser to an XML 
> External Entities attack. See external issue URL.
> File: 
> bundle/core/src/main/java/org/apache/karaf/bundle/core/internal/MavenConfigService.java
> Line: 74
> MavenConfigService.java, lines 66-76:
> {code}
> 66 static String getLocalRepoFromConfig(Dictionary dict) 
> throws XMLStreamException, FileNotFoundException {
> 67 String path = null;
> 68 if (dict != null) {
> 69 path = (String) dict.get("org.ops4j.pax.url.mvn.localRepository");
> 70 if (path == null) {
> 71 String settings = (String) 
> dict.get("org.ops4j.pax.url.mvn.settings");
> 72 if (settings != null) {
> 73 File file = new File(settings);
> 74 XMLStreamReader reader = 
> XMLInputFactory.newFactory().createXMLStreamReader(new FileInputStream(file));
> 75 try {
> 76 int event;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4273) Add -o (--only-matching) option to grep command

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4273:

Fix Version/s: 4.0.6
   4.1.0

> Add -o (--only-matching) option to grep command
> ---
>
> Key: KARAF-4273
> URL: https://issues.apache.org/jira/browse/KARAF-4273
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.0.4
>Reporter: Roland Hauser
>Assignee: Andrea Cosentino
> Fix For: 4.1.0, 4.0.6
>
>
> It would be helpful for scripting if the built-in grep command had an -o 
> option like the Unix counterpart. The -o option should cause grep to print 
> only the matching section of a line, not the whole line itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4209) Weak XML Schema: Unbounded Occurrences

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4209:

Fix Version/s: 4.0.6
   4.1.0

> Weak XML Schema: Unbounded Occurrences
> --
>
> Key: KARAF-4209
> URL: https://issues.apache.org/jira/browse/KARAF-4209
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> Setting a maxOccurs value to unbounded can lead to resources exhaustion and 
> ultimately a denial of service.
> File: 
> features/core/src/main/resources/org/apache/karaf/features/karaf-features-1.0.0.xsd
> Line: 64
> karaf-features-1.0.0.xsd, lines 64-77:
> 64 
> 65 
> 66 
> 67 
> 70 
> 71 
> 72 
> 73 
> 74 
> 75 
> 76 
> 77 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4207) Poor Error Handling: Empty Catch Block

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4207:

Fix Version/s: 4.0.6
   4.1.0

> Poor Error Handling: Empty Catch Block
> --
>
> Key: KARAF-4207
> URL: https://issues.apache.org/jira/browse/KARAF-4207
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> The method authenticate() in JaasSecurityProvider.java ignores an exception 
> on line 199, which could cause the program to overlook unexpected states and 
> conditions. In this case the attempt to authenticate is ignored which is 
> never a good idea.
> File: 
> webconsole/console/src/main/java/org/apache/felix/webconsole/internal/servlet/JaasSecurityProvider.java
> Line: 199
> JaasSecurityProvider.java, lines 155-205:
> {code}
> 155 public boolean authenticate( HttpServletRequest request, 
> HttpServletResponse response )
> 156 {
> 157 // Return immediately if the header is missing
> 158 String authHeader = request.getHeader( HEADER_AUTHORIZATION );
> 159 if ( authHeader != null && authHeader.length() > 0 )
> 160 {
> . . .
> 166 if ( blank > 0 )
> 167 {
> . . .
> 171 // Check whether authorization type matches
> 172 if ( authType.equalsIgnoreCase( AUTHENTICATION_SCHEME_BASIC ) 
> )
> 173 {
> 174 try
> 175 {
> . . .
> 181 // authenticate
> 182 Subject subject = doAuthenticate( username, password 
> );
> 183 if ( subject != null )
> 184 {
> . . .
> 198 }
> 199 catch ( Exception e )
> 200 {
> 201 // Ignore
> 202 }
> 203 }
> 204 }
> 205 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4212) Null Dereference

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4212:

Fix Version/s: 4.0.6
   4.1.0

> Null Dereference
> 
>
> Key: KARAF-4212
> URL: https://issues.apache.org/jira/browse/KARAF-4212
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> The method execute() in LoadTest.java can crash the program by dereferencing 
> a null pointer on line 71.
> File: bundle/core/src/main/java/org/apache/karaf/bundle/command/LoadTest.java
> Line: 71
> LoadTest.java, lines 65-74:
> {code}
> 65 @Override
> 66 public Object execute() throws Exception {
> 67 if (!confirm(session)) {
> 68 return null;
> 69 }
> 70 final BundleContext bundleContext = 
> this.bundleContext.getBundle(0).getBundleContext();
> 71 final FrameworkWiring wiring = 
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> 72 final CountDownLatch latch = new CountDownLatch(threads);
> 73 final Bundle[] bundles = bundleContext.getBundles();
> 74 final AtomicBoolean[] locks = new AtomicBoolean[bundles.length];
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Component/s: karaf-shell

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4208) Poor Error Handling: Empty Catch Block

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4208:

Fix Version/s: 4.0.6
   4.1.0

> Poor Error Handling: Empty Catch Block
> --
>
> Key: KARAF-4208
> URL: https://issues.apache.org/jira/browse/KARAF-4208
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis of the karaf source code.
> The method authenticate() in JaasSecurityProvider.java ignores an exception 
> on line 215, which could cause the program to overlook unexpected states and 
> conditions. In this case an authentication has failed and the attempt to 
> respond to the client and  let them know has also failed. The comment 
> indicates that nothing can be done about the problem but the issue should be 
> logged for further investigation or forensics purposes.
> File: 
> webconsole/console/src/main/java/org/apache/felix/webconsole/internal/servlet/JaasSecurityProvider.java
> Line: 215
> JaasSecurityProvider.java, lines 207-218:
> {code}
> 207 // request authentication
> 208 try
> 209 {
> 210 response.setHeader( HEADER_WWW_AUTHENTICATE, 
> AUTHENTICATION_SCHEME_BASIC + " realm=\"" + this.realm + "\"" );
> 211 response.setStatus( HttpServletResponse.SC_UNAUTHORIZED );
> 212 response.setContentLength( 0 );
> 213 response.flushBuffer();
> 214 }
> 215 catch ( IOException ioe )
> 216 {
> 217 // failed sending the response ... cannot do anything about it
> 218 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4206) Session Fixation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4206:

Fix Version/s: 4.0.6
   4.1.0

> Session Fixation
> 
>
> Key: KARAF-4206
> URL: https://issues.apache.org/jira/browse/KARAF-4206
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand was used to perform an application 
> security analysis on the karaf source code.
> On line 69 of SuCommand.java the method execute() authenticates users without 
> invalidating the existing session identifier, giving an attacker the 
> opportunity to steal authenticated sessions. An existing session should be 
> invalidated by calling HttpSession.invalidate() prior to calling  
> loginContext.login().
> File: jaas/command/src/main/java/org/apache/karaf/jaas/command/SuCommand.java
> Line: 69
> SuCommand.java, lines 52-69:
> {code}
> 52 @Override
> 53 public Object execute() throws Exception {
> 54 Subject subject = new Subject();
> 55 LoginContext loginContext = new LoginContext(realm, subject, new 
> CallbackHandler() {
> 56 public void handle(Callback[] callbacks) throws IOException, 
> UnsupportedCallbackException {
> 57 for (Callback callback : callbacks) {
> 58 if (callback instanceof NameCallback) {
> 59 ((NameCallback) callback).setName(user);
> 60 } else if (callback instanceof PasswordCallback) {
> 61 String password = 
> SuCommand.this.session.readLine("Password: ", '*');
> 62 ((PasswordCallback) 
> callback).setPassword(password.toCharArray());
> 63 } else {
> 64 throw new UnsupportedCallbackException(callback);
> 65 }
> 66 }
> 67 }
> 68 });
> 69 loginContext.login();
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4210) Unreleased Resource: Streams

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4210:

Fix Version/s: 4.0.6
   4.1.0

> Unreleased Resource: Streams
> 
>
> Key: KARAF-4210
> URL: https://issues.apache.org/jira/browse/KARAF-4210
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> The function getLocalRepoFromConfig() in MavenConfigService.java sometimes 
> fails to release a system resource allocated by FileInputStream() on line 74.
> File: 
> bundle/core/src/main/java/org/apache/karaf/bundle/core/internal/MavenConfigService.java
> Line: 74
> MavenConfigService.java, lines 66-76:
> 66 static String getLocalRepoFromConfig(Dictionary dict) 
> throws XMLStreamException, FileNotFoundException {
> 67 String path = null;
> 68 if (dict != null) {
> 69 path = (String) dict.get("org.ops4j.pax.url.mvn.localRepository");
> 70 if (path == null) {
> 71 String settings = (String) 
> dict.get("org.ops4j.pax.url.mvn.settings");
> 72 if (settings != null) {
> 73 File file = new File(settings);
> 74 XMLStreamReader reader = 
> XMLInputFactory.newFactory().createXMLStreamReader(new FileInputStream(file));
> 75 try {
> 76 int event;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4202) Password Management: Hardcoded Password

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4202:

Fix Version/s: 4.0.6
   4.1.0

> Password Management: Hardcoded Password
> ---
>
> Key: KARAF-4202
> URL: https://issues.apache.org/jira/browse/KARAF-4202
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security scan on karaf source code.
> Analysis: Hardcoded passwords may compromise system security in a way that 
> cannot be easily remedied.
> File: 
> jaas/modules/src/main/java/org/apache/karaf/jaas/modules/syncope/SyncopeLoginModule.java
> Line: 47
> SyncopeLoginModule.java, lines 41-49:
> 41 public class SyncopeLoginModule extends AbstractKarafLoginModule {
> 42 
> 43 private final static Logger LOGGER = 
> LoggerFactory.getLogger(SyncopeLoginModule.class);
> 44 
> 45 public final static String ADDRESS = "address";
> 46 public final static String ADMIN_USER = "admin.user"; // for the 
> backing engine
> 47 public final static String ADMIN_PASSWORD = "admin.password"; // for 
> the backing engine
> 48 
> 49 private String address;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4271) Circular dependency not handled properly when a feature references itself directly

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4271:

Fix Version/s: 4.0.6
   4.1.0

> Circular dependency not handled properly when a feature references itself 
> directly
> --
>
> Key: KARAF-4271
> URL: https://issues.apache.org/jira/browse/KARAF-4271
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.4
>Reporter: Roland Hauser
> Fix For: 4.1.0, 4.0.6
>
>
> I did some experiments with circular dependencies where a feature references 
> itself directly. When attribute {{prerequisite}} is set to {{false}} then the 
> feature install succeeds with following log-message
> {code}
> 2016-01-14 17:44:25,509 | INFO  | e user appsrvadm | FeaturesServiceImpl  
> | 7 - org.apache.karaf.features.core - 4.0.4 | Adding features: 
> self-circular-dependency/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
> 2016-01-14 17:44:25,795 | INFO  | pool-47-thread-1 | FeaturesServiceImpl  
> | 7 - org.apache.karaf.features.core - 4.0.4 | No deployment change.
> 2016-01-14 17:44:25,803 | INFO  | pool-47-thread-1 | FeaturesServiceImpl  
> | 7 - org.apache.karaf.features.core - 4.0.4 | Done.
> {code}
> When {{prerequisite}} is set to {{true}}, the feature installation fails with 
> a StackOverFlowError:
> {code}
> java.lang.StackOverflowError
>   at 
> org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:117)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:103)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   ...
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]}}
> {code}
> I would expect in both cases, that the feature:install command fails with an 
> error message like this: "Feature com.foo.bar could not be installed because 
> it references itself"
> You can checkout a project which helps to reproduce the case from 
> [https://github.com/SourcePond/reproduce-feature-circular-dependency.git] 
> (Maven-Modules self-circular-dependency and 
> self-circular-dependency-prerequisite-true). Simply install the root-project 
> to have all necessary Maven dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4205) Privacy Violation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4205:

Fix Version/s: 4.0.6
   4.1.0

> Privacy Violation
> -
>
> Key: KARAF-4205
> URL: https://issues.apache.org/jira/browse/KARAF-4205
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis of the karaf source code.
> The method find() in GogoParser.java mishandles confidential information, 
> which can compromise user privacy and is often illegal.
> File: 
> shell/core/src/main/java/org/apache/karaf/shell/support/parsing/GogoParser.java
> Line: 332
> GogoParser.java, lines 329-333:
> 329 while (level != 0) {
> 330 if (eof()) {
> 331 throw new RuntimeException("Eof found in the middle of a compound 
> for '"
> 332 + target + deeper + "', begins at " + context(start));
> 333 }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4204) Weak SecurityManager Check: Overridable Method

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4204:

Fix Version/s: 4.0.6
   4.1.0

> Weak SecurityManager Check: Overridable Method
> --
>
> Key: KARAF-4204
> URL: https://issues.apache.org/jira/browse/KARAF-4204
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis of the karaf source code.
> Non-final methods that perform security checks can be overridden in ways that 
> bypass security checks. See external issue for more information.
> File: exception/src/main/java/java/lang/Exception.java
> Line: 137
> Exception.java, lines 137-153:
> {code}
> 137 public Class[] getThrowableContext(Throwable t) {
> 138 try {
> 139 Class[] context = getClassContext();
> 140 int nb = 0;
> 141 for (;;) {
> 142 if (context[context.length - 1 - nb] == t.getClass()) {
> 143 break;
> 144 }
> 145 nb++;
> 146 }
> 147 Class[] nc = new Class[nb];
> 148 System.arraycopy(context, context.length - nb, nc, 0, nb);
> 149 return nc;
> 150 } catch (Exception e) {
> 151 return null;
> 152 }
> 153 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4272) Karaf freezes when a circular dependency is introduced where a feature references itself over a chain of other features

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4272:

Fix Version/s: 4.0.6
   4.1.0

> Karaf freezes when a circular dependency is introduced where a feature 
> references itself over a chain of other features
> ---
>
> Key: KARAF-4272
> URL: https://issues.apache.org/jira/browse/KARAF-4272
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.4
>Reporter: Roland Hauser
> Fix For: 4.1.0, 4.0.6
>
>
> Karaf freezes when a circular dependency is introduced where a features 
> references itself over a chain of other features
> I did some experiments with circular dependencies where a feature references 
> itself indirectly over some other features. In this case it does not matter 
> if attribute {{prerequisite}} is set or not. After command {{feature:install 
> c-references-a}} Karaf freezes and must be restarted.
>   
> I would expect, that the feature:install command fails with an error message 
> like this: 
> "Feature com.foo.bar could not be installed because a circular reference:
>  a-references-b
>   b-references-c
>   c-references-a"
> You can checkout a project which helps to reproduce the case from 
> [https://github.com/SourcePond/reproduce-feature-circular-dependency.git] 
> (Maven-Modules c-references-a and c-references-a-prerequisite-true). Simply 
> install the root-project to have all necessary Maven dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4214) Deserialization of Untrusted Data

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4214:

Fix Version/s: 4.0.6
   4.1.0

> Deserialization of Untrusted Data
> -
>
> Key: KARAF-4214
> URL: https://issues.apache.org/jira/browse/KARAF-4214
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> The application deserializes untrusted data without sufficiently verifying 
> that the resulting data will be valid. An adversary could attack the 
> application by tampering with the resource "karaf.key". 
> File: client\src\main\java\org\apache\karaf\client\Main.java
> Line: 297
> Main.java, lines 291-313:
> {code}
> 291 private static SshAgent startAgent(String user, URL privateKeyUrl, String 
> keyFile) {
> 292 InputStream is = null;
> 293 try {
> 294 SshAgent agent = new AgentImpl();
> 295 is = privateKeyUrl.openStream();
> 296 ObjectInputStream r = new ObjectInputStream(is);
> 297 KeyPair keyPair = (KeyPair) r.readObject();
> 298 is.close();
> 299 agent.addIdentity(keyPair, user);
> 300 if (keyFile != null) {
> 301 String[] keyFiles = new String[]{keyFile};
> 302 FileKeyPairProvider fileKeyPairProvider = new 
> FileKeyPairProvider(keyFiles);
> 303 for (KeyPair key : fileKeyPairProvider.loadKeys()) {
> 304 agent.addIdentity(key, user);
> 305 }
> 306 }
> 307 return agent;
> 308 } catch (Throwable e) {
> 309 close(is);
> 310 System.err.println("Error starting ssh agent for: " + 
> e.getMessage());
> 311 return null;
> 312 }
> 313 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4216) Poor Error Handling: Return Inside Finally

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4216:

Fix Version/s: 4.0.6
   4.1.0

> Poor Error Handling: Return Inside Finally
> --
>
> Key: KARAF-4216
> URL: https://issues.apache.org/jira/browse/KARAF-4216
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> The method build() in PublickeyBackingEngineFactory.java returns from inside 
> a finally block on line 52, which will cause exceptions to be lost.
> File: 
> jaas/modules/src/main/java/org/apache/karaf/jaas/modules/publickey/PublickeyBackingEngineFactory.java
> Line: 52
> PublickeyBackingEngineFactory.java, lines 40-54:
> {code}
> 40 public BackingEngine build(Map options) {
> 41 PublickeyBackingEngine engine = null;
> 42 String usersFile = (String) options.get(USER_FILE);
> 43 
> 44 File f = new File(usersFile);
> 45 Properties users;
> 46 try {
> 47 users = new Properties(f);
> 48 engine = new PublickeyBackingEngine(users);
> 49 } catch (IOException ioe) {
> 50 logger.warn("Cannot open keys file:" + usersFile);
> 51 } finally {
> 52 return engine;
> 53 }
> 54 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4215) Use of Dynamic Class Loading, Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4215:

Fix Version/s: 4.0.6
   4.1.0

> Use of Dynamic Class Loading, Use of Externally-Controlled Input to Select 
> Classes or Code ('Unsafe Reflection')
> 
>
> Key: KARAF-4215
> URL: https://issues.apache.org/jira/browse/KARAF-4215
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Eduardo Aguinaga
> Fix For: 4.1.0, 4.0.6
>
>
> HP Fortify SCA and SciTools Understand were used to perform an application 
> security analysis on the karaf source code.
> Dynamically loaded code has the potential to be malicious. The application 
> uses external input with reflection to select which classes or code to use, 
> but it does not sufficiently prevent the input from selecting improper 
> classes or code. The constructor for DefaultJDBCLock includes one parameter 
> for a Properties object from which the parameters for the dynamic class are 
> taken. None of the properties are checked for content.
> File: main\src\main\java\org\apache\karaf\main\lock\DefaultJDBCLock.java
> Line: 365
> DefaultJDBCLock.java, lines 364-369:
> {code}
> 364 Connection doCreateConnection(String driver, String url, String username, 
> String password) throws ClassNotFoundException, SQLException {
> 365 Class.forName(driver);
> 366 // results in a closed connection in Derby if the update lock table 
> request timed out
> 367 // DriverManager.setLoginTimeout(timeout);
> 368 return DriverManager.getConnection(url, username, password);
> 369 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4260:
---

Assignee: Jean-Baptiste Onofré

> Setting karaf.clean.all = true breaks service wrapper service script
> 
>
> Key: KARAF-4260
> URL: https://issues.apache.org/jira/browse/KARAF-4260
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> The Karaf service wrapper script is generated such that the PID file is 
> created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then 
> the PID file created by the service script gets deleted together with the 
> data directory. As a result of this the service script reports Karaf as not 
> running and it is not possible to stop the process via the script.
> The PID file location probably should be outside the data directory by 
> default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4237) can't install transaction feature and activemq-camel feature: Missing dependency javax.transaction.TransactionManager

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4237:

Assignee: (was: Jean-Baptiste Onofré)

> can't install transaction feature and activemq-camel feature: Missing 
> dependency javax.transaction.TransactionManager
> -
>
> Key: KARAF-4237
> URL: https://issues.apache.org/jira/browse/KARAF-4237
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
> Environment: ubuntu 14.04, java 7 update 79 (also tried with java 8 
> update 45), karaf 3.0.3 camel 2.16.1, activemq 5.13.0
>Reporter: Edward Welch
> Fix For: 4.1.0, 4.0.6
>
>
> I found a little bit of a strange behavior, which I think points to a 
> possible bug in the features dependency resolver?
> Easiest way to reproduce, start with a vanilla 4.0.3
> feature:repo-add activemq 5.13.0
> feature:repo-add camel 2.16.1
> feature:install transaction activemq-camel
> bundle:diag
> You will see both Apache Aries Transaction Blueprint bundles in Grace Period 
> waiting for javax.transaction.TransactionManager
> Pretty sure this is caused by some bad wiring on a bundle which 
> activemq-camel brings in, here is that feature descriptor:
> {code}
>  start-level='50'>
> spring
>  dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta-spec-version}
>  dependency='true'>mvn:commons-pool/commons-pool/${commons-pool-version}
>  dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/${geronimo-jms-spec-version}
> spring-jms
> camel-core
> mvn:org.apache.camel/camel-jms/${project.version}
> 
> {code}
> I see the aries transaction bundles being wired to this bundle coming from 
> the activemq-camel feature: 
> mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta-spec-version}
> What's strange about this, that bundle is marked dependency="true" so I would 
> think it wouldn't need to be installed at all.
> Also peculiar, if you follow this install order:
> feature:repo-add activemq 5.13.0
> feature:repo-add camel 2.16.1
> feature:install transaction
> feature:install activemq-camel
> bundle:diag
> There is no issue, so the re-wiring/refresh of the transaction bundles never 
> happens
> Also when I originally posted this on the mailing list: 
> http://karaf.922171.n3.nabble.com/Missing-dependency-javax-transaction-TransactionManager-with-transaction-feature-and-activemq-camel-td4044354.html
> Christian Schneider was unable to reproduce the issue, even though it occurs 
> 100% of the time for me, so maybe there is something else in play here that I 
> can't think of.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4260:

Fix Version/s: 4.0.5
   4.1.0

> Setting karaf.clean.all = true breaks service wrapper service script
> 
>
> Key: KARAF-4260
> URL: https://issues.apache.org/jira/browse/KARAF-4260
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> The Karaf service wrapper script is generated such that the PID file is 
> created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then 
> the PID file created by the service script gets deleted together with the 
> data directory. As a result of this the service script reports Karaf as not 
> running and it is not possible to stop the process via the script.
> The PID file location probably should be outside the data directory by 
> default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4237) can't install transaction feature and activemq-camel feature: Missing dependency javax.transaction.TransactionManager

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4237:

Fix Version/s: 4.0.6
   4.1.0

> can't install transaction feature and activemq-camel feature: Missing 
> dependency javax.transaction.TransactionManager
> -
>
> Key: KARAF-4237
> URL: https://issues.apache.org/jira/browse/KARAF-4237
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
> Environment: ubuntu 14.04, java 7 update 79 (also tried with java 8 
> update 45), karaf 3.0.3 camel 2.16.1, activemq 5.13.0
>Reporter: Edward Welch
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> I found a little bit of a strange behavior, which I think points to a 
> possible bug in the features dependency resolver?
> Easiest way to reproduce, start with a vanilla 4.0.3
> feature:repo-add activemq 5.13.0
> feature:repo-add camel 2.16.1
> feature:install transaction activemq-camel
> bundle:diag
> You will see both Apache Aries Transaction Blueprint bundles in Grace Period 
> waiting for javax.transaction.TransactionManager
> Pretty sure this is caused by some bad wiring on a bundle which 
> activemq-camel brings in, here is that feature descriptor:
> {code}
>  start-level='50'>
> spring
>  dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta-spec-version}
>  dependency='true'>mvn:commons-pool/commons-pool/${commons-pool-version}
>  dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/${geronimo-jms-spec-version}
> spring-jms
> camel-core
> mvn:org.apache.camel/camel-jms/${project.version}
> 
> {code}
> I see the aries transaction bundles being wired to this bundle coming from 
> the activemq-camel feature: 
> mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta-spec-version}
> What's strange about this, that bundle is marked dependency="true" so I would 
> think it wouldn't need to be installed at all.
> Also peculiar, if you follow this install order:
> feature:repo-add activemq 5.13.0
> feature:repo-add camel 2.16.1
> feature:install transaction
> feature:install activemq-camel
> bundle:diag
> There is no issue, so the re-wiring/refresh of the transaction bundles never 
> happens
> Also when I originally posted this on the mailing list: 
> http://karaf.922171.n3.nabble.com/Missing-dependency-javax-transaction-TransactionManager-with-transaction-feature-and-activemq-camel-td4044354.html
> Christian Schneider was unable to reproduce the issue, even though it occurs 
> 100% of the time for me, so maybe there is something else in play here that I 
> can't think of.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4261) Bundle start-level seems to be ignored at Karaf restart

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4261:

Fix Version/s: 4.0.6
   4.1.0

> Bundle start-level seems to be ignored at Karaf restart
> ---
>
> Key: KARAF-4261
> URL: https://issues.apache.org/jira/browse/KARAF-4261
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
> Fix For: 4.1.0, 4.0.6
>
>
> AS a workaround for CAMEL-9483 I have set a start-level for my bundles 
> deployed as part of my features. This works as expected during initial 
> deployment (order of deployment is according to the start levels I set), but 
> not during sub-sequent starts of Karaf. It appears the start-level of the 
> bundles is ignored, meaning the order of deployment of my bundles is more or 
> less random and I observe the issues described in CAMEL-9483 again.
> {{bundle:list}} shows my bundles with the start-levels they have been 
> originally deployed with, though.
> As a workaround I set {{karaf.clean.all = true}} in system.properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4269) Jetty logs backtrace for combination of jolokia and async

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4269.
-
Resolution: Won't Fix

Agree with Achim: it's a Pax Web issue.

> Jetty logs backtrace for combination of jolokia and async
> -
>
> Key: KARAF-4269
> URL: https://issues.apache.org/jira/browse/KARAF-4269
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-webcontainer
>Affects Versions: 4.0.4
>Reporter: Benson Margulies
>
> If I install the jolokia feature, plus my CXF 3.1.4 services that are async 
> (use @Suspended AsyncResponse params), each call to my service results in the 
> following in the log:
> {noformat}
> 2016-01-14 09:41:36,034 | WARN  | qtp465679012-170 | HttpChannel  
> | 197 - org.eclipse.jetty.util - 9.2.14.v20151106 | 
> /rest/v1/morphology/parts-of-speech
> java.lang.IllegalStateException: STREAM
>   at 
> org.eclipse.jetty.server.Response.getWriter(Response.java:910)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.apache.cxf.transport.servlet.ServletController.generateNotFound(ServletController.java:247)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:184)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:707)[83:javax.servlet-api:3.1.0]
>   at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)[122:org.apache.cxf.cxf-rt-transports-http:3.1.4]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
>   at 
> org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[193:org.eclipse.jetty.security:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:271)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[195:org.eclipse.jetty.servlet:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:99)[216:org.ops4j.pax.web.pax-web-jetty:4.2.4]
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.Server.handleAsync(Server.java:549)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:318)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:262)[194:org.eclipse.jetty.server:9.2.14.v20151106]
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[197:org.eclipse.jetty.util:9.2.14.v20151106]
>   at 
> 

[jira] [Updated] (KARAF-4275) StaticConfigurationAdmin and NPE with spring dm

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4275:

Fix Version/s: 4.0.6
   4.1.0

> StaticConfigurationAdmin and NPE with spring dm
> ---
>
> Key: KARAF-4275
> URL: https://issues.apache.org/jira/browse/KARAF-4275
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-profile
>Affects Versions: 4.0.4
> Environment: Karaf 4.0.4 with a static distribution
>Reporter: J. Brébec
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Spring DM throw a NPE with a Karaf static distribution, when a configuration 
> is not bound. The Static ConfigurationAdmin implementation is not compliant 
> with the specification : getConfiguration should never return null.
> A workaround : create an for every configuration a file .cfg in 
> etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4275) StaticConfigurationAdmin and NPE with spring dm

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4275:
---

Assignee: Jean-Baptiste Onofré

> StaticConfigurationAdmin and NPE with spring dm
> ---
>
> Key: KARAF-4275
> URL: https://issues.apache.org/jira/browse/KARAF-4275
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-profile
>Affects Versions: 4.0.4
> Environment: Karaf 4.0.4 with a static distribution
>Reporter: J. Brébec
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Spring DM throw a NPE with a Karaf static distribution, when a configuration 
> is not bound. The Static ConfigurationAdmin implementation is not compliant 
> with the specification : getConfiguration should never return null.
> A workaround : create an for every configuration a file .cfg in 
> etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4311) karaf maven plugin does not respect -s setting on maven

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4311:

Fix Version/s: 4.0.5
   4.1.0

> karaf maven plugin does not respect -s setting on maven
> ---
>
> Key: KARAF-4311
> URL: https://issues.apache.org/jira/browse/KARAF-4311
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Raman Gupta
>Assignee: Jean-Baptiste Onofré
>  Labels: maven
> Fix For: 4.1.0, 4.0.5
>
>
> The karaf maven plugin uses the pax maven resolver for some things, like 
> verification for example.
> However, mvn has the -s switch to specify a particular settings.xml at build 
> time, which is often used by CI systems. Since the karaf-maven-plugin is 
> running from a maven command, it should call or configure pax so that it uses 
> the settings.xml specified by the user at the command line, if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (KARAF-4283) List command reporting incorrect bundle state after service recovery

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4283:
---

Assignee: Jean-Baptiste Onofré

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)