issues@karaf.apache.org
ChengRen created KARAF-3030: --- Summary: Karaf doesn't support Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.7)) Key: KARAF-3030 URL: https://issues.apache.org/jira/browse/KARAF-3030 Project: Karaf Issue Type: Bug Affects Versions: 3.0.1 Reporter: ChengRen I have a bundle who's manifest contains osgi header: Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.7)) when i run the bundle in karaf 3.0.1, I got bundle can not be resolved error : Error executing command: Error executing command on bundles: Unable to execute command on bundle 182: The bundle "myproject.core.api_1.0.0.201405150206 [182]" could not be res olved. Reason: Missing Constraint: Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.7))" When I check karaf config.properties, I found "org.osgi.framework.system.capabilities" property which export osgi.ee. Is this a karaf bug?? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-1545) Jar files in lib directory require "karaf-" prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1545: Fix Version/s: (was: 2.2.12) 4.0.0 > Jar files in lib directory require "karaf-" prefix in order to be loaded > > > Key: KARAF-1545 > URL: https://issues.apache.org/jira/browse/KARAF-1545 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-documentation >Affects Versions: 2.2.2 > Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. > Java home: /home/jcarman/Programs/jdk1.6.0_32/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" >Reporter: James Carman >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > Attachments: karaf-3.0_1545.diff > > > I was trying to configure JDBC fail-over, so I put my mysql driver jar in the > KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the > advice of someone on IRC, I changed the name to > "karaf-mysql-connector-java.jar" and it started working. Why the karaf- > prefix requirement? If that's the intended behavior, then please update the > README file in the lib directory. It says: > "Any jar in this folder will be part of the main classloader used to load > Karaf." -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-1545) Jar files in lib directory require "karaf-" prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1545: Component/s: karaf-documentation > Jar files in lib directory require "karaf-" prefix in order to be loaded > > > Key: KARAF-1545 > URL: https://issues.apache.org/jira/browse/KARAF-1545 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-documentation >Affects Versions: 2.2.2 > Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. > Java home: /home/jcarman/Programs/jdk1.6.0_32/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" >Reporter: James Carman >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > Attachments: karaf-3.0_1545.diff > > > I was trying to configure JDBC fail-over, so I put my mysql driver jar in the > KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the > advice of someone on IRC, I changed the name to > "karaf-mysql-connector-java.jar" and it started working. Why the karaf- > prefix requirement? If that's the intended behavior, then please update the > README file in the lib directory. It says: > "Any jar in this folder will be part of the main classloader used to load > Karaf." -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-1545) Jar files in lib directory require "karaf-" prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026534#comment-14026534 ] Jean-Baptiste Onofré commented on KARAF-1545: - Good idea. Let me do that. > Jar files in lib directory require "karaf-" prefix in order to be loaded > > > Key: KARAF-1545 > URL: https://issues.apache.org/jira/browse/KARAF-1545 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-documentation >Affects Versions: 2.2.2 > Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. > Java home: /home/jcarman/Programs/jdk1.6.0_32/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" >Reporter: James Carman >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > Attachments: karaf-3.0_1545.diff > > > I was trying to configure JDBC fail-over, so I put my mysql driver jar in the > KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the > advice of someone on IRC, I changed the name to > "karaf-mysql-connector-java.jar" and it started working. Why the karaf- > prefix requirement? If that's the intended behavior, then please update the > README file in the lib directory. It says: > "Any jar in this folder will be part of the main classloader used to load > Karaf." -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-1545) Jar files in lib directory require "karaf-" prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026529#comment-14026529 ] James Carman commented on KARAF-1545: - How about just fix the documentation? The intended behavior was that only karaf-prefixed jars would be loaded, so the docs are obviously wrong. > Jar files in lib directory require "karaf-" prefix in order to be loaded > > > Key: KARAF-1545 > URL: https://issues.apache.org/jira/browse/KARAF-1545 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 2.2.2 > Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. > Java home: /home/jcarman/Programs/jdk1.6.0_32/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" >Reporter: James Carman >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.12, 2.4.0, 3.0.2, 2.3.6 > > Attachments: karaf-3.0_1545.diff > > > I was trying to configure JDBC fail-over, so I put my mysql driver jar in the > KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the > advice of someone on IRC, I changed the name to > "karaf-mysql-connector-java.jar" and it started working. Why the karaf- > prefix requirement? If that's the intended behavior, then please update the > README file in the lib directory. It says: > "Any jar in this folder will be part of the main classloader used to load > Karaf." -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-3029) Support encryption of Maven repo passwords
[ https://issues.apache.org/jira/browse/KARAF-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026510#comment-14026510 ] Jonathan Anstey commented on KARAF-3029: I'm still using Java 1.7 so didn't notice this yet ;-) Thx for the heads up. I'll switch to pax url 2.1. > Support encryption of Maven repo passwords > -- > > Key: KARAF-3029 > URL: https://issues.apache.org/jira/browse/KARAF-3029 > Project: Karaf > Issue Type: Improvement >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.4.0, 4.0.0, 3.0.2 > > > Maven already provides a nice mechanism to encrypt server passwords (see > http://maven.apache.org/guides/mini/guide-encryption.html) but pax-url-mvn > ignores this information and requires a plaintext password be added to the > repo URL. This is already fixed in pax-url-aether 2.0.0 so I'm looking at > using that. Just should already be working for 4.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-3029) Support encryption of Maven repo passwords
[ https://issues.apache.org/jira/browse/KARAF-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026500#comment-14026500 ] Jean-Baptiste Onofré commented on KARAF-3029: - Pax URL 2.0.0 has some issue about Java8 support. I would recommend to go to Pax URL 2.1.0-SNAPSHOT for now. > Support encryption of Maven repo passwords > -- > > Key: KARAF-3029 > URL: https://issues.apache.org/jira/browse/KARAF-3029 > Project: Karaf > Issue Type: Improvement >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.4.0, 4.0.0, 3.0.2 > > > Maven already provides a nice mechanism to encrypt server passwords (see > http://maven.apache.org/guides/mini/guide-encryption.html) but pax-url-mvn > ignores this information and requires a plaintext password be added to the > repo URL. This is already fixed in pax-url-aether 2.0.0 so I'm looking at > using that. Just should already be working for 4.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-3029) Support encryption of Maven repo passwords
[ https://issues.apache.org/jira/browse/KARAF-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3029: Fix Version/s: 3.0.2 > Support encryption of Maven repo passwords > -- > > Key: KARAF-3029 > URL: https://issues.apache.org/jira/browse/KARAF-3029 > Project: Karaf > Issue Type: Improvement >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.4.0, 4.0.0, 3.0.2 > > > Maven already provides a nice mechanism to encrypt server passwords (see > http://maven.apache.org/guides/mini/guide-encryption.html) but pax-url-mvn > ignores this information and requires a plaintext password be added to the > repo URL. This is already fixed in pax-url-aether 2.0.0 so I'm looking at > using that. Just should already be working for 4.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (KARAF-3029) Support encryption of Maven repo passwords
Jonathan Anstey created KARAF-3029: -- Summary: Support encryption of Maven repo passwords Key: KARAF-3029 URL: https://issues.apache.org/jira/browse/KARAF-3029 Project: Karaf Issue Type: Improvement Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.4.0, 4.0.0 Maven already provides a nice mechanism to encrypt server passwords (see http://maven.apache.org/guides/mini/guide-encryption.html) but pax-url-mvn ignores this information and requires a plaintext password be added to the repo URL. This is already fixed in pax-url-aether 2.0.0 so I'm looking at using that. Just should already be working for 4.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-1545) Jar files in lib directory require "karaf-" prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026471#comment-14026471 ] Jean-Baptiste Onofré commented on KARAF-1545: - ping ? > Jar files in lib directory require "karaf-" prefix in order to be loaded > > > Key: KARAF-1545 > URL: https://issues.apache.org/jira/browse/KARAF-1545 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 2.2.2 > Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. > Java home: /home/jcarman/Programs/jdk1.6.0_32/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" >Reporter: James Carman >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.12, 2.4.0, 3.0.2, 2.3.6 > > Attachments: karaf-3.0_1545.diff > > > I was trying to configure JDBC fail-over, so I put my mysql driver jar in the > KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the > advice of someone on IRC, I changed the name to > "karaf-mysql-connector-java.jar" and it started working. Why the karaf- > prefix requirement? If that's the intended behavior, then please update the > README file in the lib directory. It says: > "Any jar in this folder will be part of the main classloader used to load > Karaf." -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-3010) jclouds-commands cannot resolve correct version of Karaf shell
[ https://issues.apache.org/jira/browse/KARAF-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026459#comment-14026459 ] Jean-Baptiste Onofré commented on KARAF-3010: - Karaf 3.0.1 provides console.jline 2.11.0 which is newer than 2.2.0 (it's 2.11.0, not 2.1.1.0). console.jline 2.2.0 is pretty old and can't work with "new" blueprint version: it's normal. However, with the jclouds wiring should be able to use 2.11.0 instead of 2.2.0 (>= 2.2.0). Let me try to reproduce to understand the problem. I'm still thinking that the problem is in jclouds, not in Karaf. > jclouds-commands cannot resolve correct version of Karaf shell > -- > > Key: KARAF-3010 > URL: https://issues.apache.org/jira/browse/KARAF-3010 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Affects Versions: 3.0.1 >Reporter: Ryan Moquin >Assignee: Jean-Baptiste Onofré > > Installing the jclouds-commands feature will fail due to it looking for the > karaf shell console bundle minimum version 2.2.0, but Karaf 3.0.1 uses > version 2.11.0. > karaf@root()> feature:install jclouds-commands > Error executing command: Could not start bundle > mvn:org.apache.jclouds.karaf/commands/1.7.2 in feature(s) > jclouds-commands-1.7.2: Unres > olved constraint in bundle org.apache.jclouds.karaf.commands [135]: Unable to > resolve 135.0: missing requirement [135.0] osgi.wiring.pa > ckage; > (&(osgi.wiring.package=org.apache.karaf.shell.console.jline)(version>=2.2.0)) > Manually installing it, will prevent that error: > karaf@root()> bundle:install > mvn:org.apache.karaf.shell/org.apache.karaf.shell.console/2.2.0 > but when trying to install the feature again: > karaf@root()> feature:install jclouds-commands > Error executing command: Could not start bundle > mvn:org.apache.jclouds.karaf/commands/1.7.2 in feature(s) > jclouds-commands-1.7.2: Unres > olved constraint in bundle org.apache.jclouds.karaf.commands [189]: Unable to > resolve 189.0: missing requirement [189.0] osgi.wiring.pa > ckage; > (&(osgi.wiring.package=org.apache.karaf.shell.console.jline)(version>=2.2.0)) > [caused by: Unable to resolve 141.0: missing requi > rement [141.0] osgi.wiring.package; > (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=0.3.0)(!(version>=1.0.0)))] > Shows that the karaf shell console bundle version 2.2.0 is relying on some > old bundle versions. If I list the headers of version 2.2.0 to see what all > is wrong, these are the lines in the manifest it flags as unresolved: > org.apache.aries.blueprint;version="[0.3,1)", > org.apache.aries.blueprint.mutable;version="[0.3,1)", > org.apache.karaf.jaas.modules;version="[2.2,3)", > org.fusesource.hawtjni.runtime;version="[1.0,2)",: -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (KARAF-3010) jclouds-commands cannot resolve correct version of Karaf shell
[ https://issues.apache.org/jira/browse/KARAF-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-3010: --- Assignee: Jean-Baptiste Onofré > jclouds-commands cannot resolve correct version of Karaf shell > -- > > Key: KARAF-3010 > URL: https://issues.apache.org/jira/browse/KARAF-3010 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Affects Versions: 3.0.1 >Reporter: Ryan Moquin >Assignee: Jean-Baptiste Onofré > > Installing the jclouds-commands feature will fail due to it looking for the > karaf shell console bundle minimum version 2.2.0, but Karaf 3.0.1 uses > version 2.11.0. > karaf@root()> feature:install jclouds-commands > Error executing command: Could not start bundle > mvn:org.apache.jclouds.karaf/commands/1.7.2 in feature(s) > jclouds-commands-1.7.2: Unres > olved constraint in bundle org.apache.jclouds.karaf.commands [135]: Unable to > resolve 135.0: missing requirement [135.0] osgi.wiring.pa > ckage; > (&(osgi.wiring.package=org.apache.karaf.shell.console.jline)(version>=2.2.0)) > Manually installing it, will prevent that error: > karaf@root()> bundle:install > mvn:org.apache.karaf.shell/org.apache.karaf.shell.console/2.2.0 > but when trying to install the feature again: > karaf@root()> feature:install jclouds-commands > Error executing command: Could not start bundle > mvn:org.apache.jclouds.karaf/commands/1.7.2 in feature(s) > jclouds-commands-1.7.2: Unres > olved constraint in bundle org.apache.jclouds.karaf.commands [189]: Unable to > resolve 189.0: missing requirement [189.0] osgi.wiring.pa > ckage; > (&(osgi.wiring.package=org.apache.karaf.shell.console.jline)(version>=2.2.0)) > [caused by: Unable to resolve 141.0: missing requi > rement [141.0] osgi.wiring.package; > (&(osgi.wiring.package=org.apache.aries.blueprint)(version>=0.3.0)(!(version>=1.0.0)))] > Shows that the karaf shell console bundle version 2.2.0 is relying on some > old bundle versions. If I list the headers of version 2.2.0 to see what all > is wrong, these are the lines in the manifest it flags as unresolved: > org.apache.aries.blueprint;version="[0.3,1)", > org.apache.aries.blueprint.mutable;version="[0.3,1)", > org.apache.karaf.jaas.modules;version="[2.2,3)", > org.fusesource.hawtjni.runtime;version="[1.0,2)",: -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2563) Compilation fails with JDK 8 ea
[ https://issues.apache.org/jira/browse/KARAF-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2563: Fix Version/s: 3.0.2 > Compilation fails with JDK 8 ea > --- > > Key: KARAF-2563 > URL: https://issues.apache.org/jira/browse/KARAF-2563 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.2 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-2961) When a feature is generated from a bundle project, include that bundle in the feature
[ https://issues.apache.org/jira/browse/KARAF-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026309#comment-14026309 ] Stuart McCulloch commented on KARAF-2961: - Just wondering if there's an ETA for the next 3.x release of karaf-maven-plugin? It would be really helpful if this could be included - thanks. > When a feature is generated from a bundle project, include that bundle in the > feature > - > > Key: KARAF-2961 > URL: https://issues.apache.org/jira/browse/KARAF-2961 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Reporter: Stuart McCulloch >Assignee: Jean-Baptiste Onofré > > We're migrating a custom plugin framework over to Karaf and would like to > both create the OSGi bundle and generate the associated Karaf feature in the > same Maven project. Otherwise downstream clients will need to create two > Maven projects for each plugin: one to create the bundle, and one to create > the Karaf feature. > The proposed change is to consider the project packaging, and if it is > "bundle" then include the main project artifact (ie. the bundle itself) in > the generated feature. This requires no configuration change and should not > affect anyone generating features in isolation. We could also add a new flag > such as "includeProjectArtifact" so this change has to be explicitly enabled, > if people prefer. -- This message was sent by Atlassian JIRA (v6.2#6252)
