[jira] [Commented] (KARAF-4603) Nashorn support in Karaf
[
https://issues.apache.org/jira/browse/KARAF-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376873#comment-16376873
]
Claus Ibsen commented on KARAF-4603:
Mind you need to apply the PR
[https://github.com/apache/camel/pull/1190]
On Apache Camel so it imports that nashhorn api
> Nashorn support in Karaf
>
>
> Key: KARAF-4603
> URL: https://issues.apache.org/jira/browse/KARAF-4603
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.7
> Environment: Ubuntu 16.04
> OpenJDK 8 64-bit
>Reporter: Roman Sakno
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.1.2, 4.0.10, 4.2.0.M1
>
>
> I can't use JavaScript scripting in Karaf on Java 8 because
> ScriptEngineFactory implementation (provided by Nashorn) is located in system
> package {{jdk.nashorn.api.scripting}}. In Java 7, Rhino implementation is
> located in package {{com.sun.script.javascript}}. By default, Karaf offers
> some system packages (including {{com.sun}}) in configuration property
> {{org.osgi.framework.bootdelegation}} which is defined in file
> {{etc/config.properties}}. That's why Rhino available from Karaf. It will be
> great if you add {{jdk.nashorn}} to boot delegation by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-4603) Nashorn support in Karaf
[
https://issues.apache.org/jira/browse/KARAF-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376872#comment-16376872
]
Claus Ibsen commented on KARAF-4603:
Still fails - just tried with Karaf 4.1.5
{code:java}
davsclaus:/opt/apache-karaf-4.1.5/$ bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.5)
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 camel 2.21.0-SNAPSHOT
Adding feature url
mvn:org.apache.camel.karaf/apache-camel/2.21.0-SNAPSHOT/xml/features
karaf@root()> feature:install camel
karaf@root()> feature:install camel-script
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=camel-script; type=karaf.feature;
version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]";
filter:="(&(osgi.identity=camel-script)(type=karaf.feature)(version>=2.21.0.SNAPSHOT)(version<=2.21.0.SNAPSHOT))"
[caused by: Unable to resolve camel-script/2.21.0.SNAPSHOT: missing
requirement [camel-script/2.21.0.SNAPSHOT] osgi.identity;
osgi.identity=org.apache.camel.camel-script; type=osgi.bundle;
version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.camel.camel-script/2.21.0.SNAPSHOT: missing
requirement [org.apache.camel.camel-script/2.21.0.SNAPSHOT]
osgi.wiring.package;
filter:="(osgi.wiring.package=jdk.nashorn.api.scripting)"]]{code}
> Nashorn support in Karaf
>
>
> Key: KARAF-4603
> URL: https://issues.apache.org/jira/browse/KARAF-4603
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.7
> Environment: Ubuntu 16.04
> OpenJDK 8 64-bit
>Reporter: Roman Sakno
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.1.2, 4.0.10, 4.2.0.M1
>
>
> I can't use JavaScript scripting in Karaf on Java 8 because
> ScriptEngineFactory implementation (provided by Nashorn) is located in system
> package {{jdk.nashorn.api.scripting}}. In Java 7, Rhino implementation is
> located in package {{com.sun.script.javascript}}. By default, Karaf offers
> some system packages (including {{com.sun}}) in configuration property
> {{org.osgi.framework.bootdelegation}} which is defined in file
> {{etc/config.properties}}. That's why Rhino available from Karaf. It will be
> great if you add {{jdk.nashorn}} to boot delegation by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-4603) Nashorn support in Karaf
[
https://issues.apache.org/jira/browse/KARAF-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309453#comment-16309453
]
Claus Ibsen commented on KARAF-4603:
Are you guys looking into this?
> Nashorn support in Karaf
>
>
> Key: KARAF-4603
> URL: https://issues.apache.org/jira/browse/KARAF-4603
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.7
> Environment: Ubuntu 16.04
> OpenJDK 8 64-bit
>Reporter: Roman Sakno
>Assignee: Guillaume Nodet
> Fix For: 3.0.9, 4.1.2, 4.0.10, 4.2.0.M1
>
>
> I can't use JavaScript scripting in Karaf on Java 8 because
> ScriptEngineFactory implementation (provided by Nashorn) is located in system
> package {{jdk.nashorn.api.scripting}}. In Java 7, Rhino implementation is
> located in package {{com.sun.script.javascript}}. By default, Karaf offers
> some system packages (including {{com.sun}}) in configuration property
> {{org.osgi.framework.bootdelegation}} which is defined in file
> {{etc/config.properties}}. That's why Rhino available from Karaf. It will be
> great if you add {{jdk.nashorn}} to boot delegation by default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-4603) Nashorn support in Karaf
[
https://issues.apache.org/jira/browse/KARAF-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303627#comment-16303627
]
Claus Ibsen commented on KARAF-4603:
Karaf 4.1.3
> Nashorn support in Karaf
>
>
> Key: KARAF-4603
> URL: https://issues.apache.org/jira/browse/KARAF-4603
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.7
> Environment: Ubuntu 16.04
> OpenJDK 8 64-bit
>Reporter: Roman Sakno
>Assignee: Guillaume Nodet
> Fix For: 3.0.9, 4.1.2, 4.0.10, 4.2.0.M1
>
>
> I can't use JavaScript scripting in Karaf on Java 8 because
> ScriptEngineFactory implementation (provided by Nashorn) is located in system
> package {{jdk.nashorn.api.scripting}}. In Java 7, Rhino implementation is
> located in package {{com.sun.script.javascript}}. By default, Karaf offers
> some system packages (including {{com.sun}}) in configuration property
> {{org.osgi.framework.bootdelegation}} which is defined in file
> {{etc/config.properties}}. That's why Rhino available from Karaf. It will be
> great if you add {{jdk.nashorn}} to boot delegation by default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-4603) Nashorn support in Karaf
[
https://issues.apache.org/jira/browse/KARAF-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303306#comment-16303306
]
Claus Ibsen commented on KARAF-4603:
This does not work as when you install a bundle that uses this nashhorn it
still fails
{code}
karaf@root()> feature:install camel-script-javascript
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=camel-script-javascript; type=karaf.feature;
version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]";
filter:="(&(osgi.identity=camel-script-javascript)(type=karaf.feature)(version>=2.21.0.SNAPSHOT)(version<=2.21.0.SNAPSHOT))"
[caused by: Unable to resolve camel-script-javascript/2.21.0.SNAPSHOT: missing
requirement [camel-script-javascript/2.21.0.SNAPSHOT] osgi.identity;
osgi.identity=camel-script; type=karaf.feature;
version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]" [caused by: Unable to resolve
camel-script/2.21.0.SNAPSHOT: missing requirement
[camel-script/2.21.0.SNAPSHOT] osgi.identity;
osgi.identity=org.apache.camel.camel-script; type=osgi.bundle;
version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.camel.camel-script/2.21.0.SNAPSHOT: missing
requirement [org.apache.camel.camel-script/2.21.0.SNAPSHOT]
osgi.wiring.package;
filter:="(osgi.wiring.package=jdk.nashorn.api.scripting)"]]]
{code}
Only if I add this line to the etc/jre.properties file I can get it to work
jdk.nashorn.api.scripting, \
> Nashorn support in Karaf
>
>
> Key: KARAF-4603
> URL: https://issues.apache.org/jira/browse/KARAF-4603
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.7
> Environment: Ubuntu 16.04
> OpenJDK 8 64-bit
>Reporter: Roman Sakno
>Assignee: Guillaume Nodet
> Fix For: 3.0.9, 4.1.2, 4.0.10, 4.2.0.M1
>
>
> I can't use JavaScript scripting in Karaf on Java 8 because
> ScriptEngineFactory implementation (provided by Nashorn) is located in system
> package {{jdk.nashorn.api.scripting}}. In Java 7, Rhino implementation is
> located in package {{com.sun.script.javascript}}. By default, Karaf offers
> some system packages (including {{com.sun}}) in configuration property
> {{org.osgi.framework.bootdelegation}} which is defined in file
> {{etc/config.properties}}. That's why Rhino available from Karaf. It will be
> great if you add {{jdk.nashorn}} to boot delegation by default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5392) watch command throws NPE
Claus Ibsen created KARAF-5392:
--
Summary: watch command throws NPE
Key: KARAF-5392
URL: https://issues.apache.org/jira/browse/KARAF-5392
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.2
Reporter: Claus Ibsen
Priority: Minor
If you run the watch command you get a NPE
{code}
java.lang.NullPointerException
at org.apache.felix.gogo.jline.Posix.lambda$watch$6(Posix.java:872)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
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:748)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-4921) Expose more versions of slf4j api
[ https://issues.apache.org/jira/browse/KARAF-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903087#comment-15903087 ] Claus Ibsen commented on KARAF-4921: This keeps being a problem even on latest 4.1.0 release. > Expose more versions of slf4j api > - > > Key: KARAF-4921 > URL: https://issues.apache.org/jira/browse/KARAF-4921 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.8 >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré > > See CAMEL-10363 > This causes some 3rd party osgi bundles not be able to install and run in > karaf, because its shipped with too old slf4j api versions. > Please add newer versions of the slf4j api into karaf. See that CAMEL ticket > for more details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-4921) Expose more versions of slf4j api
Claus Ibsen created KARAF-4921: -- Summary: Expose more versions of slf4j api Key: KARAF-4921 URL: https://issues.apache.org/jira/browse/KARAF-4921 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.8 Reporter: Claus Ibsen See CAMEL-10363 This causes some 3rd party osgi bundles not be able to install and run in karaf, because its shipped with too old slf4j api versions. Please add newer versions of the slf4j api into karaf. See that CAMEL ticket for more details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4582) karaf-utils - Export packages so its a real OSGi bundle
Claus Ibsen created KARAF-4582:
--
Summary: karaf-utils - Export packages so its a real OSGi bundle
Key: KARAF-4582
URL: https://issues.apache.org/jira/browse/KARAF-4582
Project: Karaf
Issue Type: Improvement
Affects Versions: 4.0.5
Reporter: Claus Ibsen
The artifact
org.apache.karaf
org.apache.karaf.util
${karaf4-version}
Is not exporting any packages and is some kind of NON reusable bundle.
Karaf should export these util packages so end users can USE the code.
Related problem CAMEL-10063
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4455) Testing with pax-exam - Allow to specify the name of the real unpack directory
Claus Ibsen created KARAF-4455:
--
Summary: Testing with pax-exam - Allow to specify the name of the
real unpack directory
Key: KARAF-4455
URL: https://issues.apache.org/jira/browse/KARAF-4455
Project: Karaf
Issue Type: Improvement
Reporter: Claus Ibsen
When testing with pax-exam and you run a bunch of tests its really annoying
that it uses random directory names.
Then its hard to track down which of these directory has the karaf container
you want to inspect, such as its logs, or try to start it manually etc.
For example
{code}
davsclaus:~/workspace/camel/tests/camel-itest-karaf/target/paxexam/unpack
(master)/$ ls
0901403a-88f0-47dd-8853-30d424419b173b3dc26e-7186-4c85-a11a-d19e9b24211a
66227858-ce1c-400d-a276-1ddcee2c6f18caf36185-315c-4fff-ada5-472ea6288160
0f0c5c99-26fa-462f-a394-45212bd10ad93d1b8af9-fc10-48f1-83d4-1fb09461d3cc
7e82acca-19db-44dd-8c6b-04c0101df22fcf9636d0-f44f-4be7-a149-bce392530a46
11bd7128-a93d-4fbd-9def-279dfcc07204400a761d-71d5-47d7-84c1-203cbbec5b9f
80961ac2-e0d6-4f0f-9460-d7ef077f0c3cd1daf2ed-b661-4ab5-8950-069f4f7772ad
129eca6c-39cd-46dc-887b-870c666a5bb047d86021-c604-4cce-87aa-d5f168e7f329
945aae77-f15a-4445-939c-22df23267d3be13af1f7-ebe3-4e9d-89f2-cc2acd8608d0
149374c0-da94-40ac-9073-2c37174797714ece834c-7095-4fd3-9f55-e686f217e7ee
99dbab81-7769-406d-8b2f-9de7e516b3e8eba1a3c8-acc7-4b87-ab75-abccfdf45bb5
1617ee3f-b128-4883-a52a-56c557242b6a52f82410-cd44-4d8c-abac-d93615586f5b
9b9eded6-4732-473f-9a92-be93f18f1073f1ba6e7d-52bd-47dd-bbb5-50d026b59f04
2adde2e8-3dcd-4d42-875e-b9ed8fd7722755d1d84d-be28-4d3e-80ef-b25f8ce74492
acd39400-bf91-465b-8cc2-34119393e92ff379a0c3-8f9c-457c-8fa9-fffb94662d1d
2e371760-99c2-49c8-94e4-b7a037f9e5bd57c803e5-219d-4184-a506-6371a409596d
ace1f473-8102-42dc-b8a3-23c1ea153a48f91a762c-83cf-4bd8-9f40-67cf7dcddff7
3201d6ef-bd16-40c4-af07-d6b651acca395f04f917-4f61-482b-99f8-3cdd66e8e9d7
beed3685-4a12-4bca-a9b3-1f2d6a5353be
{code}
So if you could set the unpack directory and its name its using, then you give
those names a meaning name, such as the name of your unit test etc.
For example with a new unpackName("myTestName") method.
{code}
KarafDistributionOption.karafDistributionConfiguration()
.frameworkUrl(maven().groupId("org.apache.karaf").artifactId("apache-karaf").type("tar.gz").versionAsInProject())
.karafVersion(karafVersion)
.name("Apache Karaf")
.useDeployFolder(false).unpackDirectory(new
File("target/paxexam/unpack/")).unpackName("myTestName"),
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing
[
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated KARAF-4415:
---
Issue Type: Documentation (was: Bug)
> 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
>Priority: Minor
>
> 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
[
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193416#comment-15193416
]
Claus Ibsen commented on KARAF-4415:
You should update and fix the documentation then, its out of date.
Also on this page
http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin.html
> 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: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>
> 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-4415) karaf-maven-plugin - The feature validate goal is missing
[
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated KARAF-4415:
---
Priority: Minor (was: Major)
> 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: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>Priority: Minor
>
> 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
[
https://issues.apache.org/jira/browse/KARAF-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192218#comment-15192218
]
Claus Ibsen commented on KARAF-4415:
The plugin has the goal in karaf 3.0.6 with that same setting as above, but
change the version from 4.0.3 to 3.0.6
{code}
Downloaded:
https://repo.maven.apache.org/maven2/org/apache/karaf/deployer/org.apache.karaf.deployer.blueprint/3.0.6/org.apache.karaf.deployer.blueprint-3.0.6.jar
(30 KB at 46.7 KB/sec)
[INFO] == Preparing for validation ==
[INFO] - getting list of system bundle exports
[INFO] - getting list of provided bundle exports
[INFO] scanning org.apache.camel.karaf:apache-camel:pom:2.17-SNAPSHOT for
exports
...
{code}
> 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: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.4
>Reporter: Claus Ibsen
>
> According to this guide
> http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin.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] [Created] (KARAF-4415) karaf-maven-plugin - The feature validate goal is missing
Claus Ibsen created KARAF-4415:
--
Summary: 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: Bug
Components: karaf-tooling
Affects Versions: 4.0.4
Reporter: Claus Ibsen
According to this guide
http://karaf.apache.org/manual/latest/developers-guide/karaf-maven-plugin.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-4242) Add apache artemis to repo-add shorthand list
[ https://issues.apache.org/jira/browse/KARAF-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074924#comment-15074924 ] Claus Ibsen commented on KARAF-4242: [~jbonofre] can you do this also how that you have added ignite? > Add apache artemis to repo-add shorthand list > - > > Key: KARAF-4242 > URL: https://issues.apache.org/jira/browse/KARAF-4242 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Claus Ibsen > > Today you can add cxf, camel, activemq, etc using > feature:repo-add camel 2.16.1 > We should add artemis to that list too, so you can do > feature:repo-add artemis 1.2.0 > Today you have to use > feature:repo-add mvn:org.apache.activemq/artemis-features/1.2.1-SNAPSHOT/xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4243) Add apache ignite to feature repo:add shorthand
Claus Ibsen created KARAF-4243: -- Summary: Add apache ignite to feature repo:add shorthand Key: KARAF-4243 URL: https://issues.apache.org/jira/browse/KARAF-4243 Project: Karaf Issue Type: Improvement Reporter: Claus Ibsen See https://apacheignite.readme.io/docs/osgi-installation-in-karaf We should add a shorthand so you can do feature:repo-add ignite 1.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4242) Add apache artemis to repo-add shorthand list
Claus Ibsen created KARAF-4242: -- Summary: Add apache artemis to repo-add shorthand list Key: KARAF-4242 URL: https://issues.apache.org/jira/browse/KARAF-4242 Project: Karaf Issue Type: Improvement Components: karaf-feature Reporter: Claus Ibsen Today you can add cxf, camel, activemq, etc using feature:repo-add camel 2.16.1 We should add artemis to that list too, so you can do feature:repo-add artemis 1.2.0 Today you have to use feature:repo-add mvn:org.apache.activemq/artemis-features/1.2.1-SNAPSHOT/xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3939) Karaf 2.4.x - Upgrade to latest spring 3.2.x release
Claus Ibsen created KARAF-3939: -- Summary: Karaf 2.4.x - Upgrade to latest spring 3.2.x release Key: KARAF-3939 URL: https://issues.apache.org/jira/browse/KARAF-3939 Project: Karaf Issue Type: Task Affects Versions: 2.4.3 Reporter: Claus Ibsen Should upgrade to spring 3.2.14. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3940) Make it possible / easy to configure which spring version Karaf uses
Claus Ibsen created KARAF-3940: -- Summary: Make it possible / easy to configure which spring version Karaf uses Key: KARAF-3940 URL: https://issues.apache.org/jira/browse/KARAF-3940 Project: Karaf Issue Type: Improvement Affects Versions: 2.4.3 Reporter: Claus Ibsen It would be great if the spring version that karaf uses is configured in one of the etc config files. So people can easily upgrade by changing the version in that file. Today you cannot do that and its a hazzle to upgrade spring. In fact very hard as the spring version is hardcoded in the features file truemvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features The reason is that spring has frequent releases and often they have security issues in their new releases. Or some 3rd party libraries with osgi ranges requires a higher version, even on patch level, eg 3.2.13 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3940) Make it possible / easy to configure which spring version Karaf uses
[ https://issues.apache.org/jira/browse/KARAF-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704550#comment-14704550 ] Claus Ibsen commented on KARAF-3940: Well something to make it easy for end users to upgrade spring in the current version of karaf. Today you are locked down on the shipped version, and have to wait for new release to upgrade. PS: A bit same problem for jetty. But I guess that one is maybe harder. But would be nice to just change a version in a .cfg file and restart karaf and its upgraded. If the versions is hardcoded in features xml file that are resovled from maven central its harder to upgrade/change the version. And spring is not 1 bundle so there are many bundles to upgrade manually and it would be an error prone procedure. Maybe there could be a version alias config file, so when karaf resolve a version of a bundle, eg bundle A version 1.2.3, then lookup in the version alias and see if there is a mapping. So you can overrule/control all versions. Make it possible / easy to configure which spring version Karaf uses Key: KARAF-3940 URL: https://issues.apache.org/jira/browse/KARAF-3940 Project: Karaf Issue Type: Improvement Affects Versions: 2.4.3 Reporter: Claus Ibsen It would be great if the spring version that karaf uses is configured in one of the etc config files. So people can easily upgrade by changing the version in that file. Today you cannot do that and its a hazzle to upgrade spring. In fact very hard as the spring version is hardcoded in the features file truemvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features The reason is that spring has frequent releases and often they have security issues in their new releases. Or some 3rd party libraries with osgi ranges requires a higher version, even on patch level, eg 3.2.13 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3940) Make it possible / easy to configure which spring version Karaf uses
[ https://issues.apache.org/jira/browse/KARAF-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704415#comment-14704415 ] Claus Ibsen commented on KARAF-3940: Wonder if a general solution could be to allow to upgrade / change versions with this command karaf@root features:listversions spring VersionRepositoryRepository URL [3.1.4.RELEASE ] spring-2.4.3 mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features [3.2.11.RELEASE_1] spring-2.4.3 mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features [4.0.7.RELEASE_1 ] spring-2.4.3 mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features [4.1.6.RELEASE_1 ] spring-2.4.3 mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features eg have a way of changing the version, so you can say 3.2.11_RELEASE_1 - 3.2.14_RELEASE_1. Make it possible / easy to configure which spring version Karaf uses Key: KARAF-3940 URL: https://issues.apache.org/jira/browse/KARAF-3940 Project: Karaf Issue Type: Improvement Affects Versions: 2.4.3 Reporter: Claus Ibsen It would be great if the spring version that karaf uses is configured in one of the etc config files. So people can easily upgrade by changing the version in that file. Today you cannot do that and its a hazzle to upgrade spring. In fact very hard as the spring version is hardcoded in the features file truemvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features The reason is that spring has frequent releases and often they have security issues in their new releases. Or some 3rd party libraries with osgi ranges requires a higher version, even on patch level, eg 3.2.13 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3938) NPE in Felix when installing camel-spark-rest feature
Claus Ibsen created KARAF-3938:
--
Summary: 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
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] [Created] (KARAF-3427) Upgrade to JAXB 2.2.11 which now is OSGi bundle
Claus Ibsen created KARAF-3427: -- Summary: Upgrade to JAXB 2.2.11 which now is OSGi bundle Key: KARAF-3427 URL: https://issues.apache.org/jira/browse/KARAF-3427 Project: Karaf Issue Type: Task Reporter: Claus Ibsen Priority: Minor We are upgrading Camel to use 2.2.11 which is OSGi bundles. Then we do not need the SMX bundle wrapper anymore. Not sure if karaf comes with JAXB bundles out of the box or as features. But if so then it would be good to upgrade here as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3401) Typo in users.properties
Claus Ibsen created KARAF-3401: -- Summary: Typo in users.properties Key: KARAF-3401 URL: https://issues.apache.org/jira/browse/KARAF-3401 Project: Karaf Issue Type: Task Affects Versions: 2.4.0 Reporter: Claus Ibsen Priority: Trivial Noticed this All users, grousp, and roles entered in this file are available after Karaf startup groups is spelt wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3378) bin\client.bat on Windows fails to read SSH_PORT from env causing a NumberFormatException
Claus Ibsen created KARAF-3378:
--
Summary: bin\client.bat on Windows fails to read SSH_PORT from env
causing a NumberFormatException
Key: KARAF-3378
URL: https://issues.apache.org/jira/browse/KARAF-3378
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.2, 2.4.0
Environment: Windows
Reporter: Claus Ibsen
Priority: Minor
If you run Karaf on windows and define the SSH_PORT as a env variable, then if
you want to use bin/client.bat to have a shell for the running karaf, then it
fails with a
{code}
C:\mykarafbin\client.bat
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:569)
at java.lang.Integer.parseInt(Integer.java:615)
at org.apache.karaf.client.Main.main(Main.java:58)
{code}
The ENV variable has been set with
{code}
SSH_PORT=50123
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3377) Starting Karaf on Windows changes console title
Claus Ibsen created KARAF-3377: -- Summary: Starting Karaf on Windows changes console title Key: KARAF-3377 URL: https://issues.apache.org/jira/browse/KARAF-3377 Project: Karaf Issue Type: Bug Affects Versions: 3.0.2, 2.4.0 Environment: Windows Reporter: Claus Ibsen Priority: Minor If you want to start karaf on windows, you can use bin\start And it startup karaf, but the start.bat script has an issue. a) it set the title of current command window to KARAF_TITLE b) it sets the spawned command window to hardcoded Karaf The problem is that it should not do (a) as the current command window is just a CLI to control karaf, not to run the karaf itself. And for (b) it should actually use KARAF_TITLE as the title, so you can control this. This code at should be removed https://github.com/apache/karaf/blob/master/assemblies/features/framework/src/main/filtered-resources/resources/bin/start.bat#L33 And the KARAF_TITLE code from above should be used here instead, eg so the spawned window gets the title of choice https://github.com/apache/karaf/blob/master/assemblies/features/framework/src/main/filtered-resources/resources/bin/start.bat#L90 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3346) Stopping Karaf 2.4.0 prints ugly ERRORS in the log
Claus Ibsen created KARAF-3346:
--
Summary: Stopping Karaf 2.4.0 prints ugly ERRORS in the log
Key: KARAF-3346
URL: https://issues.apache.org/jira/browse/KARAF-3346
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 2.4.0
Reporter: Claus Ibsen
Priority: Minor
Untar a vaniallia apache karaf 2.4.0
bin/karaf
Let it boot up, and type logout in the shell to exit
The log prints a bunch of MBean unregistering exceptions at ERROR level.
Ideally Karaf should shutdown cleanly.
{code}
Nov 04, 2014 12:00:50 PM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
2014-11-04 12:00:50,712 | INFO | FelixStartLevel | fileinstall
| 6 - org.apache.felix.fileinstall - 3.4.2 | Creating configuration from
org.apache.karaf.command.acl.features.cfg
2014-11-04 12:00:50,717 | INFO | FelixStartLevel | fileinstall
| 6 - org.apache.felix.fileinstall - 3.4.2 | Creating configuration from
jmx.acl.org.apache.karaf.security.jmx.cfg
2014-11-04 12:00:50,721 | INFO | FelixStartLevel | fileinstall
| 6 - org.apache.felix.fileinstall - 3.4.2 | Creating configuration from
org.apache.karaf.management.cfg
2014-11-04 12:00:50,724 | INFO | FelixStartLevel | fileinstall
| 6 - org.apache.felix.fileinstall - 3.4.2 | Creating configuration from
org.apache.karaf.command.acl.scope_bundle.cfg
2014-11-04 12:00:50,729 | INFO | FelixStartLevel | fileinstall
| 6 - org.apache.felix.fileinstall - 3.4.2 | Creating configuration from
jmx.acl.org.apache.karaf.bundle.cfg
2014-11-04 12:00:50,732 | INFO | FelixStartLevel | fileinstall
| 6 - org.apache.felix.fileinstall - 3.4.2 | Creating configuration from
org.apache.felix.fileinstall-deploy.cfg
2014-11-04 12:00:52,003 | INFO | pool-1-thread-1 | Activator
| 25 - org.apache.karaf.service.guard - 2.4.0 | Adding role-based
security to services with filter:
((osgi.command.scope=*)(osgi.command.function=*))
2014-11-04 12:00:52,158 | INFO | FelixStartLevel | BlueprintExtender
| 14 - org.apache.aries.blueprint.core - 1.4.1 | No quiesce support is
available, so blueprint components will not participate in quiesce operations
2014-11-04 12:00:52,568 | INFO | FelixStartLevel |
SecuredCommandConfigTransformer | 17 - org.apache.karaf.shell.console - 2.4.0
| Generating command ACL config org.apache.karaf.command.acl.features into
service ACL configs [org.apache.karaf.service.acl.command.features.install,
org.apache.karaf.service.acl.command.features.uninstall]
2014-11-04 12:00:52,575 | INFO | FelixStartLevel |
SecuredCommandConfigTransformer | 17 - org.apache.karaf.shell.console - 2.4.0
| Generating command ACL config org.apache.karaf.command.acl.osgi into service
ACL configs [org.apache.karaf.service.acl.command.osgi.watch,
org.apache.karaf.service.acl.command.osgi.uninstall,
org.apache.karaf.service.acl.command.osgi.shutdown,
org.apache.karaf.service.acl.command.osgi.refresh,
org.apache.karaf.service.acl.command.osgi.start-level,
org.apache.karaf.service.acl.command.osgi.start,
org.apache.karaf.service.acl.command.osgi.restart,
org.apache.karaf.service.acl.command.osgi.install,
org.apache.karaf.service.acl.command.osgi.stop,
org.apache.karaf.service.acl.command.osgi.update]
2014-11-04 12:00:52,599 | INFO | FelixStartLevel |
SecuredCommandConfigTransformer | 17 - org.apache.karaf.shell.console - 2.4.0
| Generating command ACL config org.apache.karaf.command.acl.jaas into service
ACL configs [org.apache.karaf.service.acl.command.jaas.update]
2014-11-04 12:00:52,602 | INFO | FelixStartLevel |
SecuredCommandConfigTransformer | 17 - org.apache.karaf.shell.console - 2.4.0
| Generating command ACL config org.apache.karaf.command.acl.config into
service ACL configs [org.apache.karaf.service.acl.command.config.propappend,
org.apache.karaf.service.acl.command.config.delete,
org.apache.karaf.service.acl.command.config.cancel,
org.apache.karaf.service.acl.command.config.propdel,
org.apache.karaf.service.acl.command.config.propset,
org.apache.karaf.service.acl.command.config.update,
org.apache.karaf.service.acl.command.config.edit]
2014-11-04 12:00:52,618 | INFO | FelixStartLevel |
SecuredCommandConfigTransformer | 17 - org.apache.karaf.shell.console - 2.4.0
| Generating command ACL config org.apache.karaf.command.acl.shell into service
ACL configs [org.apache.karaf.service.acl.command.shell.java,
org.apache.karaf.service.acl.command.shell.edit,
org.apache.karaf.service.acl.command.shell.exec,
org.apache.karaf.service.acl.command.shell.new]
2014-11-04 12:00:52,625 | INFO | FelixStartLevel |
SecuredCommandConfigTransformer | 17 - org.apache.karaf.shell.console - 2.4.0
| Generating command ACL config
[jira] [Created] (KARAF-3245) Upgrade spring from 3.2.9 to 3.2.11
Claus Ibsen created KARAF-3245: -- Summary: Upgrade spring from 3.2.9 to 3.2.11 Key: KARAF-3245 URL: https://issues.apache.org/jira/browse/KARAF-3245 Project: Karaf Issue Type: Task Affects Versions: 2.4.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.4.1 The new Karaf 2.4.0 release is using a bit older spring version 3.2.9. We should use the latest 3.2.11, which has latest security fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3245) Upgrade spring from 3.2.9 to 3.2.11
[ https://issues.apache.org/jira/browse/KARAF-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142144#comment-14142144 ] Claus Ibsen commented on KARAF-3245: feature:list shows [uninstalled] [3.2.9.RELEASE_1 ] springspring-2.4.0 Spring 3.2.x support Upgrade spring from 3.2.9 to 3.2.11 --- Key: KARAF-3245 URL: https://issues.apache.org/jira/browse/KARAF-3245 Project: Karaf Issue Type: Task Affects Versions: 2.4.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.4.1 The new Karaf 2.4.0 release is using a bit older spring version 3.2.9. We should use the latest 3.2.11, which has latest security fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3245) Upgrade spring from 3.2.9 to 3.2.11
[ https://issues.apache.org/jira/browse/KARAF-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142145#comment-14142145 ] Claus Ibsen commented on KARAF-3245: btw using the new 2.4.0 release. Upgrade spring from 3.2.9 to 3.2.11 --- Key: KARAF-3245 URL: https://issues.apache.org/jira/browse/KARAF-3245 Project: Karaf Issue Type: Task Affects Versions: 2.4.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.4.1 The new Karaf 2.4.0 release is using a bit older spring version 3.2.9. We should use the latest 3.2.11, which has latest security fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3222) Command description for osgi:shutdown could be improved
Claus Ibsen created KARAF-3222:
--
Summary: Command description for osgi:shutdown could be improved
Key: KARAF-3222
URL: https://issues.apache.org/jira/browse/KARAF-3222
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.7
Reporter: Claus Ibsen
Priority: Trivial
If you type `help` you see a list of commands with a short description
{code}
osgi:shutdown Shutdown the framework down.
{code}
That text may confuse people a bit as it says framework / what framework is
that???
Its better to say
{code}
osgi:shutdown Shutdown the Karaf container.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3217) Karaf shell - scr:info - Cannot coerce info() to any of [(String)]
Claus Ibsen created KARAF-3217:
--
Summary: Karaf shell - scr:info - Cannot coerce info() to any of
[(String)]
Key: KARAF-3217
URL: https://issues.apache.org/jira/browse/KARAF-3217
Project: Karaf
Issue Type: Bug
Components: karaf-scr, karaf-shell
Affects Versions: 2.3.7
Reporter: Claus Ibsen
Priority: Minor
To reproduce using a vanilla karaf 2.3.7
bin/karaf
features:install scr
scr:list
scr:aaa
scr:info
{code}
karaf@root scr:info
Error executing command: Cannot coerce info() to any of [(String)]
karaf@root log:tail
2014-09-09 11:48:49,932 | INFO | JMX OSGi Agent | core
| ? ? | 24 - org.apache.aries.jmx.core
- 1.1.1 | Registering org.osgi.jmx.framework.wiring.BundleWiringStateMBean to
MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@7f7c3215 with name
osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=e0fc1809-e35b-4124-b942-288b4499066e
2014-09-09 11:48:49,933 | INFO | JMX OSGi Agent | core
| ? ? | 24 - org.apache.aries.jmx.core
- 1.1.1 | Registering org.osgi.jmx.framework.FrameworkMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@7f7c3215 with name
osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=e0fc1809-e35b-4124-b942-288b4499066e
2014-09-09 11:48:49,934 | INFO | JMX OSGi Agent | core
| ? ? | 24 - org.apache.aries.jmx.core
- 1.1.1 | Registering org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@7f7c3215 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=e0fc1809-e35b-4124-b942-288b4499066e
2014-09-09 11:48:49,934 | INFO | JMX OSGi Agent | core
| ? ? | 24 - org.apache.aries.jmx.core
- 1.1.1 | Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to
MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@7f7c3215 with name
osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=e0fc1809-e35b-4124-b942-288b4499066e
2014-09-09 11:48:49,934 | INFO | JMX OSGi Agent | core
| ? ? | 24 - org.apache.aries.jmx.core
- 1.1.1 | Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@7f7c3215 with name
osgi.core:type=serviceState,version=1.7,framework=org.apache.felix.framework,uuid=e0fc1809-e35b-4124-b942-288b4499066e
2014-09-09 11:48:49,935 | INFO | JMX OSGi Agent | core
| ? ? | 24 - org.apache.aries.jmx.core
- 1.1.1 | Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@7f7c3215 with name
osgi.core:type=bundleState,version=1.7,framework=org.apache.felix.framework,uuid=e0fc1809-e35b-4124-b942-288b4499066e
2014-09-09 11:49:01,730 | INFO | l Console Thread | DetailsCommandComponent
| hell.scr.DetailsCommandComponent 67 | 57 - org.apache.karaf.shell.scr
- 2.3.7 | Activating the Apache Karaf SCR Details Command
2014-09-09 11:49:01,738 | INFO | l Console Thread | ListCommandComponent
| f.shell.scr.ListCommandComponent 61 | 57 - org.apache.karaf.shell.scr
- 2.3.7 | Activating the Apache Karaf SCR List Command
2014-09-09 11:49:01,741 | INFO | l Console Thread | ActivateCommandComponent
| ell.scr.ActivateCommandComponent 66 | 57 - org.apache.karaf.shell.scr
- 2.3.7 | Activating the Apache Karaf SCR Activate Command
2014-09-09 11:49:01,743 | INFO | l Console Thread | DeactivateCommandComponent
| l.scr.DeactivateCommandComponent 66 | 57 - org.apache.karaf.shell.scr
- 2.3.7 | Activating the Apache Karaf SCR Deactivate Command
2014-09-09 11:49:01,757 | INFO | l Console Thread | ScrServiceMBeanImpl
| scr.internal.ScrServiceMBeanImpl 78 | 58 -
org.apache.karaf.management.mbeans.scr - 2.3.7 | Activating the Apache Karaf
SCR Service MBean
2014-09-09 11:49:10,839 | ERROR | l Console Thread | Console
| araf.shell.console.jline.Console 213 | 14 -
org.apache.karaf.shell.console - 2.3.7 | Exception caught while executing
command
java.lang.IllegalArgumentException: Cannot coerce info() to any of [(String)]
at
org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:178)[14:org.apache.karaf.shell.console:2.3.7]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)[14:org.apache.karaf.shell.console:2.3.7]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[14:org.apache.karaf.shell.console:2.3.7]
at
[jira] [Created] (KARAF-3149) Karaf chooseurl for jclouds is wrong
Claus Ibsen created KARAF-3149:
--
Summary: Karaf chooseurl for jclouds is wrong
Key: KARAF-3149
URL: https://issues.apache.org/jira/browse/KARAF-3149
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.6
Reporter: Claus Ibsen
Priority: Minor
{code}
davsclaus:/opt/$ tar xf ~/Downloads/apache-karaf-2.3.6.tar.gz
davsclaus:/opt/$ cd apache-karaf-2.3.6/
davsclaus:/opt/apache-karaf-2.3.6/$ bin/karaf
__ __
/ //_/ __ _/ __/
/ , / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.3.6)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.
karaf@root features:chooseurl jclouds 1.8.0
Adding feature url mvn:org.jclouds.karaf/jclouds-karaf/1.8.0/xml/features
Error executing command: URL
[mvn:org.jclouds.karaf/jclouds-karaf/1.8.0/xml/features] could not be resolved.
karaf@root
{code}
The url should be something with apache jclouds.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (KARAF-3149) Karaf chooseurl for jclouds is wrong
[
https://issues.apache.org/jira/browse/KARAF-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087382#comment-14087382
]
Claus Ibsen commented on KARAF-3149:
Found this from Camel
repositorymvn:org.apache.jclouds.karaf/jclouds-karaf/${jclouds-version}/xml/features/repository
Karaf chooseurl for jclouds is wrong
Key: KARAF-3149
URL: https://issues.apache.org/jira/browse/KARAF-3149
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.6
Reporter: Claus Ibsen
Priority: Minor
{code}
davsclaus:/opt/$ tar xf ~/Downloads/apache-karaf-2.3.6.tar.gz
davsclaus:/opt/$ cd apache-karaf-2.3.6/
davsclaus:/opt/apache-karaf-2.3.6/$ bin/karaf
__ __
/ //_/ __ _/ __/
/ , / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.3.6)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.
karaf@root features:chooseurl jclouds 1.8.0
Adding feature url mvn:org.jclouds.karaf/jclouds-karaf/1.8.0/xml/features
Error executing command: URL
[mvn:org.jclouds.karaf/jclouds-karaf/1.8.0/xml/features] could not be
resolved.
karaf@root
{code}
The url should be something with apache jclouds.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (KARAF-3149) Karaf chooseurl for jclouds is wrong
[
https://issues.apache.org/jira/browse/KARAF-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087383#comment-14087383
]
Claus Ibsen commented on KARAF-3149:
Workaround is to do
features:addurl mvn:org.apache.jclouds.karaf/jclouds-karaf/1.8.0/xml/features
Karaf chooseurl for jclouds is wrong
Key: KARAF-3149
URL: https://issues.apache.org/jira/browse/KARAF-3149
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.6
Reporter: Claus Ibsen
Priority: Minor
{code}
davsclaus:/opt/$ tar xf ~/Downloads/apache-karaf-2.3.6.tar.gz
davsclaus:/opt/$ cd apache-karaf-2.3.6/
davsclaus:/opt/apache-karaf-2.3.6/$ bin/karaf
__ __
/ //_/ __ _/ __/
/ , / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.3.6)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.
karaf@root features:chooseurl jclouds 1.8.0
Adding feature url mvn:org.jclouds.karaf/jclouds-karaf/1.8.0/xml/features
Error executing command: URL
[mvn:org.jclouds.karaf/jclouds-karaf/1.8.0/xml/features] could not be
resolved.
karaf@root
{code}
The url should be something with apache jclouds.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (KARAF-3144) osgi:ls - Sort multi values before outputting so its easier readable
Claus Ibsen created KARAF-3144:
--
Summary: osgi:ls - Sort multi values before outputting so its
easier readable
Key: KARAF-3144
URL: https://issues.apache.org/jira/browse/KARAF-3144
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.5
Reporter: Claus Ibsen
Priority: Minor
The ls command is great to see the osgi services exported by the bundles.
But when the values is multi valued, then the data shown is listed in random
order.
{code}
karaf@root features:chooseurl camel 2.14-SNAPSHOT
adding feature url
mvn:org.apache.camel.karaf/apache-camel/2.14-SNAPSHOT/xml/features
karaf@root features:
features:addurl features:chooseurl features:info
features:install
features:listfeatures:listrepositoriesfeatures:listurl
features:listversions
features:refreshurl features:removerepositoryfeatures:removeurl
features:uninstall
karaf@root features:install camel
karaf@root features:install camel-metrics
karaf@root list
START LEVEL 100 , List Threshold: 50
ID State Blueprint SpringLevel Name
[ 60] [Active ] [] [ ] [ 50] camel-core
(2.14.0.SNAPSHOT)
[ 61] [Active ] [Created ] [ ] [ 50] camel-karaf-commands
(2.14.0.SNAPSHOT)
[ 75] [Active ] [] [ ] [ 50] geronimo-jta_1.1_spec
(1.1.1)
[ 76] [Active ] [] [ ] [ 50] camel-spring
(2.14.0.SNAPSHOT)
[ 77] [Active ] [Created ] [ ] [ 50] camel-blueprint
(2.14.0.SNAPSHOT)
[ 78] [Active ] [] [ ] [ 50] Metrics Core (3.0.2)
[ 79] [Active ] [] [ ] [ 50] camel-metrics
(2.14.0.SNAPSHOT)
karaf@root ls 60
You are about to access system bundle 60. Do you wish to continue (yes/no):
yes
camel-core (60) provides:
-
component = direct, vm, mock, bean, test, stub, validator, class, properties,
direct-vm, log, ref, xslt, browse, dataset, timer, file, controlbus, binding,
seda, rest, language, dataformat
objectClass = org.apache.camel.spi.ComponentResolver
service.id = 225
language = ref, constant, bean, simple, file, xtokenize, property, header,
xpath, tokenize
objectClass = org.apache.camel.spi.LanguageResolver
service.id = 226
dataformat = zip, string, serialization
objectClass = org.apache.camel.spi.DataFormatResolver
service.id = 227
objectClass = org.apache.camel.spi.TypeConverterLoader
service.id = 228
karaf@root
{code}
For example as shown above with Apache Camel where we have many components /
languages etc exported.
Would be nice to have the values sorted before they are printed to the console.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (KARAF-3144) osgi:ls - Sort multi values before outputting so its easier readable
[
https://issues.apache.org/jira/browse/KARAF-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079269#comment-14079269
]
Claus Ibsen commented on KARAF-3144:
eg for components you see
{code}
component = direct, vm, mock, bean, test, stub, validator, class, properties,
direct-vm, log, ref, xslt, browse, dataset, timer, file, controlbus, binding,
seda, rest, language, dataformat
{code}
But would be great if that was sorted
osgi:ls - Sort multi values before outputting so its easier readable
Key: KARAF-3144
URL: https://issues.apache.org/jira/browse/KARAF-3144
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.5
Reporter: Claus Ibsen
Priority: Minor
The ls command is great to see the osgi services exported by the bundles.
But when the values is multi valued, then the data shown is listed in random
order.
{code}
karaf@root features:chooseurl camel 2.14-SNAPSHOT
adding feature url
mvn:org.apache.camel.karaf/apache-camel/2.14-SNAPSHOT/xml/features
karaf@root features:
features:addurl features:chooseurl features:info
features:install
features:listfeatures:listrepositoriesfeatures:listurl
features:listversions
features:refreshurl features:removerepositoryfeatures:removeurl
features:uninstall
karaf@root features:install camel
karaf@root features:install camel-metrics
karaf@root list
START LEVEL 100 , List Threshold: 50
ID State Blueprint SpringLevel Name
[ 60] [Active ] [] [ ] [ 50] camel-core
(2.14.0.SNAPSHOT)
[ 61] [Active ] [Created ] [ ] [ 50] camel-karaf-commands
(2.14.0.SNAPSHOT)
[ 75] [Active ] [] [ ] [ 50] geronimo-jta_1.1_spec
(1.1.1)
[ 76] [Active ] [] [ ] [ 50] camel-spring
(2.14.0.SNAPSHOT)
[ 77] [Active ] [Created ] [ ] [ 50] camel-blueprint
(2.14.0.SNAPSHOT)
[ 78] [Active ] [] [ ] [ 50] Metrics Core (3.0.2)
[ 79] [Active ] [] [ ] [ 50] camel-metrics
(2.14.0.SNAPSHOT)
karaf@root ls 60
You are about to access system bundle 60. Do you wish to continue (yes/no):
yes
camel-core (60) provides:
-
component = direct, vm, mock, bean, test, stub, validator, class, properties,
direct-vm, log, ref, xslt, browse, dataset, timer, file, controlbus, binding,
seda, rest, language, dataformat
objectClass = org.apache.camel.spi.ComponentResolver
service.id = 225
language = ref, constant, bean, simple, file, xtokenize, property, header,
xpath, tokenize
objectClass = org.apache.camel.spi.LanguageResolver
service.id = 226
dataformat = zip, string, serialization
objectClass = org.apache.camel.spi.DataFormatResolver
service.id = 227
objectClass = org.apache.camel.spi.TypeConverterLoader
service.id = 228
karaf@root
{code}
For example as shown above with Apache Camel where we have many components /
languages etc exported.
Would be nice to have the values sorted before they are printed to the
console.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (KARAF-2966) scr:details - Sort the properties so its easier for humans to read
Claus Ibsen created KARAF-2966:
--
Summary: scr:details - Sort the properties so its easier for
humans to read
Key: KARAF-2966
URL: https://issues.apache.org/jira/browse/KARAF-2966
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.5
Reporter: Claus Ibsen
Priority: Minor
The scr commands is great. But it would help if scr:details would sort the
Properties A..Z so the various options is listed nicely.
For example today
{code}
Fabric8:karaf@root scr:details io.fabric8.git.proxy
Component Details
Name: io.fabric8.git.proxy
State : ACTIVE
Properties :
service.pid=io.fabric8.git.proxy
proxyHost=myproxy
component.name=io.fabric8.git.proxy
component.id=115
proxyPort=9001
fabric.zookeeper.pid=io.fabric8.git.proxy
References
Reference : configurer
State : satisfied
Multiple : single
Optional : mandatory
Policy: static
Service Reference : Bound Service ID 393
(io.fabric8.service.ComponentConfigurer)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (KARAF-2963) osgi:headers - Add option to not display uses:= in exported headers as its too verbose and useless information
Claus Ibsen created KARAF-2963:
--
Summary: osgi:headers - Add option to not display uses:= in
exported headers as its too verbose and useless information
Key: KARAF-2963
URL: https://issues.apache.org/jira/browse/KARAF-2963
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 2.3.5
Reporter: Claus Ibsen
The osgi:headers command is good for look at which osgi imports|exports etc a
bundle has.
But the list is very verbose, when uses:= details is listed (which you most
often dont care about).
It would be nice if you could type
osgi:headers 70
And it displays without uses:=
And if you want it verbose, then type
osgi:headers 70 --verbose
For example showing the aws-sdk headers is
{code}
karaf@root headers 70
You are about to access system bundle 70. Do you wish to continue (yes/no):
yes
Apache ServiceMix :: Bundles :: aws-java-sdk (70)
-
Manifest-Version = 1.0
Original-Wires =
com.fasterxml.jackson.databind,org.apache.http.message,org.apache.commons.logging,org.apache.http.protocol,org.apache.http.conn.scheme,org.apache.http.params,javax.mail.internet,org.apache.http.entity,org.apache.http.conn.ssl,org.apache.http.client.utils,org.apache.http.impl.conn,org.apache.http.client,org.apache.commons.codec.binary,com.fasterxml.jackson.core,org.apache.http.impl.client,org.apache.http.conn,org.joda.time.format,com.fasterxml.jackson.annotation,org.apache.http.impl.auth,javax.mail,org.apache.http.client.methods,org.apache.http,org.apache.http.auth
Bnd-LastModified = 1399013186171
Tool = Bnd-0.0.357
Originally-Created-By = Apache Maven Bundle Plugin
Built-By = jbonofre
Generated-By-Ops4j-Pax-From =
wrap:mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1$Bundle-UpdateLocation=mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1DynamicImport-Package=*Original-Wires=com.fasterxml.jackson.databind,org.apache.http.message,org.apache.commons.logging,org.apache.http.protocol,org.apache.http.conn.scheme,org.apache.http.params,javax.mail.internet,org.apache.http.entity,org.apache.http.conn.ssl,org.apache.http.client.utils,org.apache.http.impl.conn,org.apache.http.client,org.apache.commons.codec.binary,com.fasterxml.jackson.core,org.apache.http.impl.client,org.apache.http.conn,org.joda.time.format,com.fasterxml.jackson.annotation,org.apache.http.impl.auth,javax.mail,org.apache.http.client.methods,org.apache.http,org.apache.http.authoverwrite=merge
Build-Jdk = 1.7.0_51
Created-By = 1.7.0_45 (Oracle Corporation)
Bundle-Vendor = The Apache Software Foundation
Bundle-UpdateLocation =
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1
Bundle-Name = Apache ServiceMix :: Bundles :: aws-java-sdk
Bundle-DocURL = http://www.apache.org/
Bundle-Description = This OSGi bundle wraps aws-java-sdk 1.7.1 jar file.
Bundle-SymbolicName = org.apache.servicemix.bundles.aws-java-sdk
Bundle-Version = 1.7.1.1
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion = 2
DynamicImport-Package =
*
Private-Package =
.
Import-Package =
com.fasterxml.jackson.annotation;resolution:=optional;version=[2.1,3),
com.fasterxml.jackson.core;resolution:=optional;version=[2.1,3),
com.fasterxml.jackson.databind;resolution:=optional;version=[2.1,3),
javax.crypto,
javax.crypto.spec,
javax.mail;resolution:=optional;version=[1.4,2),
javax.mail.internet;resolution:=optional;version=[1.4,2),
javax.management,
javax.net.ssl,
javax.xml.namespace,
javax.xml.parsers,
javax.xml.stream,
javax.xml.stream.events,
javax.xml.xpath,
org.apache.commons.codec.binary;version=[1.3,2),
org.apache.commons.logging;resolution:=optional;version=[1.1,2),
org.apache.http;version=[4,5),
org.apache.http.auth;version=[4,5),
org.apache.http.client;version=[4,5),
org.apache.http.client.methods;version=[4,5),
org.apache.http.client.utils;version=[4,5),
org.apache.http.conn;version=[4,5),
org.apache.http.conn.scheme;version=[4,5),
org.apache.http.conn.ssl;version=[4,5),
org.apache.http.entity;version=[4,5),
org.apache.http.impl.auth;version=[4,5),
org.apache.http.impl.client;version=[4,5),
org.apache.http.impl.conn;version=[4,5),
org.apache.http.message;version=[4,5),
org.apache.http.params;version=[4,5),
org.apache.http.protocol;version=[4,5),
org.aspectj.lang;resolution:=optional;version=[1,2),
org.aspectj.lang.annotation;resolution:=optional;version=[1,2),
org.aspectj.lang.reflect;resolution:=optional;version=[1,2),
[jira] [Commented] (KARAF-2963) osgi:headers - Add option to not display uses:= in exported headers as its too verbose and useless information
[
https://issues.apache.org/jira/browse/KARAF-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987451#comment-13987451
]
Claus Ibsen commented on KARAF-2963:
Yes there is also packages:import and packages:export but they dont show the
version range, or when some packages are not imported (shown in red) etc.
I guess if headers had a --no-uses to filter out those lines, then that would
be a good solution too.
And btw which is there a difference how packages:import and packages:export
display their data?
And it would be nice if these commands had an option to only show the package
name, in case you need to copy that information.
osgi:headers - Add option to not display uses:= in exported headers as its
too verbose and useless information
--
Key: KARAF-2963
URL: https://issues.apache.org/jira/browse/KARAF-2963
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 2.3.5
Reporter: Claus Ibsen
The osgi:headers command is good for look at which osgi imports|exports etc a
bundle has.
But the list is very verbose, when uses:= details is listed (which you most
often dont care about).
It would be nice if you could type
osgi:headers 70
And it displays without uses:=
And if you want it verbose, then type
osgi:headers 70 --verbose
For example showing the aws-sdk headers is
{code}
karaf@root headers 70
You are about to access system bundle 70. Do you wish to continue (yes/no):
yes
Apache ServiceMix :: Bundles :: aws-java-sdk (70)
-
Manifest-Version = 1.0
Original-Wires =
com.fasterxml.jackson.databind,org.apache.http.message,org.apache.commons.logging,org.apache.http.protocol,org.apache.http.conn.scheme,org.apache.http.params,javax.mail.internet,org.apache.http.entity,org.apache.http.conn.ssl,org.apache.http.client.utils,org.apache.http.impl.conn,org.apache.http.client,org.apache.commons.codec.binary,com.fasterxml.jackson.core,org.apache.http.impl.client,org.apache.http.conn,org.joda.time.format,com.fasterxml.jackson.annotation,org.apache.http.impl.auth,javax.mail,org.apache.http.client.methods,org.apache.http,org.apache.http.auth
Bnd-LastModified = 1399013186171
Tool = Bnd-0.0.357
Originally-Created-By = Apache Maven Bundle Plugin
Built-By = jbonofre
Generated-By-Ops4j-Pax-From =
wrap:mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1$Bundle-UpdateLocation=mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1DynamicImport-Package=*Original-Wires=com.fasterxml.jackson.databind,org.apache.http.message,org.apache.commons.logging,org.apache.http.protocol,org.apache.http.conn.scheme,org.apache.http.params,javax.mail.internet,org.apache.http.entity,org.apache.http.conn.ssl,org.apache.http.client.utils,org.apache.http.impl.conn,org.apache.http.client,org.apache.commons.codec.binary,com.fasterxml.jackson.core,org.apache.http.impl.client,org.apache.http.conn,org.joda.time.format,com.fasterxml.jackson.annotation,org.apache.http.impl.auth,javax.mail,org.apache.http.client.methods,org.apache.http,org.apache.http.authoverwrite=merge
Build-Jdk = 1.7.0_51
Created-By = 1.7.0_45 (Oracle Corporation)
Bundle-Vendor = The Apache Software Foundation
Bundle-UpdateLocation =
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1
Bundle-Name = Apache ServiceMix :: Bundles :: aws-java-sdk
Bundle-DocURL = http://www.apache.org/
Bundle-Description = This OSGi bundle wraps aws-java-sdk 1.7.1 jar file.
Bundle-SymbolicName = org.apache.servicemix.bundles.aws-java-sdk
Bundle-Version = 1.7.1.1
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion = 2
DynamicImport-Package =
*
Private-Package =
.
Import-Package =
com.fasterxml.jackson.annotation;resolution:=optional;version=[2.1,3),
com.fasterxml.jackson.core;resolution:=optional;version=[2.1,3),
com.fasterxml.jackson.databind;resolution:=optional;version=[2.1,3),
javax.crypto,
javax.crypto.spec,
javax.mail;resolution:=optional;version=[1.4,2),
javax.mail.internet;resolution:=optional;version=[1.4,2),
javax.management,
javax.net.ssl,
javax.xml.namespace,
javax.xml.parsers,
javax.xml.stream,
javax.xml.stream.events,
javax.xml.xpath,
org.apache.commons.codec.binary;version=[1.3,2),
org.apache.commons.logging;resolution:=optional;version=[1.1,2),
org.apache.http;version=[4,5),
org.apache.http.auth;version=[4,5),
org.apache.http.client;version=[4,5),
org.apache.http.client.methods;version=[4,5),
[jira] [Updated] (KARAF-2963) osgi:headers - Add option to not display uses:= in exported headers as its too verbose and useless information
[
https://issues.apache.org/jira/browse/KARAF-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated KARAF-2963:
---
Priority: Minor (was: Major)
osgi:headers - Add option to not display uses:= in exported headers as its
too verbose and useless information
--
Key: KARAF-2963
URL: https://issues.apache.org/jira/browse/KARAF-2963
Project: Karaf
Issue Type: Wish
Components: karaf-shell
Affects Versions: 2.3.5
Reporter: Claus Ibsen
Priority: Minor
The osgi:headers command is good for look at which osgi imports|exports etc a
bundle has.
But the list is very verbose, when uses:= details is listed (which you most
often dont care about).
It would be nice if you could type
osgi:headers 70
And it displays without uses:=
And if you want it verbose, then type
osgi:headers 70 --verbose
For example showing the aws-sdk headers is
{code}
karaf@root headers 70
You are about to access system bundle 70. Do you wish to continue (yes/no):
yes
Apache ServiceMix :: Bundles :: aws-java-sdk (70)
-
Manifest-Version = 1.0
Original-Wires =
com.fasterxml.jackson.databind,org.apache.http.message,org.apache.commons.logging,org.apache.http.protocol,org.apache.http.conn.scheme,org.apache.http.params,javax.mail.internet,org.apache.http.entity,org.apache.http.conn.ssl,org.apache.http.client.utils,org.apache.http.impl.conn,org.apache.http.client,org.apache.commons.codec.binary,com.fasterxml.jackson.core,org.apache.http.impl.client,org.apache.http.conn,org.joda.time.format,com.fasterxml.jackson.annotation,org.apache.http.impl.auth,javax.mail,org.apache.http.client.methods,org.apache.http,org.apache.http.auth
Bnd-LastModified = 1399013186171
Tool = Bnd-0.0.357
Originally-Created-By = Apache Maven Bundle Plugin
Built-By = jbonofre
Generated-By-Ops4j-Pax-From =
wrap:mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1$Bundle-UpdateLocation=mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1DynamicImport-Package=*Original-Wires=com.fasterxml.jackson.databind,org.apache.http.message,org.apache.commons.logging,org.apache.http.protocol,org.apache.http.conn.scheme,org.apache.http.params,javax.mail.internet,org.apache.http.entity,org.apache.http.conn.ssl,org.apache.http.client.utils,org.apache.http.impl.conn,org.apache.http.client,org.apache.commons.codec.binary,com.fasterxml.jackson.core,org.apache.http.impl.client,org.apache.http.conn,org.joda.time.format,com.fasterxml.jackson.annotation,org.apache.http.impl.auth,javax.mail,org.apache.http.client.methods,org.apache.http,org.apache.http.authoverwrite=merge
Build-Jdk = 1.7.0_51
Created-By = 1.7.0_45 (Oracle Corporation)
Bundle-Vendor = The Apache Software Foundation
Bundle-UpdateLocation =
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aws-java-sdk/1.7.1_1
Bundle-Name = Apache ServiceMix :: Bundles :: aws-java-sdk
Bundle-DocURL = http://www.apache.org/
Bundle-Description = This OSGi bundle wraps aws-java-sdk 1.7.1 jar file.
Bundle-SymbolicName = org.apache.servicemix.bundles.aws-java-sdk
Bundle-Version = 1.7.1.1
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion = 2
DynamicImport-Package =
*
Private-Package =
.
Import-Package =
com.fasterxml.jackson.annotation;resolution:=optional;version=[2.1,3),
com.fasterxml.jackson.core;resolution:=optional;version=[2.1,3),
com.fasterxml.jackson.databind;resolution:=optional;version=[2.1,3),
javax.crypto,
javax.crypto.spec,
javax.mail;resolution:=optional;version=[1.4,2),
javax.mail.internet;resolution:=optional;version=[1.4,2),
javax.management,
javax.net.ssl,
javax.xml.namespace,
javax.xml.parsers,
javax.xml.stream,
javax.xml.stream.events,
javax.xml.xpath,
org.apache.commons.codec.binary;version=[1.3,2),
org.apache.commons.logging;resolution:=optional;version=[1.1,2),
org.apache.http;version=[4,5),
org.apache.http.auth;version=[4,5),
org.apache.http.client;version=[4,5),
org.apache.http.client.methods;version=[4,5),
org.apache.http.client.utils;version=[4,5),
org.apache.http.conn;version=[4,5),
org.apache.http.conn.scheme;version=[4,5),
org.apache.http.conn.ssl;version=[4,5),
org.apache.http.entity;version=[4,5),
org.apache.http.impl.auth;version=[4,5),
org.apache.http.impl.client;version=[4,5),
org.apache.http.impl.conn;version=[4,5),
org.apache.http.message;version=[4,5),
org.apache.http.params;version=[4,5),
[jira] [Created] (KARAF-2840) Creating child container using admin service should use KARAF_OPTS
Claus Ibsen created KARAF-2840:
--
Summary: Creating child container using admin service should use
KARAF_OPTS
Key: KARAF-2840
URL: https://issues.apache.org/jira/browse/KARAF-2840
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 2.3.4
Reporter: Claus Ibsen
Fix For: 2.3.5
When you use admin:create to create a child container, then the AdminService is
used to create the JVM process. This code does not read the KARAF_OPTS
environment variable which means the child container does not use that when
started.
But if you use the bin/start script to start the child container, then the
setenv script will read the KARAF_OPTS.
So that means there is a difference between using the admin commands to
crate|start child containers, vs using the bin scripts.
This is a serious problem for Windows users on IP6 network that hits a well
known issue, where they have to set a JVM system property to work around this.
If they do not you get network issues such as
java.net.SocketException: Permission denied: no further information
To fix this with Karaf you set this option
KARAF_OPTS '-Djava.net.preferIPv4Stack=true'
Maybe either globally in the Windows box, or in the bin/setenv.bat file.
But the child containers do not pickup that env option when created by admin
server.
This patch fixes that.
To see if the env option was picked up by Karaf, you can connect to the child
container, and run
{code}
dev:system-property | grep java.net
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (KARAF-2840) Creating child container using admin service should use KARAF_OPTS
[
https://issues.apache.org/jira/browse/KARAF-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated KARAF-2840:
---
Attachment: karaf2840.patch
Attached patch for 2.3.x branch
Creating child container using admin service should use KARAF_OPTS
--
Key: KARAF-2840
URL: https://issues.apache.org/jira/browse/KARAF-2840
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 2.3.4
Reporter: Claus Ibsen
Fix For: 2.3.5
Attachments: karaf2840.patch
When you use admin:create to create a child container, then the AdminService
is used to create the JVM process. This code does not read the KARAF_OPTS
environment variable which means the child container does not use that when
started.
But if you use the bin/start script to start the child container, then the
setenv script will read the KARAF_OPTS.
So that means there is a difference between using the admin commands to
crate|start child containers, vs using the bin scripts.
This is a serious problem for Windows users on IP6 network that hits a well
known issue, where they have to set a JVM system property to work around this.
If they do not you get network issues such as
java.net.SocketException: Permission denied: no further information
To fix this with Karaf you set this option
KARAF_OPTS '-Djava.net.preferIPv4Stack=true'
Maybe either globally in the Windows box, or in the bin/setenv.bat file.
But the child containers do not pickup that env option when created by admin
server.
This patch fixes that.
To see if the env option was picked up by Karaf, you can connect to the child
container, and run
{code}
dev:system-property | grep java.net
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (KARAF-2691) Karaf shell info command to display the pid
Claus Ibsen created KARAF-2691: -- Summary: Karaf shell info command to display the pid Key: KARAF-2691 URL: https://issues.apache.org/jira/browse/KARAF-2691 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-shell Affects Versions: 2.3.3 Reporter: Claus Ibsen Priority: Minor The karaf info is a useful command. Though it would be nice if it could display the pid (process id). Not sure how easy that is to grab. And maybe also a pid command to just return the pid, which can be used in scripts etc. [11:47:40] davsclaus would it be possible to show the pid in the karaf info command [11:49:17] cschneide Sure [11:49:52] cschneide davsclaus: If you open an issue I can implement it [11:50:36] cschneide davsclaus: If you want to use the pid in a script it might also make sense to return only the pid [11:51:29] davsclaus yeah a pid command -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (KARAF-2691) Karaf shell info command to display the pid
[ https://issues.apache.org/jira/browse/KARAF-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13874807#comment-13874807 ] Claus Ibsen commented on KARAF-2691: I am fine with the command as a sub shell in karaf 3.0 onwards. I would though like the pid to be listed in osgi info in karaf 2.x. This makes it easier to help people as just tell them to info and they can easily find the pid on the screen. Karaf shell info command to display the pid --- Key: KARAF-2691 URL: https://issues.apache.org/jira/browse/KARAF-2691 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-shell Affects Versions: 2.3.3 Reporter: Claus Ibsen Assignee: Christian Schneider Priority: Minor Fix For: 2.4.0, 3.0.1, 2.3.4 The karaf info is a useful command. Though it would be nice if it could display the pid (process id). Not sure how easy that is to grab. And maybe also a pid command to just return the pid, which can be used in scripts etc. [11:47:40] davsclauswould it be possible to show the pid in the karaf info command [11:49:17] cschneideSure [11:49:52] cschneidedavsclaus: If you open an issue I can implement it [11:50:36] cschneidedavsclaus: If you want to use the pid in a script it might also make sense to return only the pid [11:51:29] davsclausyeah a pid command -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (KARAF-2687) Better thread name for lock and shutdown background threads
Claus Ibsen created KARAF-2687: -- Summary: Better thread name for lock and shutdown background threads Key: KARAF-2687 URL: https://issues.apache.org/jira/browse/KARAF-2687 Project: Karaf Issue Type: Improvement Components: karaf-core Affects Versions: 2.3.3 Reporter: Claus Ibsen Priority: Minor Attachments: thread-1.png, thread-2.png Notice that in my karaf container the JVM has threads just named Thread-1, Thread-2, etc. So looking into naming these better, so its easier for people to monitor and manage their Karaf based JVMs. I am attaching screenshots of jconsole with the thread name examples. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (KARAF-2687) Better thread name for lock and shutdown background threads
[ https://issues.apache.org/jira/browse/KARAF-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated KARAF-2687: --- Attachment: thread-2.png thread-1.png Better thread name for lock and shutdown background threads --- Key: KARAF-2687 URL: https://issues.apache.org/jira/browse/KARAF-2687 Project: Karaf Issue Type: Improvement Components: karaf-core Affects Versions: 2.3.3 Reporter: Claus Ibsen Priority: Minor Attachments: thread-1.png, thread-2.png Notice that in my karaf container the JVM has threads just named Thread-1, Thread-2, etc. So looking into naming these better, so its easier for people to monitor and manage their Karaf based JVMs. I am attaching screenshots of jconsole with the thread name examples. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (KARAF-2687) Better thread name for lock and shutdown background threads
[ https://issues.apache.org/jira/browse/KARAF-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated KARAF-2687: --- Attachment: karaf-shell-tail-thread.png Better thread name for lock and shutdown background threads --- Key: KARAF-2687 URL: https://issues.apache.org/jira/browse/KARAF-2687 Project: Karaf Issue Type: Improvement Components: karaf-core Affects Versions: 2.3.3 Reporter: Claus Ibsen Priority: Minor Attachments: karaf-shell-tail-thread.png, thread-1.png, thread-2.png Notice that in my karaf container the JVM has threads just named Thread-1, Thread-2, etc. So looking into naming these better, so its easier for people to monitor and manage their Karaf based JVMs. I am attaching screenshots of jconsole with the thread name examples. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (KARAF-2687) Better thread name for lock and shutdown background threads
[ https://issues.apache.org/jira/browse/KARAF-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated KARAF-2687: --- Attachment: tail.png Better thread name for lock and shutdown background threads --- Key: KARAF-2687 URL: https://issues.apache.org/jira/browse/KARAF-2687 Project: Karaf Issue Type: Improvement Components: karaf-core Affects Versions: 2.3.3 Reporter: Claus Ibsen Priority: Minor Attachments: tail.png, thread-1.png, thread-2.png Notice that in my karaf container the JVM has threads just named Thread-1, Thread-2, etc. So looking into naming these better, so its easier for people to monitor and manage their Karaf based JVMs. I am attaching screenshots of jconsole with the thread name examples. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (KARAF-2687) Better thread name for lock and shutdown background threads
[ https://issues.apache.org/jira/browse/KARAF-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated KARAF-2687: --- Attachment: (was: karaf-shell-tail-thread.png) Better thread name for lock and shutdown background threads --- Key: KARAF-2687 URL: https://issues.apache.org/jira/browse/KARAF-2687 Project: Karaf Issue Type: Improvement Components: karaf-core Affects Versions: 2.3.3 Reporter: Claus Ibsen Priority: Minor Attachments: tail.png, thread-1.png, thread-2.png Notice that in my karaf container the JVM has threads just named Thread-1, Thread-2, etc. So looking into naming these better, so its easier for people to monitor and manage their Karaf based JVMs. I am attaching screenshots of jconsole with the thread name examples. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (KARAF-2688) Karaf info - Add memory details about perm gen pool
Claus Ibsen created KARAF-2688:
--
Summary: Karaf info - Add memory details about perm gen pool
Key: KARAF-2688
URL: https://issues.apache.org/jira/browse/KARAF-2688
Project: Karaf
Issue Type: Improvement
Components: karaf-core, karaf-shell
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Priority: Minor
When running the info command you get some JVM details
For memory you get
{code}
Memory
Current heap size 90,407 kbytes
Maximum heap size 521,216 kbytes
Committed heap size 106,496 kbytes
{code}
It would be good to have the perm-gen pool as well. As if you are running out
of perm gen you are fucked. The GC cannot reclaim perm gen memory.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (KARAF-2688) Karaf info - Add memory details about perm gen pool
[
https://issues.apache.org/jira/browse/KARAF-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated KARAF-2688:
---
Attachment: Screen Shot 2014-01-16 at 3.05.16 PM.png
screenshot of jconsole with perm gen pool.
Karaf info - Add memory details about perm gen pool
---
Key: KARAF-2688
URL: https://issues.apache.org/jira/browse/KARAF-2688
Project: Karaf
Issue Type: Improvement
Components: karaf-core, karaf-shell
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.4.0, 3.0.1, 2.3.4
Attachments: Screen Shot 2014-01-16 at 3.05.16 PM.png
When running the info command you get some JVM details
For memory you get
{code}
Memory
Current heap size 90,407 kbytes
Maximum heap size 521,216 kbytes
Committed heap size 106,496 kbytes
{code}
It would be good to have the perm-gen pool as well. As if you are running out
of perm gen you are fucked. The GC cannot reclaim perm gen memory.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (KARAF-2516) log:tail | grep foo - throws interrupted exception when using ctrl + c
Claus Ibsen created KARAF-2516:
--
Summary: log:tail | grep foo - throws interrupted exception when
using ctrl + c
Key: KARAF-2516
URL: https://issues.apache.org/jira/browse/KARAF-2516
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Priority: Minor
I am doing
{code}
karaf@root log:tail | grep Listening
2013-10-11 16:43:48,158 | INFO | fd-2b635899ab2a) |
TransportServerThreadSupport | ort.TransportServerThreadSupport 72 | 89 -
org.apache.activemq.activemq-osgi - 5.10.0.SNAPSHOT | Listening for connections
at:
tcp://davsclaus.air:61616?maximumConnections=1000wireFormat.maxFrameSize=104857600
^C
Error executing command: java.lang.InterruptedException
{code}
And using ctrl + c to break out of the tail
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (KARAF-2512) features:info should display feature description
Claus Ibsen created KARAF-2512:
--
Summary: features:info should display feature description
Key: KARAF-2512
URL: https://issues.apache.org/jira/browse/KARAF-2512
Project: Karaf
Issue Type: Improvement
Components: karaf-feature, karaf-shell
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Priority: Minor
We have descriptions to our features in ActiveMQ 5.9. And I wanted to see these
when I do a feature:info activemq etc. As I can't remember which one install
the web console out of the box etc, as we have activemq | activemq-broker |
activemq-xxx
{code}
karaf@root features:info activemq
Description of activemq 5.9-SNAPSHOT feature
Feature has no configuration
Feature has no configuration files
Feature depends on:
jetty 0.0.0
activemq-client 5.9-SNAPSHOT
Feature contains followed bundles:
mvn:org.apache.activemq/activemq-karaf/5.9-SNAPSHOT start-level=50
mvn:org.apache.xbean/xbean-spring/3.14 start-level=50
mvn:commons-collections/commons-collections/3.2.1 start-level=50
mvn:commons-lang/commons-lang/2.6 start-level=50
mvn:commons-codec/commons-codec/1.4 start-level=50
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.velocity/1.7_5
start-level=50
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jasypt/1.9.0_1
start-level=50
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.stax-api-1.0/1.9.0
start-level=50
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xpp3/1.1.4c_5
start-level=50
mvn:joda-time/joda-time/1.6.2 start-level=50
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xstream/1.3_3
start-level=50
mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.0.0
start-level=50
mvn:org.apache.geronimo.specs/geronimo-j2ee-connector_1.5_spec/2.0.0
start-level=50
mvn:org.apache.aries/org.apache.aries.util/1.0.0 start-level=50
mvn:org.apache.activemq/activeio-core/3.1.4 start-level=50
mvn:org.codehaus.jettison/jettison/1.3.4 start-level=50
mvn:org.codehaus.jackson/jackson-core-asl/1.9.12 start-level=50
mvn:org.codehaus.jackson/jackson-mapper-asl/1.9.12 start-level=50
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.scala-library/2.9.1_3
start-level=50
{code}
And when I do a features:list you can see the descriptions
{code}
karaf@root features:list | grep activemq
[uninstalled] [5.9-SNAPSHOT ] activemq-client
activemq-5.9-SNAPSHOT ActiveMQ client libraries
[uninstalled] [5.9-SNAPSHOT ] activemq
activemq-5.9-SNAPSHOT ActiveMQ broker libraries
[uninstalled] [5.9-SNAPSHOT ] activemq-broker-noweb
activemq-5.9-SNAPSHOT Full ActiveMQ broker with default configuration
[uninstalled] [5.9-SNAPSHOT ] activemq-broker
activemq-5.9-SNAPSHOT Full ActiveMQ broker with default configuration and web
console
[uninstalled] [5.9-SNAPSHOT ] activemq-camel
activemq-5.9-SNAPSHOT
[uninstalled] [5.9-SNAPSHOT ] activemq-web-console
activemq-5.9-SNAPSHOT
[uninstalled] [5.9-SNAPSHOT ] activemq-blueprint
activemq-5.9-SNAPSHOT
{code}
eg its the text ctiveMQ broker libraries I want to see in features:info also.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (KARAF-2497) NPE in PropertiesLoginModule
[
https://issues.apache.org/jira/browse/KARAF-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789187#comment-13789187
]
Claus Ibsen commented on KARAF-2497:
Thanks for checking and fixing. A good idea with a more descriptive exception
message. Thanks
NPE in PropertiesLoginModule
Key: KARAF-2497
URL: https://issues.apache.org/jira/browse/KARAF-2497
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Assignee: Jean-Baptiste Onofré
Priority: Minor
Fix For: 2.4.0, 3.0.0, 2.3.4
Notice this stacktrace during an karaf itest in ActiveMQ
{code}
Caused by: javax.security.auth.login.LoginException:
java.lang.NullPointerException
at java.lang.String.init(String.java:168)
at
org.apache.karaf.jaas.modules.properties.PropertiesLoginModule.login(PropertiesLoginModule.java:85)
at
org.apache.karaf.jaas.boot.ProxyLoginModule.login(ProxyLoginModule.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784)
at
javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695)
at javax.security.auth.login.LoginContext.login(LoginContext.java:594)
at
org.apache.activemq.security.JaasAuthenticationBroker.addConnection(JaasAuthenticationBroker.java:73)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97)
{code}
I guess the PropertiesLoginModule could deal with this an possible throw a
more meaningful exception instead of NPE if something is not correct.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (KARAF-2503) Allow to limit the number of entries the history command remembers
Claus Ibsen created KARAF-2503: -- Summary: Allow to limit the number of entries the history command remembers Key: KARAF-2503 URL: https://issues.apache.org/jira/browse/KARAF-2503 Project: Karaf Issue Type: Improvement Components: karaf-shell Affects Versions: 2.3.3 Reporter: Claus Ibsen The Karaf shell command remembers X number of entires back (jline history). It would be great if you could configure this in a configuration file in the etc, to have a upper limit how many entries is remembered. This applies when you use cursor up/down to scroll the history. As well when you type history in the shell to output the history stack. And it should be possible to disable the history, for example if you set the limit to 0 or -1 etc. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2503) Allow to limit the number of entries the history command remembers
[ https://issues.apache.org/jira/browse/KARAF-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788052#comment-13788052 ] Claus Ibsen commented on KARAF-2503: From the karaf chat room today [10:15:54] davsclaus is there a way in karaf to setup the number of entries the shell history remembers ? [10:17:40] jgoodyear good question [10:18:18] davsclaus the history command in the shell has only the --help option [10:18:46] jgoodyear looking a the code, need a moment ;) [10:18:49] davsclaus one reason asking is to be able to configure this, either in a etc file or from the shell, but in the etc would be lovely [10:18:57] jgoodyear also need my coffee to kick in [10:19:05] davsclaus and a 2nd reason is due security as some ppl dont want to expose the history [10:19:18] davsclaus good idea, brewing time [10:28:01] ch007m2 (~cmoul...@ip-83-134-172-113.dsl.scarlet.be) left IRC. (Leaving) [10:33:43] anierbeck jgoodyear: :) longer days could be helpfull but only combined with less amount of sleep required ;) [10:34:25] anierbeck davsclaus: hmm, I'm not sure but I think it's not configurable yet ... [10:34:44] anierbeck davsclaus: +1 for a new requirement :) [10:36:10] davsclaus yeah if its missing then would like to see that implement in karaf [10:36:53] jgoodyear davsclaus: its just the JLine history lib [10:37:05] davsclaus k [10:37:14] jgoodyear davsclaus: didn't notice anything in there for setting file size or the like [10:37:38] davsclaus oh maybe we can do limits in the shell command [10:37:42] davsclaus eg when you type [10:37:45] davsclaus historyt [10:37:50] anierbeck jgoodyear: hmm, btw is this history shared by all users? [10:37:52] davsclaus it can limit based on configured option [10:38:06] jgoodyear anierbeck: appears so [10:38:21] jgoodyear anierbeck: the history interface isn't very sophisticated [10:38:33] davsclaus yeah it should ideally be per user and not shared, and a way to limit the length , and also be able to set it to 0 to turn it off [10:38:41] davsclaus and maybe a history --clear to clear it [10:38:50] jgoodyear clear per user [10:39:04] jgoodyear userA should not be able to clear userB [10:39:08] davsclaus yeah [10:39:10] jgoodyear unless userA is Admin [10:39:16] davsclaus but you may have a shared user account for ppl to use [10:41:11] anierbeck davsclaus: which is OK, but the users shouldn't share the history ... [10:41:23] anierbeck jgoodyear: ok, so this could need some bigger improvements then ... [10:41:35] jgoodyear anierbeck: yes [10:42:05] cschneid1 (~thund...@b2b-92-50-84-158.unitymedia.biz) joined the channel. [10:42:05] jgoodyear anierbeck: that's not going to be so simple given the current impl [10:42:44] anierbeck jgoodyear: I wouldn't have guessed it to be simple, since it's not implemented already :D [10:43:50] davsclaus well 1st goal would be to limit the history size in some way [10:43:56] jgoodyear yup [10:43:58] davsclaus then 2nd goal could be clear / sharing history etc [10:44:00] anierbeck davsclaus: yep [10:44:14] jgoodyear third goal is obtain more coffee - brb [10:44:28] davsclaus that would be a recurring goal :) Allow to limit the number of entries the history command remembers -- Key: KARAF-2503 URL: https://issues.apache.org/jira/browse/KARAF-2503 Project: Karaf Issue Type: Improvement Components: karaf-shell Affects Versions: 2.3.3 Reporter: Claus Ibsen The Karaf shell command remembers X number of entires back (jline history). It would be great if you could configure this in a configuration file in the etc, to have a upper limit how many entries is remembered. This applies when you use cursor up/down to scroll the history. As well when you type history in the shell to output the history stack. And it should be possible to disable the history, for example if you set the limit to 0 or -1 etc. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (KARAF-2497) NPE in PropertiesLoginModule
Claus Ibsen created KARAF-2497:
--
Summary: NPE in PropertiesLoginModule
Key: KARAF-2497
URL: https://issues.apache.org/jira/browse/KARAF-2497
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Priority: Minor
Notice this stacktrace during an karaf itest in ActiveMQ
{code}
Caused by: javax.security.auth.login.LoginException:
java.lang.NullPointerException
at java.lang.String.init(String.java:168)
at
org.apache.karaf.jaas.modules.properties.PropertiesLoginModule.login(PropertiesLoginModule.java:85)
at
org.apache.karaf.jaas.boot.ProxyLoginModule.login(ProxyLoginModule.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784)
at
javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695)
at javax.security.auth.login.LoginContext.login(LoginContext.java:594)
at
org.apache.activemq.security.JaasAuthenticationBroker.addConnection(JaasAuthenticationBroker.java:73)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97)
{code}
I guess the PropertiesLoginModule could deal with this an possible throw a more
meaningful exception instead of NPE if something is not correct.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (KARAF-2413) Add features:chooseurl for camel-extra
Claus Ibsen created KARAF-2413:
--
Summary: Add features:chooseurl for camel-extra
Key: KARAF-2413
URL: https://issues.apache.org/jira/browse/KARAF-2413
Project: Karaf
Issue Type: Task
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.3.3, 2.4.0, 3.0.0
The Camel Extra project has karaf support to install features
For example I can add this url today:
{code}
features:addurl
mvn:org.apache-extras.karaf/camel-extra/2.12-SNAPSHOT/xml/features
{code}
It would be great if there was a chooseurl shorthand like below added to Karaf
out of the box:
{code}
features:chooseurl camel-extras
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1901) Camel stream:out route destination freezes console if you try to stop or uninstall it
[ https://issues.apache.org/jira/browse/KARAF-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718069#comment-13718069 ] Claus Ibsen commented on KARAF-1901: I think this has been fixed in latests Camel releases. Can you guys try again with a newer Camel version? Camel stream:out route destination freezes console if you try to stop or uninstall it - Key: KARAF-1901 URL: https://issues.apache.org/jira/browse/KARAF-1901 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 2.2.9 Environment: 1.6 on osx Reporter: Tracy Snell Priority: Minor Attachments: thread-dump-1901txt Create the camel maven blueprint archetype. Change the route in the example to stream:out, build, deploy. Works fine with annoying messages every 5 seconds to the console. Stop the route or the bundle and the command will succeed but you never get a karaf prompt again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2020) log:tail blocks on ^D
[ https://issues.apache.org/jira/browse/KARAF-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718071#comment-13718071 ] Claus Ibsen commented on KARAF-2020: Why is this not considered a more serious bug? Pressing ctrl + D / ctrl + C is common to do in a shell. log:tail blocks on ^D - Key: KARAF-2020 URL: https://issues.apache.org/jira/browse/KARAF-2020 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 2.3.0 Environment: Karaf 2.3.0 on Fedora 12 Reporter: Jordi Deu-Pons Assignee: Jean-Baptiste Onofré Priority: Trivial Fix For: 2.3.3, 3.0.0 First problem is that the log:tail command help don't tell you that you can exit with a ^C So first I pressed ^D, after this I cannot do anything I tried lots of combinations trying to guess the exit command until I killed Karaf. Then I've discovered (looking at the source code) that you can exit the tail with ^C, but if you first press ^D then ^C no longer exits the tail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2403) NPE in log:tail after doing a log:clear
Claus Ibsen created KARAF-2403:
--
Summary: NPE in log:tail after doing a log:clear
Key: KARAF-2403
URL: https://issues.apache.org/jira/browse/KARAF-2403
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.2
Reporter: Claus Ibsen
Priority: Minor
I think this has been reported before. Would have though its been fixed in
latest release. But its still there
{code}
araf@root log:clear
karaf@root log:get ALL^C
karaf@root log:tail
Error executing command: java.lang.NullPointerException
karaf@root log:display
log:display log:display-exception
karaf@root log:display
2013-07-23 14:21:38,867 | ERROR | l Console Thread | Console
| araf.shell.console.jline.Console 199 | 14 -
org.apache.karaf.shell.console - 2.3.2 | Exception caught while executing
command
java.lang.NullPointerException
at
org.apache.karaf.shell.log.layout.PatternParser$DatePatternConverter.convert(PatternParser.java:428)[38:org.apache.karaf.shell.log:2.3.2]
at
org.apache.karaf.shell.log.layout.PatternConverter.format(PatternConverter.java:61)[38:org.apache.karaf.shell.log:2.3.2]
at
org.apache.karaf.shell.log.DisplayLog.display(DisplayLog.java:153)[38:org.apache.karaf.shell.log:2.3.2]
at
org.apache.karaf.shell.log.LogTail.doExecute(LogTail.java:40)[38:org.apache.karaf.shell.log:2.3.2]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[14:org.apache.karaf.shell.console:2.3.2]
at
org.apache.karaf.shell.console.jline.Console.run(Console.java:173)[14:org.apache.karaf.shell.console:2.3.2]
at java.lang.Thread.run(Thread.java:722)[:1.7.0_13]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2300) log command to list all the logging levels currently been set
[
https://issues.apache.org/jira/browse/KARAF-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13654480#comment-13654480
]
Claus Ibsen commented on KARAF-2300:
Yeah the ALL is what I need. Though it should be mentioned in the help for the
log:get so people is aware of this. AFAIR it only mentions about ROOT.
Also the JMX MBean operation is still needed so tooling and others can get this
information as well.
log command to list all the logging levels currently been set
-
Key: KARAF-2300
URL: https://issues.apache.org/jira/browse/KARAF-2300
Project: Karaf
Issue Type: New Feature
Components: karaf-core
Affects Versions: 2.3.1
Reporter: Claus Ibsen
Priority: Minor
You can use log:set to set a logging level for a logger name.
eg
{code}
log:set DEBUG org.apache.camel
{code}
But you cannot see what has been configured, eg
log:get
Will only show for the root logger, which typically is INFO.
What we need is
{code}
log:list
{code}
To show all the custom logging levels been set.
Something alike:
{code}
log:list
LevelName
INFO ROOT
DEBUGorg.apache.camel
{code}
Also the MBean for the log should expose a JMX operation to get this data.
org.apache.karaf.management.mbeans.log.internal.LogMBeanImpl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2300) log command to list all the logging levels currently been set
Claus Ibsen created KARAF-2300:
--
Summary: log command to list all the logging levels currently been
set
Key: KARAF-2300
URL: https://issues.apache.org/jira/browse/KARAF-2300
Project: Karaf
Issue Type: New Feature
Components: karaf-core
Affects Versions: 2.3.1
Reporter: Claus Ibsen
Priority: Minor
You can use log:set to set a logging level for a logger name.
eg
{code}
log:set DEBUG org.apache.camel
{code}
But you cannot see what has been configured, eg
log:get
Will only show for the root logger, which typically is INFO.
What we need is
{code}
log:list
{code}
To show all the custom logging levels been set.
Something alike:
{code}
log:list
LevelName
INFO ROOT
DEBUGorg.apache.camel
{code}
Also the MBean for the log should expose a JMX operation to get this data.
org.apache.karaf.management.mbeans.log.internal.LogMBeanImpl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2300) log command to list all the logging levels currently been set
[
https://issues.apache.org/jira/browse/KARAF-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649034#comment-13649034
]
Claus Ibsen commented on KARAF-2300:
If you remember the logger name, you can type
{code}
log:get org.apache.camel
{code}
But what is needed is that list command to set which has been explicit set.
There is also log:clear to clear all the entires.
log command to list all the logging levels currently been set
-
Key: KARAF-2300
URL: https://issues.apache.org/jira/browse/KARAF-2300
Project: Karaf
Issue Type: New Feature
Components: karaf-core
Affects Versions: 2.3.1
Reporter: Claus Ibsen
Priority: Minor
You can use log:set to set a logging level for a logger name.
eg
{code}
log:set DEBUG org.apache.camel
{code}
But you cannot see what has been configured, eg
log:get
Will only show for the root logger, which typically is INFO.
What we need is
{code}
log:list
{code}
To show all the custom logging levels been set.
Something alike:
{code}
log:list
LevelName
INFO ROOT
DEBUGorg.apache.camel
{code}
Also the MBean for the log should expose a JMX operation to get this data.
org.apache.karaf.management.mbeans.log.internal.LogMBeanImpl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2230) Watch command - Add option to control if the console should clear or not
Claus Ibsen created KARAF-2230:
--
Summary: Watch command - Add option to control if the console
should clear or not
Key: KARAF-2230
URL: https://issues.apache.org/jira/browse/KARAF-2230
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.1
Reporter: Claus Ibsen
Priority: Minor
The watch command will clear the console on each run. It would be nice if there
was an option to not clear, so the watch can run like a log:tail command does.
{code}
karaf@root watch --help
DESCRIPTION
shell:watch
Watches refreshes the output of a command
SYNTAX
shell:watch [options] command
ARGUMENTS
command
The command to watch / refresh
OPTIONS
--help
Display this help message
-n, --interval
The interval between executions of the command in seconds
(defaults to 1)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2222) Add hawtio to features.repos
Claus Ibsen created KARAF-: -- Summary: Add hawtio to features.repos Key: KARAF- URL: https://issues.apache.org/jira/browse/KARAF- Project: Karaf Issue Type: Task Reporter: Claus Ibsen Priority: Minor Fix For: 2.3.2, 2.4.0, 3.0.0.RC1 In the etc/org.apache.karaf.features.repos.cfg there is a list of known 3rd party projects which has karaf features files in central maven repo. The hawt.io project has a karaf features file, that we would like to be added to karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2222) Add hawtio to features.repos
[ https://issues.apache.org/jira/browse/KARAF-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594502#comment-13594502 ] Claus Ibsen commented on KARAF-: I created a pull request at github https://github.com/apache/karaf/pull/16 Add hawtio to features.repos Key: KARAF- URL: https://issues.apache.org/jira/browse/KARAF- Project: Karaf Issue Type: Task Reporter: Claus Ibsen Priority: Minor Fix For: 2.3.2, 2.4.0, 3.0.0.RC1 Attachments: KARAF-.patch In the etc/org.apache.karaf.features.repos.cfg there is a list of known 3rd party projects which has karaf features files in central maven repo. The hawt.io project has a karaf features file, that we would like to be added to karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-2222) Add hawtio to features.repos
[ https://issues.apache.org/jira/browse/KARAF-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated KARAF-: --- Attachment: KARAF-.patch Patch file attached as well. Add hawtio to features.repos Key: KARAF- URL: https://issues.apache.org/jira/browse/KARAF- Project: Karaf Issue Type: Task Reporter: Claus Ibsen Priority: Minor Fix For: 2.3.2, 2.4.0, 3.0.0.RC1 Attachments: KARAF-.patch In the etc/org.apache.karaf.features.repos.cfg there is a list of known 3rd party projects which has karaf features files in central maven repo. The hawt.io project has a karaf features file, that we would like to be added to karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2222) Add hawtio to features.repos
[ https://issues.apache.org/jira/browse/KARAF-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594505#comment-13594505 ] Claus Ibsen commented on KARAF-: btw maybe the features should be sorted A..Z in that file, so when we have more and more features added its easier to see what we have in the file already. Add hawtio to features.repos Key: KARAF- URL: https://issues.apache.org/jira/browse/KARAF- Project: Karaf Issue Type: Task Reporter: Claus Ibsen Priority: Minor Fix For: 2.3.2, 2.4.0, 3.0.0.RC1 Attachments: KARAF-.patch In the etc/org.apache.karaf.features.repos.cfg there is a list of known 3rd party projects which has karaf features files in central maven repo. The hawt.io project has a karaf features file, that we would like to be added to karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2146) Add a log command to log from shell to the log
Claus Ibsen created KARAF-2146:
--
Summary: Add a log command to log from shell to the log
Key: KARAF-2146
URL: https://issues.apache.org/jira/browse/KARAF-2146
Project: Karaf
Issue Type: New Feature
Components: karaf-shell
Affects Versions: 2.3.0
Reporter: Claus Ibsen
Priority: Minor
When working with Karaf, you often have to look in the logs etc. And sometimes
you need to configure the logs to be very verbose with TRACE level logging.
It would be nice if I from the shell could do
{code}
log:log I am going to stop bundle 88 now, and you can find this text in the
log. Yeah coffee is great.
{code}
eg to log at INFO level a text. This makes it easier to grep in the log after
this text. To find a spot you wanna look at. If the log is very verbose and has
many many lines. It takes longer to find the spot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2105) Karaf features for Spring should all be same name and use version ranges
[ https://issues.apache.org/jira/browse/KARAF-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13551859#comment-13551859 ] Claus Ibsen commented on KARAF-2105: @Christian I dont think the Karaf team have said they wont support Spring 3.2. This ticket is about Spring 3.1 support on Karaf, to fix that spring31 issue. If adding Spring 3.2 was as easy as adding a new set of features with version range [3.2,3.3) then I am sure the Karaf team can do that quickly. Though isn't there a problem with Spring 3.2 not being OSGi bundles? Anyway there is another Karaf ticket about Spring 3.2 support, where its better to comment. Karaf features for Spring should all be same name and use version ranges Key: KARAF-2105 URL: https://issues.apache.org/jira/browse/KARAF-2105 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 2.3.0 Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Critical Fix For: 2.3.1 See http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-And-spring-in-the-out-of-the-box-features-files-tp4027202.html The spring features should all be named spring, and use version ranges to differentiate between the various spring version supported. Currently Spring 3.1 is named spring31, and not spring. This causes problem for end users, such as installing both spring 3.0 and 3.1, when they only want spring 3.1 etc. See more details in that nabble link. The ciritical issue is that SMX / Camel etc cannot reuse the spring features of Karaf when spring 3.1 is the new default choice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2105) Karaf features for Spring should all be same name and use version ranges
[ https://issues.apache.org/jira/browse/KARAF-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13551890#comment-13551890 ] Claus Ibsen commented on KARAF-2105: Yeah I think What Freeman said is that Karaf 3.0 there is no spring31 feature names, and that the out of the box spring feature version ranges is 3.1 (not 3.0 as in Karaf 2.x). Freeman does Karaf 3.0 have spring 2.5.6 and 3.0 version ranges for its spring features also? I assume not. Karaf features for Spring should all be same name and use version ranges Key: KARAF-2105 URL: https://issues.apache.org/jira/browse/KARAF-2105 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 2.3.0 Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Critical Fix For: 2.3.1 See http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-And-spring-in-the-out-of-the-box-features-files-tp4027202.html The spring features should all be named spring, and use version ranges to differentiate between the various spring version supported. Currently Spring 3.1 is named spring31, and not spring. This causes problem for end users, such as installing both spring 3.0 and 3.1, when they only want spring 3.1 etc. See more details in that nabble link. The ciritical issue is that SMX / Camel etc cannot reuse the spring features of Karaf when spring 3.1 is the new default choice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2105) Karaf features for Spring should all be same name and use version ranges
Claus Ibsen created KARAF-2105: -- Summary: Karaf features for Spring should all be same name and use version ranges Key: KARAF-2105 URL: https://issues.apache.org/jira/browse/KARAF-2105 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 2.3.0 Reporter: Claus Ibsen Priority: Critical Fix For: 2.3.1, 3.0.0 See http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-And-spring-in-the-out-of-the-box-features-files-tp4027202.html The spring features should all be named spring, and use version ranges to differentiate between the various spring version supported. Currently Spring 3.1 is named spring31, and not spring. This causes problem for end users, such as installing both spring 3.0 and 3.1, when they only want spring 3.1 etc. See more details in that nabble link. The ciritical issue is that SMX / Camel etc cannot reuse the spring features of Karaf when spring 3.1 is the new default choice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-2049) Instructions in welcome screen is a bit misleading with hit
[
https://issues.apache.org/jira/browse/KARAF-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508693#comment-13508693
]
Claus Ibsen commented on KARAF-2049:
And you can also shutdown by logging out using the 'logout' command.
Though I guess that only applies if running it in the foreground, right?
Its just a habbit I have when testing with Karaf in the foreground to use
logout.
Instructions in welcome screen is a bit misleading with hit
---
Key: KARAF-2049
URL: https://issues.apache.org/jira/browse/KARAF-2049
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.0
Reporter: Claus Ibsen
Priority: Trivial
The welcome screen for Karaf 2.3.0 is
{code}
__ __
/ //_/ __ _/ __/
/ , / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.3.0)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.
{code}
Notice that it says Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.
I think its a bit misleading for 'osgi:shutdown' as you do not hit that.
You should type that.
So maybe it should say
Hit 'ctrl-d' or type 'osgi:shutdown' to shutdown Karaf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-2049) Instructions in welcome screen is a bit misleading with hit
Claus Ibsen created KARAF-2049:
--
Summary: Instructions in welcome screen is a bit misleading with
hit
Key: KARAF-2049
URL: https://issues.apache.org/jira/browse/KARAF-2049
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.3.0
Reporter: Claus Ibsen
Priority: Trivial
The welcome screen for Karaf 2.3.0 is
{code}
__ __
/ //_/ __ _/ __/
/ , / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.3.0)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.
{code}
Notice that it says Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.
I think its a bit misleading for 'osgi:shutdown' as you do not hit that.
You should type that.
So maybe it should say
Hit 'ctrl-d' or type 'osgi:shutdown' to shutdown Karaf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-1924) Fix the WARN logs from starting a vanilla Karaf 2.3.0
Claus Ibsen created KARAF-1924:
--
Summary: Fix the WARN logs from starting a vanilla Karaf 2.3.0
Key: KARAF-1924
URL: https://issues.apache.org/jira/browse/KARAF-1924
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Affects Versions: 2.3.0
Environment: osx, 10.7.5, jdk 1.6.0_35
Reporter: Claus Ibsen
Priority: Minor
When starting the just released Karaf 2.3.0 on my laptop I see 3 WARNs in the
log
{code}
2012-10-16 07:00:51,051 | WARN | JMX OSGi Agent | core
| ? ? | 29 - org.apache.aries.jmx.core
- 1.0.1 | There are no MBean servers registred, can't register MBeans
2012-10-16 07:00:51,423 | WARN | rint Extender: 1 | MavenRepositoryURL
| maven.commons.MavenRepositoryURL 116 | 1 - org.ops4j.pax.url.mvn -
1.3.5 | Repository spec file:/opt/apache-karaf-2.3.0/system/ does not contain
an identifier. This is deprecated discouraged just evil.
2012-10-16 07:00:51,425 | WARN | rint Extender: 1 | MavenRepositoryURL
| maven.commons.MavenRepositoryURL 116 | 1 - org.ops4j.pax.url.mvn -
1.3.5 | Repository spec file:/opt/apache-karaf-2.3.0/local-repo/ does not
contain an identifier. This is deprecated discouraged just evil.
{code}
It would be nice if Karaf can startup without any WARNs. As end users may think
there is something wrong on their system.
And the warn message above is a bit harsh saying you are evil :(
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-1609) command-watch info does not work
Claus Ibsen created KARAF-1609: -- Summary: command-watch info does not work Key: KARAF-1609 URL: https://issues.apache.org/jira/browse/KARAF-1609 Project: Karaf Issue Type: Bug Components: karaf-core, karaf-shell Affects Versions: 2.2.8 Reporter: Claus Ibsen Priority: Minor I started up a vanilla Karaf 2.2.8, and executed karaf@root command-watch info -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400301#comment-13400301
]
Claus Ibsen commented on KARAF-1585:
Can you guys update the documentation with
- the link I provided had a non working example
- you need to use quotes from the shell
- there is no samples how to do this in a features file, which Freeman was the
only one who could figure out how to do
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400316#comment-13400316
]
Claus Ibsen commented on KARAF-1585:
Yes examples of all 3 uses cases in the manual would be very welcome.
I know wrap is not an ideal solution. But many JARs are not OSGi compliant out
of the box.
And ppl need to be able to use them with Karaf anyway.
So if we have a bit better docs and examples, then that would be great.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Assignee: Freeman Fang
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
Claus Ibsen created KARAF-1585:
--
Summary: Installing using wrap protocol fails when specifying
bundle version
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399907#comment-13399907
]
Claus Ibsen commented on KARAF-1585:
I think the doc is wrong, it should now be a semi colon instead
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4;Bundle-SymbolicName=commons-langBundle-Version=2.4
Bundle ID: 78
commons-langBundle-Version=2.4
{code}
Which then works
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399908#comment-13399908
]
Claus Ibsen commented on KARAF-1585:
I am not sure if the comma was supported in a previous release and changed to
semi colon now.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated KARAF-1585:
---
Priority: Minor (was: Major)
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399909#comment-13399909
]
Claus Ibsen commented on KARAF-1585:
Ah its a $ sign instead.
No wonder ppl think this is hard.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399910#comment-13399910
]
Claus Ibsen commented on KARAF-1585:
Well dont work either with $.
Instructions from here
http://karaf.922171.n3.nabble.com/Arguments-to-wrap-protocol-in-a-feature-definition-td3807247.html
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399911#comment-13399911
]
Claus Ibsen commented on KARAF-1585:
We need this in Camel to support the camel-leveldb feature that needs to be
installed as a wrap
karaf@root osgi:install
wrap:mvn:org.fusesource.leveldbjni/leveldbjni-all/1.2$Bundle-SymbolicName=Foo$Bundle-Version=1.2
java.lang.RuntimeException: URL
[mvn:org.fusesource.leveldbjni/leveldbjni-all/1.2-SymbolicName=Foo-Version=1.2]
could not be resolved.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399930#comment-13399930
]
Claus Ibsen commented on KARAF-1585:
Thanks from the shell it may be possible. But from a features file its not
possible.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399930#comment-13399930
]
Claus Ibsen edited comment on KARAF-1585 at 6/23/12 12:21 PM:
--
Thanks from the shell the single quotes works. But from a features file its not
possible.
{code}
karaf@root features:install camel-leveldb
Error executing command: no protocol:
'wrap:mvn:org.fusesource.leveldbjni/leveldbjni-all/1.2$Bundle-Version=1.2'
{code}
was (Author: davsclaus):
Thanks from the shell it may be possible. But from a features file its not
possible.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399931#comment-13399931
]
Claus Ibsen commented on KARAF-1585:
Also the export packages wont have Bundle-Version in the packages from the
bundle itself. They dont carry version=1.2
Bundle-Name =
wrap_mvn_org.fusesource.leveldbjni_leveldbjni-all_1.2_Bundle-Version_1.2
Bundle-SymbolicName =
wrap_mvn_org.fusesource.leveldbjni_leveldbjni-all_1.2_Bundle-Version_1.2
Bundle-Version = 1.2
Bundle-ManifestVersion = 2
{code}
Import-Package =
org.fusesource.hawtjni.runtime;resolution:=optional,
org.fusesource.leveldbjni;resolution:=optional,
org.fusesource.leveldbjni.internal;resolution:=optional,
org.iq80.leveldb;resolution:=optional
Export-Package =
org.fusesource.hawtjni.runtime,
org.fusesource.leveldbjni;uses:=org.iq80.leveldb,org.fusesource.leveldbjni.internal,org.fusesource.hawtjni.runtime,
org.fusesource.leveldbjni.internal;uses:=org.iq80.leveldb,org.fusesource.hawtjni.runtime,
org.iq80.leveldb
{code}
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1585) Installing using wrap protocol fails when specifying bundle version
[
https://issues.apache.org/jira/browse/KARAF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399963#comment-13399963
]
Claus Ibsen commented on KARAF-1585:
I think there is an issue when using wrap in the features file. As the $ doesnt
work, eg without the quotes. Only from the shell it works.
Installing using wrap protocol fails when specifying bundle version
---
Key: KARAF-1585
URL: https://issues.apache.org/jira/browse/KARAF-1585
Project: Karaf
Issue Type: Bug
Affects Versions: 2.2.7
Reporter: Claus Ibsen
Priority: Minor
I follow the docs at
http://karaf.apache.org/manual/2.2.7/developers-guide/creating-bundles.html
at the section _Creating bundles for third party dependencies_
I try to execute as documented
{code}
karaf@root osgi:install
wrap:mvn:commons-lang/commons-lang/2.4,Bundle-SymbolicName=commons-langBundle-Version=2.4
java.net.MalformedURLException: no protocol:
Bundle-SymbolicName=commons-langBundle-Version=2.4
{code}
But it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1293) feature level start-level not completely finished....
[ https://issues.apache.org/jira/browse/KARAF-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398257#comment-13398257 ] Claus Ibsen commented on KARAF-1293: Okay so the v1.1.0 has the start-level on the features xml element http://karaf.apache.org/xmlns/features/v1.1.0 And I assume the old 1.0.0 is kept without that option, as this was the 1st release? feature level start-level not completely finished - Key: KARAF-1293 URL: https://issues.apache.org/jira/browse/KARAF-1293 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 2.2.5 Reporter: Daniel Kulp Assignee: Jean-Baptiste Onofré Fix For: 2.2.8, 2.3.0, 3.0.0.RC1, 3.0.0 The start-level attribute at the feature level that was introduced in KARAF-576 isn't completely working. First, the schema on the web site at: http://karaf.apache.org/xmlns/features/v1.0.0 doesn't have it. Thus, some xml validation fails. Second, the schema in the tools: ./tooling/features-maven-plugin/src/main/resources/org/apache/karaf/features/karaf-features-1.0.0-ordered.xsd also doesn't have it.(I'm not sure why that second schema even exists) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1293) feature level start-level not completely finished....
[ https://issues.apache.org/jira/browse/KARAF-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398285#comment-13398285 ] Claus Ibsen commented on KARAF-1293: Ah thanks the online schema for 1.0.0 has been re-published and have the start-level attribute for features now as well. Thanks. feature level start-level not completely finished - Key: KARAF-1293 URL: https://issues.apache.org/jira/browse/KARAF-1293 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 2.2.5 Reporter: Daniel Kulp Assignee: Jean-Baptiste Onofré Fix For: 2.2.8, 2.3.0, 3.0.0.RC1, 3.0.0 The start-level attribute at the feature level that was introduced in KARAF-576 isn't completely working. First, the schema on the web site at: http://karaf.apache.org/xmlns/features/v1.0.0 doesn't have it. Thus, some xml validation fails. Second, the schema in the tools: ./tooling/features-maven-plugin/src/main/resources/org/apache/karaf/features/karaf-features-1.0.0-ordered.xsd also doesn't have it.(I'm not sure why that second schema even exists) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1293) feature level start-level not completely finished....
[ https://issues.apache.org/jira/browse/KARAF-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397238#comment-13397238 ] Claus Ibsen commented on KARAF-1293: Also why is a v1.0.0 XSD schema being *changed*? When it has been published, then IMHO it should never change! feature level start-level not completely finished - Key: KARAF-1293 URL: https://issues.apache.org/jira/browse/KARAF-1293 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 2.2.5 Reporter: Daniel Kulp The start-level attribute at the feature level that was introduced in KARAF-576 isn't completely working. First, the schema on the web site at: http://karaf.apache.org/xmlns/features/v1.0.0 doesn't have it. Thus, some xml validation fails. Second, the schema in the tools: ./tooling/features-maven-plugin/src/main/resources/org/apache/karaf/features/karaf-features-1.0.0-ordered.xsd also doesn't have it.(I'm not sure why that second schema even exists) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1497) Capability to alter versions in features and bundles
[
https://issues.apache.org/jira/browse/KARAF-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13282170#comment-13282170
]
Claus Ibsen commented on KARAF-1497:
Yeah it also seems like the activemq-camel feature file, should be [2.9,3) in
the version range.
http://search.maven.org/remotecontent?filepath=org/apache/activemq/activemq-karaf/5.6.0/activemq-karaf-5.6.0-features.xml
Capability to alter versions in features and bundles
Key: KARAF-1497
URL: https://issues.apache.org/jira/browse/KARAF-1497
Project: Karaf
Issue Type: New Feature
Affects Versions: 2.2.7
Reporter: Raul Kripalani
OSGi offers a solid solution to the legendary problem of {{dependency hell}}
in Java, through the use of explicit version numbers and version ranges in
MANIFESTs.
Unfortunately, it requires a lot of developer re-education to understand how
to use version ranges their library bundles. It's common to find bundles with
too narrow version ranges or fixed version numbers. In the real world of Open
Source, not everyone is fully conscious of OSGi concepts and the impact of
version numbers.
The maven-bundle-plugin expresses imports with version ranges by default,
which takes much of the problem away.
In practice, we may know that a bundle X even though importing package A with
fixed version 1.2, it will work reliably with version 1.3 of package A. Right
now, I think that our only way out is to repackage the bundle altering the
MANIFEST.
It'd be neat if Karaf provides functionality to *alter/re-adjust/correct*
version definitions for package imports in bundles.
Moreover, we should be able to alter versions in bundle and feature
references from within Karaf features.
The latter helps tremendously in the inter-connected world of Open Source,
where, for example, Camel and AMQ are using one another, are grouped in
ServiceMix and CXF also uses them!
Imagine the following scenario, testing Camel 2.10-SNAPSHOT on Karaf
(provided that the correct feature repos are registered):
{code}
feature:install camel/2.10-SNAPSHOT
feature:install activemq/5.6.0
feature:install activemq-camel/5.6.0
{code}
The last instruction complains that camel-jms/2.9.2 is not found. Wouldn't it
be awesome if the user could alter the feature definition from within the
shell to reference camel-jms/2.10-SNAPSHOT, instead of tampering with the
local features descriptor and refreshing it?
In my head, the command would look like:
{code}
feature:edit activemq-camel/5.6.0
feature:version-alter --feature camel-jms [2.9.2,2.10]
feature:update
{code}
(resembling the config shell constructs)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1497) Capability to alter versions in features and bundles
[
https://issues.apache.org/jira/browse/KARAF-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13282172#comment-13282172
]
Claus Ibsen commented on KARAF-1497:
I logged AMQ-3859
Capability to alter versions in features and bundles
Key: KARAF-1497
URL: https://issues.apache.org/jira/browse/KARAF-1497
Project: Karaf
Issue Type: New Feature
Affects Versions: 2.2.7
Reporter: Raul Kripalani
OSGi offers a solid solution to the legendary problem of {{dependency hell}}
in Java, through the use of explicit version numbers and version ranges in
MANIFESTs.
Unfortunately, it requires a lot of developer re-education to understand how
to use version ranges their library bundles. It's common to find bundles with
too narrow version ranges or fixed version numbers. In the real world of Open
Source, not everyone is fully conscious of OSGi concepts and the impact of
version numbers.
The maven-bundle-plugin expresses imports with version ranges by default,
which takes much of the problem away.
In practice, we may know that a bundle X even though importing package A with
fixed version 1.2, it will work reliably with version 1.3 of package A. Right
now, I think that our only way out is to repackage the bundle altering the
MANIFEST.
It'd be neat if Karaf provides functionality to *alter/re-adjust/correct*
version definitions for package imports in bundles.
Moreover, we should be able to alter versions in bundle and feature
references from within Karaf features.
The latter helps tremendously in the inter-connected world of Open Source,
where, for example, Camel and AMQ are using one another, are grouped in
ServiceMix and CXF also uses them!
Imagine the following scenario, testing Camel 2.10-SNAPSHOT on Karaf
(provided that the correct feature repos are registered):
{code}
feature:install camel/2.10-SNAPSHOT
feature:install activemq/5.6.0
feature:install activemq-camel/5.6.0
{code}
The last instruction complains that camel-jms/2.9.2 is not found. Wouldn't it
be awesome if the user could alter the feature definition from within the
shell to reference camel-jms/2.10-SNAPSHOT, instead of tampering with the
local features descriptor and refreshing it?
In my head, the command would look like:
{code}
feature:edit activemq-camel/5.6.0
feature:version-alter --feature camel-jms [2.9.2,2.10]
feature:update
{code}
(resembling the config shell constructs)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KARAF-1415) Support Jetty 7.6
Claus Ibsen created KARAF-1415: -- Summary: Support Jetty 7.6 Key: KARAF-1415 URL: https://issues.apache.org/jira/browse/KARAF-1415 Project: Karaf Issue Type: Task Reporter: Claus Ibsen Fix For: 2.3.0 The feature file of Karaf uses Jetty 7.5. In Camel if you want to use Jetty 7.6 then thats not possible with Karaf out of the box, as we use the jetty feature from Karaf. So if camel-jetty is build with Jetty 7.6, then the osgi manifest adds a new package or something Nevertheless you get this problem when install camel-jetty in karaf 2.2.x I suspect the package org.eclipse.jetty.util.ssl 2012-04-27 08:23:15.190:INFO:oejs.Server:jetty-7.5.4.v20111024 2012-04-27 08:23:15.230:INFO:oejs.AbstractConnector:Started NIOSocketConnectorWrapper@0.0.0.0:8080 STARTING ERROR: Error starting file:bundles/org.apache.camel.camel-jetty_2.10.0.SNAPSHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.camel.camel-jetty [73]: Unable to resolve 73.0: missing requirement [73.0] package; ((package=org.eclipse.jetty.util.ssl)(version=7.0.0)(!(version=8.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.camel.camel-jetty [73]: Unable to resolve 73.0: missing requirement [73.0] package; ((package=org.eclipse.jetty.util.ssl)(version=7.0.0)(!(version=8.0.0))) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3404) at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1143) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-245) Export SUN packages in config.properties like done in ServiceMix
[
https://issues.apache.org/jira/browse/KARAF-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923844#action_12923844
]
Claus Ibsen commented on KARAF-245:
---
Isn't this in {{jre.properties}}?
I found it here
http://svn.apache.org/repos/asf/servicemix/smx4/features/trunk/assembly/src/main/filtered-resources/etc/jre.properties
And its only for JDK 1.6? Why isn't it done for JDK 1.5 as well? I think the
XML stuff is also part of JDK 1.5.
com.sun.org.apache.xalan.internal.xsltc.trax, \
com.sun.org.apache.xerces.internal.dom, \
com.sun.org.apache.xerces.internal.jaxp, \
com.sun.org.apache.xerces.internal.xni, \
com.sun.jndi.ldap, \
Export SUN packages in config.properties like done in ServiceMix
Key: KARAF-245
URL: https://issues.apache.org/jira/browse/KARAF-245
Project: Karaf
Issue Type: Improvement
Components: runtime
Affects Versions: 2.0.0, 2.1.0
Environment: davsclaus:/opt$ mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Claus Ibsen
I am updating chapter 13 about OSGi and I hit a problem with camel-cxf
and Karaf 2.1
He is what I do
davsclaus:/opt$ mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
davsclaus:/opt$ tar -xf ~/Downloads/apache-karaf-2.1.0.tar.gz
davsclaus:/opt/apache-karaf-2.1.0$ bin/karaf
ka...@root features:addurl
mvn:org.apache.camel.karaf/apache-camel/2.5-SNAPSHOT/xml/features
ka...@root features:install camel-cxf
Error executing command: Could not start bundle
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1
in feature(s) : Unresolved constraint in bundle
org.apache.servicemix.bundles.saaj-impl [90]: Unable to resolve 90.0:
missing requirement [90.0] package;
(package=com.sun.org.apache.xerces.internal.dom)
And I get the above problem with the SUN package.
I have not changed any configuration settings on Karaf.
I just tried with equinox instead of felix as osgi container. Same problem
ka...@root features:install camel
ka...@root features:
features:addurl features:info
features:install features:list
features:listrepositoriesfeatures:listurl
features:listversionsfeatures:refreshurl
features:removerepositoryfeatures:removeurl features:uninstall
ka...@root features:install camel-cxf
Refreshing bundles org.springframework.context (38),
org.springframework.context.support (39),
org.apache.servicemix.bundles.cglib (47), org.apache.camel.camel-core
(46), org.springframework.aop (34),
org.apache.servicemix.bundles.jaxb-impl (44)
Error executing command: Could not start bundle
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1
in feature(s) : The bundle
org.apache.servicemix.bundles.saaj-impl_1.3.2.1 [90] could not be
resolved. Reason: Missing Constraint: Import-Package:
com.sun.org.apache.xerces.internal.dom; version=0.0.0
And the solution suggested by Willem Jiang
Hi Claus,
ServiceMix is using a different etc/config.properties from the karaf, and it
exports these sun packages
com.sun.org.apache.xalan.internal.xsltc.trax, \
com.sun.org.apache.xerces.internal.dom, \
com.sun.org.apache.xerces.internal.jaxp, \
com.sun.org.apache.xerces.internal.xni, \
I'm afraid you need to do the same thing in karaf etc/config.properties file
if you are try to using the saaj-impl from sun.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-245) Export SUN packages in config.properties like done in ServiceMix
[ https://issues.apache.org/jira/browse/KARAF-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923859#action_12923859 ] Claus Ibsen commented on KARAF-245: --- Jesus its one big guess game. In SMX the jre.properties have selected packages commented out. Looks like someone have done some trail and error and just fixed it by adding and committing out stuff. Export SUN packages in config.properties like done in ServiceMix Key: KARAF-245 URL: https://issues.apache.org/jira/browse/KARAF-245 Project: Karaf Issue Type: Improvement Components: runtime Affects Versions: 2.0.0, 2.1.0 Environment: davsclaus:/opt$ mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Claus Ibsen I am updating chapter 13 about OSGi and I hit a problem with camel-cxf and Karaf 2.1 He is what I do davsclaus:/opt$ mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac davsclaus:/opt$ tar -xf ~/Downloads/apache-karaf-2.1.0.tar.gz davsclaus:/opt/apache-karaf-2.1.0$ bin/karaf ka...@root features:addurl mvn:org.apache.camel.karaf/apache-camel/2.5-SNAPSHOT/xml/features ka...@root features:install camel-cxf Error executing command: Could not start bundle mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1 in feature(s) : Unresolved constraint in bundle org.apache.servicemix.bundles.saaj-impl [90]: Unable to resolve 90.0: missing requirement [90.0] package; (package=com.sun.org.apache.xerces.internal.dom) And I get the above problem with the SUN package. I have not changed any configuration settings on Karaf. I just tried with equinox instead of felix as osgi container. Same problem ka...@root features:install camel ka...@root features: features:addurl features:info features:install features:list features:listrepositoriesfeatures:listurl features:listversionsfeatures:refreshurl features:removerepositoryfeatures:removeurl features:uninstall ka...@root features:install camel-cxf Refreshing bundles org.springframework.context (38), org.springframework.context.support (39), org.apache.servicemix.bundles.cglib (47), org.apache.camel.camel-core (46), org.springframework.aop (34), org.apache.servicemix.bundles.jaxb-impl (44) Error executing command: Could not start bundle mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1 in feature(s) : The bundle org.apache.servicemix.bundles.saaj-impl_1.3.2.1 [90] could not be resolved. Reason: Missing Constraint: Import-Package: com.sun.org.apache.xerces.internal.dom; version=0.0.0 And the solution suggested by Willem Jiang Hi Claus, ServiceMix is using a different etc/config.properties from the karaf, and it exports these sun packages com.sun.org.apache.xalan.internal.xsltc.trax, \ com.sun.org.apache.xerces.internal.dom, \ com.sun.org.apache.xerces.internal.jaxp, \ com.sun.org.apache.xerces.internal.xni, \ I'm afraid you need to do the same thing in karaf etc/config.properties file if you are try to using the saaj-impl from sun. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
