[jira] [Updated] (KARAF-1047) feature:uninstall command may provide -r option
[ https://issues.apache.org/jira/browse/KARAF-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1047: Fix Version/s: (was: 3.0.4) 3.0.5 feature:uninstall command may provide -r option --- Key: KARAF-1047 URL: https://issues.apache.org/jira/browse/KARAF-1047 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.4.3, 3.0.5 The feature:uninstall command could support -r (--recursive) option to uninstall all dependent features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2495) reverse lookup of feature by bundle
[ https://issues.apache.org/jira/browse/KARAF-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2495: Fix Version/s: (was: 3.0.4) 3.0.5 reverse lookup of feature by bundle --- Key: KARAF-2495 URL: https://issues.apache.org/jira/browse/KARAF-2495 Project: Karaf Issue Type: New Feature Components: karaf-shell Affects Versions: 2.3.2 Reporter: Jason Reilly Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.0.0.M3, 2.4.3, 3.0.5 Lookup feature from bundle information. Where did a particular bundle come from? Similar to how features:info feature lists the bundles, but the reverse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2382) Add a command to show bundles with split packages
[ https://issues.apache.org/jira/browse/KARAF-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2382: Fix Version/s: (was: 3.0.4) 3.0.5 Add a command to show bundles with split packages - Key: KARAF-2382 URL: https://issues.apache.org/jira/browse/KARAF-2382 Project: Karaf Issue Type: New Feature Components: karaf-shell Reporter: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files - via ${ENV.foo}?
[
https://issues.apache.org/jira/browse/KARAF-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2466:
Fix Version/s: (was: 3.0.4)
3.0.5
make it easy to access environment variables inside karaf configuration
properties files - via ${ENV.foo}?
--
Key: KARAF-2466
URL: https://issues.apache.org/jira/browse/KARAF-2466
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Reporter: james strachan
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0.M3, 2.4.3, 3.0.5
when using karaf in clouds PaaS infrastructures like OpenShift, Docker,
OpenStack et al; its common to use environment variables to pass in
environment specific values; then keep a single disk image. It would be nice
if there was an easy way to reference environment variables similar to the
${foo.bar} syntax for accessing system properties.
Maybe karaf should support some kind of environment variable expansion like
{code}
# define a property based on an env var
foo = ${ENV.nameOfEnvVar}
# e.g. here's the host name
host = ${ENV.HOSTNAME}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2843) Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features
[ https://issues.apache.org/jira/browse/KARAF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2843: Fix Version/s: (was: 3.0.4) Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features - Key: KARAF-2843 URL: https://issues.apache.org/jira/browse/KARAF-2843 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2843) Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features
[ https://issues.apache.org/jira/browse/KARAF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2843: Fix Version/s: 3.0.5 Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features - Key: KARAF-2843 URL: https://issues.apache.org/jira/browse/KARAF-2843 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin
[ https://issues.apache.org/jira/browse/KARAF-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3100: Fix Version/s: (was: 3.0.4) 3.0.5 Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin - Key: KARAF-3100 URL: https://issues.apache.org/jira/browse/KARAF-3100 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 3.0.1 Reporter: Gareth Collins Assignee: Jean-Baptiste Onofré Fix For: 3.0.4, 4.0.0.M3, 2.4.3 I have created a pull request for this here: https://github.com/apache/karaf/pull/43 As the title says, this allows karaf to be configured to output feature configurations to config file...which I believe are easier to manage. Let me know what you think. If it looks OK, would it be possible to merge soon (e.g. karaf 3.0.2 :))? The changes are very localized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin
[ https://issues.apache.org/jira/browse/KARAF-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3100: Fix Version/s: (was: 3.0.5) 3.0.4 Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin - Key: KARAF-3100 URL: https://issues.apache.org/jira/browse/KARAF-3100 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 3.0.1 Reporter: Gareth Collins Assignee: Jean-Baptiste Onofré Fix For: 3.0.4, 4.0.0.M3, 2.4.3 I have created a pull request for this here: https://github.com/apache/karaf/pull/43 As the title says, this allows karaf to be configured to output feature configurations to config file...which I believe are easier to manage. Let me know what you think. If it looks OK, would it be possible to merge soon (e.g. karaf 3.0.2 :))? The changes are very localized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3193) Add diag webconsole plugin
[ https://issues.apache.org/jira/browse/KARAF-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3193: Fix Version/s: (was: 3.0.4) 3.0.5 Add diag webconsole plugin -- Key: KARAF-3193 URL: https://issues.apache.org/jira/browse/KARAF-3193 Project: Karaf Issue Type: New Feature Components: karaf-webconsole Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 The bundle:diag command (and other diag:* commands) is helpful for end user to get some details about the current bundle state. It would be helpful to provide a Diagnostic view on the Karaf WebConsole, providing the same information as in the commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3737) ActiveMQ Broker disappears after Karaf restart
[
https://issues.apache.org/jira/browse/KARAF-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-3737:
---
Assignee: Jean-Baptiste Onofré
ActiveMQ Broker disappears after Karaf restart
--
Key: KARAF-3737
URL: https://issues.apache.org/jira/browse/KARAF-3737
Project: Karaf
Issue Type: Bug
Affects Versions: 2.4.2
Reporter: Krzysztof Sobkowiak
Assignee: Jean-Baptiste Onofré
I have installed an ActiveMQ broker on a fresh Karaf version
{code}
karaf@root features:chooseurl activemq 5.11.1
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.11.1/xml/features
karaf@root features:install activemq-broker
karaf@root activemq:list
brokerName = amq-broker
{code}
There is the default {{amq-broker}} available. Here the list of installed
ActiveMQ features and bundles
{code}
karaf@root features:list | grep activemq | grep -v uninstalled
[installed ] [5.11.1 ] activemq-client
activemq-core-5.11.1 ActiveMQ client libraries
[installed ] [5.11.1 ] activemq
activemq-core-5.11.1 ActiveMQ broker libraries
[installed ] [5.11.1 ] activemq-broker
activemq-5.11.1 Full ActiveMQ broker with default configuration and
web console
[installed ] [5.11.1 ] activemq-web-console
activemq-5.11.1
karaf@root list -t 0 -l | grep activemq
[ 89] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-osgi/5.11.1
[ 90] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-karaf/5.11.1
[ 103] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activeio-core/3.1.4
[ 123] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activemq-web-console/5.11.1/war
{code}
Services exported by the {{activemq-osgi}} bundle
{code}
karaf@root ls -a 89
You are about to access system bundle 89. Do you wish to continue (yes/no):
yes
activemq-osgi (89) provides:
objectClass = [org.osgi.service.cm.ManagedServiceFactory]
osgi.service.blueprint.compname = activeMQServiceFactory
service.id = 359
service.pid = org.apache.activemq.server
objectClass = [org.osgi.service.blueprint.container.BlueprintContainer]
osgi.blueprint.container.symbolicname = org.apache.activemq.activemq-osgi
osgi.blueprint.container.version = 5.11.1
service.id = 360
Bundle-SymbolicName = org.apache.activemq.activemq-osgi
Bundle-Version = 5.11.1
objectClass =
[org.springframework.osgi.context.DelegatedExecutionOsgiBundleApplicationContext,
org.springframework.osgi.context.ConfigurableOsgiBundleApplicationContext,
org.springframework.context.ConfigurableApplicationContext,
org.springframework.context.ApplicationContext,
org.springframework.context.Lifecycle, java.io.Closeable,
org.springframework.core.env.EnvironmentCapable,
org.springframework.beans.factory.ListableBeanFactory,
org.springframework.beans.factory.HierarchicalBeanFactory,
org.springframework.context.MessageSource,
org.springframework.context.ApplicationEventPublisher,
org.springframework.core.io.support.ResourcePatternResolver,
org.springframework.beans.factory.BeanFactory,
org.springframework.core.io.ResourceLoader, java.lang.AutoCloseable,
org.springframework.beans.factory.DisposableBean]
org.springframework.context.service.name = org.apache.activemq.activemq-osgi
service.id = 390
{code}
After restart:
{code}
karaf@root activemq:list
karaf@root features:list | grep activemq | grep -v uninstalled
[installed ] [5.11.1 ] activemq-client
activemq-core-5.11.1 ActiveMQ client libraries
[installed ] [5.11.1 ] activemq
activemq-core-5.11.1 ActiveMQ broker libraries
[installed ] [5.11.1 ] activemq-broker
activemq-5.11.1 Full ActiveMQ broker with default configuration and
web console
[installed ] [5.11.1 ] activemq-web-console
activemq-5.11.1
karaf@root list -t 0 -l | grep activemq
[ 89] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-osgi/5.11.1
[ 90] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-karaf/5.11.1
[ 103] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activeio-core/3.1.4
[ 123] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activemq-web-console/5.11.1/war
karaf@root ls -a 89
You are about to access system bundle 89. Do you wish to continue (yes/no):
yes
activemq-osgi (89) provides:
objectClass = [org.osgi.service.cm.ManagedServiceFactory]
[jira] [Commented] (KARAF-3737) ActiveMQ Broker disappears after Karaf restart
[
https://issues.apache.org/jira/browse/KARAF-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553679#comment-14553679
]
Jean-Baptiste Onofré commented on KARAF-3737:
-
OK, let me check the change on 2.4.2 that can have an impact.
ActiveMQ Broker disappears after Karaf restart
--
Key: KARAF-3737
URL: https://issues.apache.org/jira/browse/KARAF-3737
Project: Karaf
Issue Type: Bug
Affects Versions: 2.4.2
Reporter: Krzysztof Sobkowiak
Assignee: Jean-Baptiste Onofré
I have installed an ActiveMQ broker on a fresh Karaf version
{code}
karaf@root features:chooseurl activemq 5.11.1
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.11.1/xml/features
karaf@root features:install activemq-broker
karaf@root activemq:list
brokerName = amq-broker
{code}
There is the default {{amq-broker}} available. Here the list of installed
ActiveMQ features and bundles
{code}
karaf@root features:list | grep activemq | grep -v uninstalled
[installed ] [5.11.1 ] activemq-client
activemq-core-5.11.1 ActiveMQ client libraries
[installed ] [5.11.1 ] activemq
activemq-core-5.11.1 ActiveMQ broker libraries
[installed ] [5.11.1 ] activemq-broker
activemq-5.11.1 Full ActiveMQ broker with default configuration and
web console
[installed ] [5.11.1 ] activemq-web-console
activemq-5.11.1
karaf@root list -t 0 -l | grep activemq
[ 89] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-osgi/5.11.1
[ 90] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-karaf/5.11.1
[ 103] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activeio-core/3.1.4
[ 123] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activemq-web-console/5.11.1/war
{code}
Services exported by the {{activemq-osgi}} bundle
{code}
karaf@root ls -a 89
You are about to access system bundle 89. Do you wish to continue (yes/no):
yes
activemq-osgi (89) provides:
objectClass = [org.osgi.service.cm.ManagedServiceFactory]
osgi.service.blueprint.compname = activeMQServiceFactory
service.id = 359
service.pid = org.apache.activemq.server
objectClass = [org.osgi.service.blueprint.container.BlueprintContainer]
osgi.blueprint.container.symbolicname = org.apache.activemq.activemq-osgi
osgi.blueprint.container.version = 5.11.1
service.id = 360
Bundle-SymbolicName = org.apache.activemq.activemq-osgi
Bundle-Version = 5.11.1
objectClass =
[org.springframework.osgi.context.DelegatedExecutionOsgiBundleApplicationContext,
org.springframework.osgi.context.ConfigurableOsgiBundleApplicationContext,
org.springframework.context.ConfigurableApplicationContext,
org.springframework.context.ApplicationContext,
org.springframework.context.Lifecycle, java.io.Closeable,
org.springframework.core.env.EnvironmentCapable,
org.springframework.beans.factory.ListableBeanFactory,
org.springframework.beans.factory.HierarchicalBeanFactory,
org.springframework.context.MessageSource,
org.springframework.context.ApplicationEventPublisher,
org.springframework.core.io.support.ResourcePatternResolver,
org.springframework.beans.factory.BeanFactory,
org.springframework.core.io.ResourceLoader, java.lang.AutoCloseable,
org.springframework.beans.factory.DisposableBean]
org.springframework.context.service.name = org.apache.activemq.activemq-osgi
service.id = 390
{code}
After restart:
{code}
karaf@root activemq:list
karaf@root features:list | grep activemq | grep -v uninstalled
[installed ] [5.11.1 ] activemq-client
activemq-core-5.11.1 ActiveMQ client libraries
[installed ] [5.11.1 ] activemq
activemq-core-5.11.1 ActiveMQ broker libraries
[installed ] [5.11.1 ] activemq-broker
activemq-5.11.1 Full ActiveMQ broker with default configuration and
web console
[installed ] [5.11.1 ] activemq-web-console
activemq-5.11.1
karaf@root list -t 0 -l | grep activemq
[ 89] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-osgi/5.11.1
[ 90] [Active ] [Created ] [ ] [ 50]
mvn:org.apache.activemq/activemq-karaf/5.11.1
[ 103] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activeio-core/3.1.4
[ 123] [Active ] [] [ ] [ 50]
mvn:org.apache.activemq/activemq-web-console/5.11.1/war
karaf@root ls -a 89
You are about to access system bundle 89. Do you wish to continue (yes/no):
yes
activemq-osgi (89) provides:
[jira] [Updated] (KARAF-1728) BundleException: Bundle installation rejected by hook. error when installing from features XML file
[
https://issues.apache.org/jira/browse/KARAF-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1728:
Fix Version/s: (was: 3.0.4)
3.0.5
BundleException: Bundle installation rejected by hook. error when installing
from features XML file
---
Key: KARAF-1728
URL: https://issues.apache.org/jira/browse/KARAF-1728
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 3.0.0
Reporter: Hendy Irawan
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0.M3, 3.0.5
Console:
{code}
karaf@root() feature:install -v commerce-shell
Installing feature commerce-shell 4.0.1-SNAPSHOT
Installing feature commerce-core 4.0.1-SNAPSHOT
Installing feature oss-deps 1.0.0
Installing feature httpclient 4.2.1
Installing feature jpa 1.0.0
Installing feature xml-specs-api 1.9.0
Installing feature soluvas-framework 1.0.0-SNAPSHOT
Installing feature magja 1.0.3-SNAPSHOT
Installing feature http 3.0.0-SNAPSHOT
Installing feature apache-ldap-client 1.0.0-M12
Installing feature drools 5.4.0
Installing feature blueprints-neo4j 1.2
Installing feature neo4j 1.7.2
Installing bundle
wrap:mvn:org.neo4j/neo4j-kernel/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-kernel;=split,*
Installing bundle
wrap:mvn:org.neo4j/neo4j-lucene-index/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-lucene-index;=split,*
Installing bundle wrap:mvn:org.neo4j/neo4j-cypher/1.8.M07
Installing bundle wrap:mvn:org.neo4j/neo4j-rest-graphdb/1.7
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-core/1.2
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-neo4j-graph/1.2
Installing bundle wrap:mvn:com.tinkerpop/frames/0.7
Installing feature soluvas-image-store 1.0.0-SNAPSHOT
Installing bundle wrap:mvn:net.coobird/thumbnailator/0.4.1
Installing bundle mvn:org.soluvas/soluvas-image-store/1.0.0-SNAPSHOT
Installing feature soluvas-ldap 1.0.0-SNAPSHOT
Installing bundle
mvn:org.apache.geronimo.specs/geronimo-validation_1.0_spec/1.1
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-common/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-api/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle mvn:org.soluvas/soluvas-ldap/1.0.0-SNAPSHOT
Installing feature openjpa 2.2.0
Installing feature jndi 1.0.0
Found installed bundle: org.apache.aries.util [9]
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.api/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.core/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.rmi/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.url/1.0.0
Installing bundle
mvn:org.apache.aries.jndi/org.apache.aries.jndi.legacy.support/1.0.0
Installing feature transaction 1.0.0
Installing bundle mvn:commons-pool/commons-pool/1.6
Error executing command: Bundle installation rejected by hook.
{code}
Log and stack trace:
{code}
2012-08-15 18:12:42,454 | INFO | Thread-6 | ShellUtil
| 40 - org.apache.karaf.shell.console - 3.0.0.SNAPSHOT | Exception
caught while executing command
org.osgi.framework.BundleException: Bundle installation rejected by hook.
at org.apache.felix.framework.Felix.installBundle(Felix.java:2872)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:894)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:606)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:450)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:431)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:420)
at Proxyd6c71027_7662_4a47_bbd6_ba300c8a7c7a.installFeature(Unknown
Source)
at
[jira] [Updated] (KARAF-2735) Add samples in distribution
[ https://issues.apache.org/jira/browse/KARAF-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2735: Fix Version/s: (was: 3.0.4) 3.0.5 Add samples in distribution --- Key: KARAF-2735 URL: https://issues.apache.org/jira/browse/KARAF-2735 Project: Karaf Issue Type: Improvement Components: karaf-demo, karaf-documentation Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 I would like to replace the demos folder (as it's not really demo) by a samples modules. The purpose is to provide examples with README about the different features (one per sub-module) provided by Karaf. I will bootstrap this module on master later today including the skeleton for the different sub-module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2836) Be able to define multiple keys per user in etc/keys.properties
[
https://issues.apache.org/jira/browse/KARAF-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2836:
Fix Version/s: (was: 3.0.4)
3.0.5
Be able to define multiple keys per user in etc/keys.properties
---
Key: KARAF-2836
URL: https://issues.apache.org/jira/browse/KARAF-2836
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0.M3, 2.4.3, 3.0.5
Currently, if we define multiple keys in etc/keys.properties like this:
{code}
karaf=key,admin
karaf=other,admin
{code}
only the latest one is used/loaded (for instance other here).
It would be great to be able to load multiple keys for one given user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3074) Provide mbeans for statistics of hibernate session factories
[ https://issues.apache.org/jira/browse/KARAF-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3074: Fix Version/s: (was: 3.0.4) 3.0.5 Provide mbeans for statistics of hibernate session factories Key: KARAF-3074 URL: https://issues.apache.org/jira/browse/KARAF-3074 Project: Karaf Issue Type: New Feature Affects Versions: 2.3.5 Reporter: Christian Schneider Fix For: 4.0.0, 3.0.5 Hibernate session factories provides JMX Beans for its statistics. We could create a bundle that looks for all EntityManagerFactories, retrieves the hibernate session factories and publishes a jmx bean for each. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3194) Add feature-generate-doc mojo
[ https://issues.apache.org/jira/browse/KARAF-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3194: Fix Version/s: (was: 3.0.4) 3.0.5 Add feature-generate-doc mojo - Key: KARAF-3194 URL: https://issues.apache.org/jira/browse/KARAF-3194 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 3.0.5 In order to generate a documentation on the resources containing: - the feature description - the feature transitive features - the feature bundles - the feature configs it would be great to have karaf:feature-generate-doc as we have karaf:commands-generate-doc mojo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3477) HeapDumpProvider should use a JMXServiceURL in order to provide username/password
[ https://issues.apache.org/jira/browse/KARAF-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553673#comment-14553673 ] Jean-Baptiste Onofré commented on KARAF-3477: - With the latest change on the guard, it should not be an issue anymore. I'm testing it. HeapDumpProvider should use a JMXServiceURL in order to provide username/password - Key: KARAF-3477 URL: https://issues.apache.org/jira/browse/KARAF-3477 Project: Karaf Issue Type: Bug Components: karaf-management Affects Versions: 3.0.2 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.4, 4.0.0.M3 The Karaf MBean guard prevent to create a heap dump in the dev:create-dump command as it directly goes to the platform MBean server. The HeapDumpProvider should go throught a JMXServiceURL in order to provide the principals. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3611) karaf-maven-plugin fails for startupFeatures + wrap:
[
https://issues.apache.org/jira/browse/KARAF-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553686#comment-14553686
]
Freeman Fang commented on KARAF-3611:
-
Hi JB,
Please postpone to 3.0.5, thanks!
Freeman
karaf-maven-plugin fails for startupFeatures + wrap:
--
Key: KARAF-3611
URL: https://issues.apache.org/jira/browse/KARAF-3611
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.3
Reporter: Ancoron Luciferis
Assignee: Freeman Fang
Fix For: 3.0.4
In case a feature declaration uses a bundle url such as the following:
{noformat}
wrap:mvn:org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-Wrappedamp;Bundle-SymbolicName=wrap-org.pacesys.openstack4jamp;Bundle-Version=2.0.1amp;Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,amp;Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*
{noformat}
...and in the assembly/custom distribution project, the feature is defined
inside {{startupFeatures/}}, the build fails with:
{noformat}
[INFO] Installing bundles defined in startup.properties in the system
[WARNING] Failed to canonicalize path
/home/ancoron/.m2/repository/wrap/mvn/org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*/mvn-org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*.jar.lastUpdated:
File name too long
[INFO] Downloading:
http://nexus-test/nexus/content/groups/public/wrap/mvn/org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*/mvn-org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*.jar
[WARNING] Failed to canonicalize path
/home/ancoron/.m2/repository/wrap/mvn/org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*/mvn-org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*.jar.lastUpdated:
File name too long
[WARNING] Failed to create parent directories for tracking file
/home/ancoron/.m2/repository/wrap/mvn/org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*/mvn-org.pacesys/openstack4j/2.0.1/jar/withdeps$Bundle-Name=OpenStack4J-WrapBundle-SymbolicName=wrap-org.pacesys.openstack4jBundle-Version=2.0.1Export-Package=org.openstack4j.model.*,org.openstack4j.api.*,org.openstack4j.common.*,org.openstack4j.openstack,Import-Package=javax.xml.*,org.xml.sax.*,org.w3c.dom.*,javax.activation,javax.net.*.jar.lastUpdated
[WARNING] Failed to canonicalize path
[jira] [Updated] (KARAF-1583) karaf-maven-plugin ignores dependency on feature
[
https://issues.apache.org/jira/browse/KARAF-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1583:
Fix Version/s: (was: 3.0.4)
3.0.5
karaf-maven-plugin ignores dependency on feature
Key: KARAF-1583
URL: https://issues.apache.org/jira/browse/KARAF-1583
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Brian Topping
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0.M3, 3.0.5
When a project has a dependency on a feature, the dependency should be
rendered in the features.xml generated by
{{karaf-maven-plugin:features-generate-descriptor}} as a {{repository}}
element.
I thought I added this, but it must have gotten lost in the patches and will
submit another patch after KARAF-1537 is applied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-1379) Provide exit alias and improve shell:logout command
[ https://issues.apache.org/jira/browse/KARAF-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1379: Fix Version/s: (was: 3.0.4) 3.0.5 Provide exit alias and improve shell:logout command --- Key: KARAF-1379 URL: https://issues.apache.org/jira/browse/KARAF-1379 Project: Karaf Issue Type: New Feature Components: karaf-shell Affects Versions: 2.2.6 Reporter: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 Currently, the shell:logout command allow to exit from Karaf shell. The problem is that it kills the Karaf process (shell:logout is called with CRTL-D). shell:logout should not kill the main Karaf process (the shutdown command is dedicated for that) and an exit alias to shell:logout could be interesting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-1379) Provide exit alias and improve shell:logout command
[ https://issues.apache.org/jira/browse/KARAF-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-1379: --- Assignee: Jean-Baptiste Onofré Provide exit alias and improve shell:logout command --- Key: KARAF-1379 URL: https://issues.apache.org/jira/browse/KARAF-1379 Project: Karaf Issue Type: New Feature Components: karaf-shell Affects Versions: 2.2.6 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 Currently, the shell:logout command allow to exit from Karaf shell. The problem is that it kills the Karaf process (shell:logout is called with CRTL-D). shell:logout should not kill the main Karaf process (the shutdown command is dedicated for that) and an exit alias to shell:logout could be interesting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2468) karaf-maven-plugin to support creation of partialbundlelists for sling launchpad
[ https://issues.apache.org/jira/browse/KARAF-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2468: Fix Version/s: (was: 3.0.4) 3.0.5 karaf-maven-plugin to support creation of partialbundlelists for sling launchpad Key: KARAF-2468 URL: https://issues.apache.org/jira/browse/KARAF-2468 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Reto Gmür Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 3.0.5 Attachments: karaf-maven-plugin.patch The sling launchpad maven plugin (http://sling.apache.org/documentation/development/maven-launchpad-plugin.html) supports the use partialbundlelists to group together related bundles. While with the sling launchpad plugin one can create both partialbundlelists and karaf features the flexibility for creating karaf features is somehow limited. So it would be great to also provide the ability in the karaf-maven-plugin to create partialbundlelist for sling. That is for users who primarily want to create a karaf features to also have the possibility to server sling launchpad using projects without having to duplicate the list of bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2630) GenerateDescriptorMojo does not resolve conflicts
[
https://issues.apache.org/jira/browse/KARAF-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2630:
Fix Version/s: (was: 3.0.4)
3.0.5
GenerateDescriptorMojo does not resolve conflicts
-
Key: KARAF-2630
URL: https://issues.apache.org/jira/browse/KARAF-2630
Project: Karaf
Issue Type: New Feature
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Maarten Winkels
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0.M3, 3.0.5
Attachments: karaf-2630.patch
When a feature project has two different versions of a dependency in its
graph, both versions are included in the generated feature.xml
e.g.:
DependencyTree:
{code}...
| +- org.activiti:activiti-engine:jar:5.15-SNAPSHOT:compile
| | +- org.activiti:activiti-bpmn-converter:jar:5.15-SNAPSHOT:compile
| | | +- org.activiti:activiti-bpmn-model:jar:5.15-SNAPSHOT:compile
| | | | +- (org.apache.commons:commons-lang3:jar:3.1:compile -
omitted for duplicate)
| | | | \- (org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile
- version managed from 1.9.9; omitted for duplicate)
| | | +- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed
from 1.7.2; scope managed from compile; omitted for duplicate)
| | | +- (org.slf4j:jcl-over-slf4j:jar:1.7.2:compile - omitted for
duplicate)
| | | \- (org.apache.commons:commons-lang3:jar:3.1:compile - omitted
for duplicate)
| | +- org.apache.commons:commons-email:jar:1.2:compile
| | | +- javax.mail:mail:jar:1.4.1:provided (scope managed from
compile)
| | | | \- (javax.activation:activation:jar:1.1.1:provided - version
managed from 1.1; scope managed from compile; omitted for duplicate)
| | | \- javax.activation:activation:jar:1.1.1:provided
| | +- org.apache.commons:commons-lang3:jar:3.1:compile
| | +- org.mybatis:mybatis:jar:3.2.2:compile
| | +- (org.springframework:spring-beans:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
| | +- joda-time:joda-time:jar:2.1:compile
| | +- org.slf4j:slf4j-api:jar:1.7.5:provided
| | \- org.slf4j:jcl-over-slf4j:jar:1.7.2:compile
| | \- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed
from 1.7.2; scope managed from compile; omitted for duplicate)
| \- org.activiti:activiti-spring:jar:5.14:compile
|+- (org.activiti:activiti-engine:jar:5.14:compile - omitted for
conflict with 5.15-SNAPSHOT)
|+- (org.springframework:spring-context:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- (org.springframework:spring-jdbc:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- (org.springframework:spring-tx:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- (org.apache.commons:commons-lang3:jar:3.1:compile - omitted for
duplicate)
|+- org.springframework:spring-orm:jar:3.2.4.RELEASE:provided
(version managed from 3.1.2.RELEASE; scope managed from compile)
|| +- (aopalliance:aopalliance:jar:1.0:provided - scope managed
from compile; omitted for duplicate)
|| +- (org.springframework:spring-beans:jar:3.2.4.RELEASE:provided
- version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|| +- (org.springframework:spring-core:jar:3.2.4.RELEASE:provided -
version managed from 3.0.7.RELEASE; scope managed from compile; omitted for
duplicate)
|| +- (org.springframework:spring-jdbc:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|| \- (org.springframework:spring-tx:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- commons-dbcp:commons-dbcp:jar:1.4:compile
|| \- commons-pool:commons-pool:jar:1.5.4:compile
|+- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed from
1.7.2; scope managed from compile; omitted for duplicate)
|\- (org.slf4j:jcl-over-slf4j:jar:1.7.2:compile - omitted for
duplicate)
...{code}
generated feature.xml:
{code}...
bundlemvn:org.activiti/activiti-engine/5.15-SNAPSHOT/bundle
bundlemvn:org.activiti/activiti-bpmn-converter/5.15-SNAPSHOT/bundle
bundlemvn:org.activiti/activiti-bpmn-model/5.15-SNAPSHOT/bundle
[jira] [Updated] (KARAF-2684) Create tests for Hibernate and OpenJPA features
[ https://issues.apache.org/jira/browse/KARAF-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2684: Fix Version/s: (was: 3.0.4) 3.0.5 Create tests for Hibernate and OpenJPA features --- Key: KARAF-2684 URL: https://issues.apache.org/jira/browse/KARAF-2684 Project: Karaf Issue Type: Task Components: karaf-test Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 A couple of users reported issues with both OpenJPA and Hibernate features. If our itests currently test the right installation of the features, they don't actually test the right behaviour of the features. It would make sense to use Aries examples (ariestrader and blog) or our own simple examples to test the right behaviour. These examples should be part of the Karaf distribution including a section in the developers guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2814) Add jmx:* commands and feature
[ https://issues.apache.org/jira/browse/KARAF-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2814: Fix Version/s: (was: 3.0.4) 3.0.5 Add jmx:* commands and feature -- Key: KARAF-2814 URL: https://issues.apache.org/jira/browse/KARAF-2814 Project: Karaf Issue Type: New Feature Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 I prepared a new feature on a local branch: the jmx feature. This feature contains: - jmx-jolokia to easily install jolokia in Karaf - jmx-commands providing new jmx:* commands to manipulate MBeans directly (jmx:query, jmx:set, etc). It could be a local action (using the local MBean server) or remote (providing the JMX service URL). I will submit the proposal on the mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2814) Add jmx:* commands and feature
[ https://issues.apache.org/jira/browse/KARAF-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553767#comment-14553767 ] Jean-Baptiste Onofré commented on KARAF-2814: - I wonder if it doesn't make sense to provide such commands in Decanter, as it's part of the monitoring layer. Add jmx:* commands and feature -- Key: KARAF-2814 URL: https://issues.apache.org/jira/browse/KARAF-2814 Project: Karaf Issue Type: New Feature Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 I prepared a new feature on a local branch: the jmx feature. This feature contains: - jmx-jolokia to easily install jolokia in Karaf - jmx-commands providing new jmx:* commands to manipulate MBeans directly (jmx:query, jmx:set, etc). It could be a local action (using the local MBean server) or remote (providing the JMX service URL). I will submit the proposal on the mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2969) Provide a script to install wrapper/service without starting Karaf
[ https://issues.apache.org/jira/browse/KARAF-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2969: Fix Version/s: (was: 3.0.4) 3.0.5 Provide a script to install wrapper/service without starting Karaf -- Key: KARAF-2969 URL: https://issues.apache.org/jira/browse/KARAF-2969 Project: Karaf Issue Type: New Feature Components: karaf-os-integration Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 2.4.3, 3.0.5 Right now, the wrapper/service installation requires to start karaf, install the wrapper feature, and finally execute the wrapper:install command. It would be great to have a script to create the wrapper resource without starting Karaf and installing the wrapper feature. The script can do the same as the wrapper:install command: detect the OS, generate the wrapper files, and provide a description message to integrate in the OS boot service (runlevel/init.d, or windows service). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3035) Use aries transaction jdbc / jms for pooling
[ https://issues.apache.org/jira/browse/KARAF-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3035: Fix Version/s: (was: 3.0.4) 3.0.5 Use aries transaction jdbc / jms for pooling Key: KARAF-3035 URL: https://issues.apache.org/jira/browse/KARAF-3035 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0.M3 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0.M3, 2.4.3, 3.0.5 Attachments: templates.zip, vcs-diff1271163984438294153.patch, vcs-diff458849033395514.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3263) karaf-maven-plugin install=auto support for aggregate features
[
https://issues.apache.org/jira/browse/KARAF-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3263:
Fix Version/s: (was: 3.0.4)
3.0.5
karaf-maven-plugin install=auto support for aggregate features
--
Key: KARAF-3263
URL: https://issues.apache.org/jira/browse/KARAF-3263
Project: Karaf
Issue Type: Improvement
Components: karaf-tooling
Affects Versions: 3.0.1
Reporter: Gary Kennedy
Assignee: Jean-Baptiste Onofré
Priority: Minor
Fix For: 4.0.0.M3, 3.0.5
When using karaf-maven-plugin:features-generate-descriptor, the generated
feature tags for xml/feature dependencies are not merged with the
feature.xml template so I cannot add install=auto to the feature tag.
eg,
POM:
{code}
...
packagingfeature/packaging
...
dependencies
dependency
artifactIdfeatureA/artifactId
typexml/type
classifierfeatures/classifier
/dependency
/dependencies
...
build
plugins
plugin
groupIdorg.apache.karaf.tooling/groupId
artifactIdkaraf-maven-plugin/artifactId
version3.0.1/version
extensionstrue/extensions
configuration
aggregateFeaturestrue/aggregateFeatures
/configuration
/plugins
/plugins
/build
{code}
feature.xml template (src/main/feature/feature.xml):
{code}
?xml ...
features ...
feature name=featureA install=auto /
/features
{code}
results in:
{code}
?xml ...
features ...
feature name=featureA install=auto /
feature name=featureA version=... description=...
!-- Generated descriptor --
/feature
/features
{code}
Since this is for generating an application feature from individual
component features, and none of the component features are auto-install
in one application and no-auto-install in another, I can work around this
by specifying the install attribute in the component feature.xml.
So, would it be possible to merge aggregated features with the feature
template? (eg, matching on name and only overriding the feature tag
attributes except for version, so only
install/description/resolver/start-level. Contents to be replaced with
dependency feature content - we don't want to mess with those)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2522) Boot feature bundle failure forces other bundles to start regardless 'start' flag
[ https://issues.apache.org/jira/browse/KARAF-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2522: Fix Version/s: (was: 3.0.4) 3.0.5 Boot feature bundle failure forces other bundles to start regardless 'start' flag - Key: KARAF-2522 URL: https://issues.apache.org/jira/browse/KARAF-2522 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 2.3.2, 2.3.3 Reporter: Alexey Gavrilov Assignee: Jean-Baptiste Onofré Fix For: 2.3.12, 2.4.3, 3.0.5 If a bundle under a boot feature fails to start, then all the bundles marked as 'start=false' will be forced to start during handling an error. Steps to reproduce: - create a boot feature containing two bundles. - make the first bundle fail on startup (due to missing dependency, for example) - mark the second bundle as 'start=false' - start the Karaf container - the first bundle will fail to start - the second bundle will be started regardless the 'start=false' flag. I think the problem is around the start bundle loop at FeaturesServiceImpl.java:525 (in Karaf 2.3.2) which doesn't respect the bunlde startup flag when starting the installed bundles when 'Option.NoCleanIfFailure' is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2538) Per user command history
[ https://issues.apache.org/jira/browse/KARAF-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2538: Fix Version/s: (was: 3.0.4) 3.0.5 Per user command history Key: KARAF-2538 URL: https://issues.apache.org/jira/browse/KARAF-2538 Project: Karaf Issue Type: Improvement Components: karaf-shell Reporter: Jonathan Anstey Fix For: 4.0.0.M3, 2.4.3, 3.0.5 As mentioned in KARAF-2503, it would be nice to have command history per user. This is what folks used to a shell environment would expect I think. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2508) make osgi:find-class a more useful command
[ https://issues.apache.org/jira/browse/KARAF-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2508: Fix Version/s: (was: 3.0.4) 3.0.5 make osgi:find-class a more useful command -- Key: KARAF-2508 URL: https://issues.apache.org/jira/browse/KARAF-2508 Project: Karaf Issue Type: Improvement Components: karaf-shell Affects Versions: 2.3.3 Reporter: Amichai Rothman Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.0.0.M3, 2.4.3, 3.0.5 I recently had to track down which bundle contains a certain class, and found the find-class command wanting. A few simple improvements would make it much more useful: 1. Add an --exact/-e option which doesn't automatically add asterisks at both ends of the string. In my case I was looking for the javax.jms.Connection class, and since the search is only on the last part of the name, this returned all classes in all packages which have the word Connection in their name, which added up to hundreds of results. with --exact I could look for what I want exactly, or choose to add asterisks at one or both ends explicitly in the search string if I wanted to. 2. Add a --local/-l option which adds BundleWiring.LISTRESOURCES_LOCAL to the listResources method call bitmask. With the current implementation, it returns both bundles containing the given class name and classes that import it from other bundles, which is useful in some cases. But with the --local option it could show only the bundles that actually contain the class (whether exported or not, unlike the exports command), which is far more useful in tracking down some classloading issues. 3. Add the bundle ID (at least) on the beginning of every printed line. This makes it amenable to grepping (without it a grep loses all bundle information, which is the whole point of using this command). 4. As a somewhat more complex alternative to #3, it would be nice if you could specify a fully qualified class name and not only the last part of the name. The command can split the search string around periods, pass the last part to listResources, then internally grep/match the full name. That would make it truly flexible in finding classes. Asterisks would have to be treated accordingly. I think adding these options (#1-#3 are trivial implementations), or at least some of them, would make the command extremely useful when performing classloading diagnosis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 3.0.4) 3.0.5 Review and update documentation --- Key: KARAF-2511 URL: https://issues.apache.org/jira/browse/KARAF-2511 Project: Karaf Issue Type: Task Components: karaf-documentation Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3, 3.0.5 The documentation (manual) should be reviewed: - The subshell part should be described (usage and configuration). - The code samples/screenshots have to be updated with Karaf 3.0.0 use cases - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2960) Optional KAR feature installation
[ https://issues.apache.org/jira/browse/KARAF-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2960: Fix Version/s: (was: 3.0.4) 3.0.5 Optional KAR feature installation - Key: KARAF-2960 URL: https://issues.apache.org/jira/browse/KARAF-2960 Project: Karaf Issue Type: Improvement Components: karaf-kar Affects Versions: 3.0.1 Reporter: Simon Watson Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.0.0.M3, 3.0.5 I find the KAR feature of Karaf very useful, and a great way to manage server deployments. I notice that when a KAR is installed (via console, or from deploy dir), that all features are automatically installed. Is it possible to only install the KAR's feature-repos and leave the features to be installed manually? This would help where we have feature A and feature B, both depending on feature C. It's easy to include all three in one features XML but we might not want both A and B installing on every server. As things stand, we have to manually uninstall the ones we don't want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3738) Karaf client should be able to read environment variables
Korenev Artem created KARAF-3738:
Summary: Karaf client should be able to read environment variables
Key: KARAF-3738
URL: https://issues.apache.org/jira/browse/KARAF-3738
Project: Karaf
Issue Type: Improvement
Affects Versions: 3.0.3
Reporter: Korenev Artem
Priority: Minor
Now the client can only get the properties from org.apache.karaf.shell.cfg and
doesn't look up in environment variables.
So specifying in org.apache.karaf.shell.cfg file something different from raw
values will cause similar exception:
Exception in thread main java.lang.NumberFormatException: For input string:
${ssh.port}
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:481)
at java.lang.Integer.parseInt(Integer.java:527)
at org.apache.karaf.client.ClientConfig.init(ClientConfig.java:46)
at org.apache.karaf.client.Main.main(Main.java:51)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3739) Add eventadmin feature as featuresBoot in standard distribution
Jean-Baptiste Onofré created KARAF-3739: --- Summary: Add eventadmin feature as featuresBoot in standard distribution Key: KARAF-3739 URL: https://issues.apache.org/jira/browse/KARAF-3739 Project: Karaf Issue Type: Improvement Components: karaf-core Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0.M3 In order to avoid shell console restart when installing eventadmin, and as lot of modules now uses eventadmin, it makes sense to install eventadmin feature by default in the standard distribution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3738) Karaf client should be able to read environment variables
[
https://issues.apache.org/jira/browse/KARAF-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Korenev Artem updated KARAF-3738:
-
Priority: Major (was: Minor)
Issue Type: Bug (was: Improvement)
Karaf client should be able to read environment variables
-
Key: KARAF-3738
URL: https://issues.apache.org/jira/browse/KARAF-3738
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.3
Reporter: Korenev Artem
Now the client can only get the properties from org.apache.karaf.shell.cfg
and doesn't look up in environment variables.
So specifying in org.apache.karaf.shell.cfg file something different from raw
values will cause similar exception:
Exception in thread main java.lang.NumberFormatException: For input string:
${ssh.port}
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:481)
at java.lang.Integer.parseInt(Integer.java:527)
at org.apache.karaf.client.ClientConfig.init(ClientConfig.java:46)
at org.apache.karaf.client.Main.main(Main.java:51)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3740) NPE on containeer startup
Christian Schneider created KARAF-3740: -- Summary: NPE on containeer startup Key: KARAF-3740 URL: https://issues.apache.org/jira/browse/KARAF-3740 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 4.0.0.M1 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.0.0.M3 21:20:36,288 | INFO | pool-1-thread-1 | rnal.service.FeaturesServiceImpl 1096 | 6 - org.apache.karaf.features.core - 4.0.0.SNAPSHOT | Adding features: shell/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], cxf-abdera/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], cxf-commands/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], package/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], spring-dm/[1.2.1,1.2.1], ssh/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel/[2.15.1,2.15.1], bundle/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], config/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], feature/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], deployer/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], request-callback/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], instance/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel-talendjob/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], camel-jms/[2.15.1,2.15.1], diagnostic/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], aries-blueprint/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], wrap/[0,0.0.0], kar/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], cxf/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], talend-job-controller/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], camel-ftp/[2.15.1,2.15.1], shell-compat/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-jmx-http-agent/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], webconsole/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-aux-client-rest/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], log/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-sam-agent/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], jaas/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], system/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], service/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], management/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel-cxf/[2.15.1,2.15.1] 21:20:45,328 | ERROR | pool-1-thread-1 | al.service.BootFeaturesInstaller 111 | 6 - org.apache.karaf.features.core - 4.0.0.SNAPSHOT | Error installing boot features java.lang.NullPointerException at org.apache.felix.resolver.ResolverImpl.permutateIfNeeded(ResolverImpl.java:1523)[org.eclipse.osgi-3.10.1.v20140909-1633.jar:] at org.apache.felix.resolver.Candidates.checkSubstitutes(Candidates.java:447)[org.eclipse.osgi-3.10.1.v20140909-1633.jar:] at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:225)[org.eclipse.osgi-3.10.1.v20140909-1633.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:266)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1059)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:958)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60] at java.lang.Thread.run(Thread.java:745)[:1.7.0_60] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3740) NPE on containeer startup
[ https://issues.apache.org/jira/browse/KARAF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3740: Priority: Critical (was: Major) NPE on containeer startup - Key: KARAF-3740 URL: https://issues.apache.org/jira/browse/KARAF-3740 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 4.0.0.M1 Reporter: Christian Schneider Assignee: Christian Schneider Priority: Critical Fix For: 4.0.0.M3 21:20:36,288 | INFO | pool-1-thread-1 | rnal.service.FeaturesServiceImpl 1096 | 6 - org.apache.karaf.features.core - 4.0.0.SNAPSHOT | Adding features: shell/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], cxf-abdera/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], cxf-commands/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], package/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], spring-dm/[1.2.1,1.2.1], ssh/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel/[2.15.1,2.15.1], bundle/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], config/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], feature/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], deployer/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], request-callback/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], instance/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel-talendjob/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], camel-jms/[2.15.1,2.15.1], diagnostic/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], aries-blueprint/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], wrap/[0,0.0.0], kar/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], cxf/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], talend-job-controller/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], camel-ftp/[2.15.1,2.15.1], shell-compat/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-jmx-http-agent/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], webconsole/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-aux-client-rest/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], log/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-sam-agent/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], jaas/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], system/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], service/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], management/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel-cxf/[2.15.1,2.15.1] 21:20:45,328 | ERROR | pool-1-thread-1 | al.service.BootFeaturesInstaller 111 | 6 - org.apache.karaf.features.core - 4.0.0.SNAPSHOT | Error installing boot features java.lang.NullPointerException at org.apache.felix.resolver.ResolverImpl.permutateIfNeeded(ResolverImpl.java:1523)[org.eclipse.osgi-3.10.1.v20140909-1633.jar:] at org.apache.felix.resolver.Candidates.checkSubstitutes(Candidates.java:447)[org.eclipse.osgi-3.10.1.v20140909-1633.jar:] at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:225)[org.eclipse.osgi-3.10.1.v20140909-1633.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:266)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1059)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:958)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60] at java.lang.Thread.run(Thread.java:745)[:1.7.0_60] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3740) NPE on containeer startup
[ https://issues.apache.org/jira/browse/KARAF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554509#comment-14554509 ] Jean-Baptiste Onofré commented on KARAF-3740: - It looks like a resolver issue due to bundle permutation. NPE on containeer startup - Key: KARAF-3740 URL: https://issues.apache.org/jira/browse/KARAF-3740 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 4.0.0.M1 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.0.0.M3 21:20:36,288 | INFO | pool-1-thread-1 | rnal.service.FeaturesServiceImpl 1096 | 6 - org.apache.karaf.features.core - 4.0.0.SNAPSHOT | Adding features: shell/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], cxf-abdera/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], cxf-commands/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], package/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], spring-dm/[1.2.1,1.2.1], ssh/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel/[2.15.1,2.15.1], bundle/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], config/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], feature/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], deployer/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], request-callback/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], instance/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel-talendjob/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], camel-jms/[2.15.1,2.15.1], diagnostic/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], aries-blueprint/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], wrap/[0,0.0.0], kar/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], cxf/[3.1.0.SNAPSHOT,3.1.0.SNAPSHOT], talend-job-controller/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], camel-ftp/[2.15.1,2.15.1], shell-compat/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-jmx-http-agent/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], webconsole/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-aux-client-rest/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], log/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], tesb-sam-agent/[6.0.0.SNAPSHOT,6.0.0.SNAPSHOT], jaas/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], system/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], service/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], management/[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT], camel-cxf/[2.15.1,2.15.1] 21:20:45,328 | ERROR | pool-1-thread-1 | al.service.BootFeaturesInstaller 111 | 6 - org.apache.karaf.features.core - 4.0.0.SNAPSHOT | Error installing boot features java.lang.NullPointerException at org.apache.felix.resolver.ResolverImpl.permutateIfNeeded(ResolverImpl.java:1523)[org.eclipse.osgi-3.10.1.v20140909-1633.jar:] at org.apache.felix.resolver.Candidates.checkSubstitutes(Candidates.java:447)[org.eclipse.osgi-3.10.1.v20140909-1633.jar:] at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:225)[org.eclipse.osgi-3.10.1.v20140909-1633.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:266)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1059)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:958)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60] at java.lang.Thread.run(Thread.java:745)[:1.7.0_60] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
