[jira] [Commented] (KARAF-3246) Rename jpa features as jpa/jpa20 and jpa21
[ https://issues.apache.org/jira/browse/KARAF-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148864#comment-14148864 ] Jean-Baptiste Onofré commented on KARAF-3246: - Fixed on karaf-2.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=714c727f4875e7aa96d36ab524a50dec7fe5820d Rename jpa features as jpa/jpa20 and jpa21 -- Key: KARAF-3246 URL: https://issues.apache.org/jira/browse/KARAF-3246 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.2, 2.4.1 Now, Aries JPA provides jpa 2.0 and jpa 2.1 support. However, the jpa features in Karaf are non easy to understand: jpa 1.0.0 and 1.0.1. I propose to rename: - jpa 1.0.0 feature as jpa20 1.0.0 (and keep jpa alias for backward compatibility) - jpa 1.0.1 feature as jpa21 1.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3246) Rename jpa features as jpa/jpa20 and jpa21
[ https://issues.apache.org/jira/browse/KARAF-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-3246. - Resolution: Fixed Rename jpa features as jpa/jpa20 and jpa21 -- Key: KARAF-3246 URL: https://issues.apache.org/jira/browse/KARAF-3246 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.2, 2.4.1 Now, Aries JPA provides jpa 2.0 and jpa 2.1 support. However, the jpa features in Karaf are non easy to understand: jpa 1.0.0 and 1.0.1. I propose to rename: - jpa 1.0.0 feature as jpa20 1.0.0 (and keep jpa alias for backward compatibility) - jpa 1.0.1 feature as jpa21 1.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-1514) Improve feature file generation to be able to create features out of special feature poms
[ https://issues.apache.org/jira/browse/KARAF-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148889#comment-14148889 ] Jean-Baptiste Onofré commented on KARAF-1514: - Fixed on master: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=39a207507b43e0ebba505457aa6e806aa0f398bb Improve feature file generation to be able to create features out of special feature poms - Key: KARAF-1514 URL: https://issues.apache.org/jira/browse/KARAF-1514 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Christian Schneider Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.2 Attachments: 0001-allow-ignoring-scope-provided-dependencies.patch Currently we have no way to describe several features without having a template feature file. To improve that we could describe a single feature as a pom which can depend on other poms and jars. We could then create another pom for the feature file which depends on the feature poms with scope feature. So the plugin would know to create a feature for each pom of scope feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-1514) Improve feature file generation to be able to create features out of special feature poms
[ https://issues.apache.org/jira/browse/KARAF-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148895#comment-14148895 ] Jean-Baptiste Onofré commented on KARAF-1514: - Fixed on karaf-3.0.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=7f9ba5ba01d2fced0f5c6d67c75e3e84fc784183 Improve feature file generation to be able to create features out of special feature poms - Key: KARAF-1514 URL: https://issues.apache.org/jira/browse/KARAF-1514 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Christian Schneider Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.2 Attachments: 0001-allow-ignoring-scope-provided-dependencies.patch Currently we have no way to describe several features without having a template feature file. To improve that we could describe a single feature as a pom which can depend on other poms and jars. We could then create another pom for the feature file which depends on the feature poms with scope feature. So the plugin would know to create a feature for each pom of scope feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-1514) Improve feature file generation to be able to create features out of special feature poms
[ https://issues.apache.org/jira/browse/KARAF-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-1514. - Resolution: Fixed Improve feature file generation to be able to create features out of special feature poms - Key: KARAF-1514 URL: https://issues.apache.org/jira/browse/KARAF-1514 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Christian Schneider Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.2 Attachments: 0001-allow-ignoring-scope-provided-dependencies.patch Currently we have no way to describe several features without having a template feature file. To improve that we could describe a single feature as a pom which can depend on other poms and jars. We could then create another pom for the feature file which depends on the feature poms with scope feature. So the plugin would know to create a feature for each pom of scope feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1583) karaf-maven-plugin ignores dependency on feature
[
https://issues.apache.org/jira/browse/KARAF-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1583:
Fix Version/s: (was: 3.0.2)
3.0.3
karaf-maven-plugin ignores dependency on feature
Key: KARAF-1583
URL: https://issues.apache.org/jira/browse/KARAF-1583
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Brian Topping
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
When a project has a dependency on a feature, the dependency should be
rendered in the features.xml generated by
{{karaf-maven-plugin:features-generate-descriptor}} as a {{repository}}
element.
I thought I added this, but it must have gotten lost in the patches and will
submit another patch after KARAF-1537 is applied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-1584) karaf-maven-plugin ignores provided scope on dependency
[
https://issues.apache.org/jira/browse/KARAF-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148911#comment-14148911
]
Jean-Baptiste Onofré commented on KARAF-1584:
-
The features-generate-descriptor goal now supports ignoreScopeProvided (false
by default). If you set ignoreScopeProvided to true, the provided dependency
won't be included in features.xml.
karaf-maven-plugin ignores provided scope on dependency
---
Key: KARAF-1584
URL: https://issues.apache.org/jira/browse/KARAF-1584
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Brian Topping
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
A dependency expressed in a project POM with {{provided}} scope should not be
rendered in a features.xml by
{{karaf-maven-plugin:features-generate-descriptor}}.
A good example of this is slf4j-api. A generated feature that lists that
dependency will not load for some reason that doesn't particularly matter,
but there needs to be a way to both express the dependency for compilation as
well as not have the dependency listed in the feature. {{provided}} scope
seems to be the most accurate way to do that.
The IT test in KARAF-1537 named test-aggregate-features demonstrates what I
am talking about.
I'll submit a patch after KARAF-1537 is applied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-1584) karaf-maven-plugin ignores provided scope on dependency
[
https://issues.apache.org/jira/browse/KARAF-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-1584.
-
Resolution: Fixed
karaf-maven-plugin ignores provided scope on dependency
---
Key: KARAF-1584
URL: https://issues.apache.org/jira/browse/KARAF-1584
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Brian Topping
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
A dependency expressed in a project POM with {{provided}} scope should not be
rendered in a features.xml by
{{karaf-maven-plugin:features-generate-descriptor}}.
A good example of this is slf4j-api. A generated feature that lists that
dependency will not load for some reason that doesn't particularly matter,
but there needs to be a way to both express the dependency for compilation as
well as not have the dependency listed in the feature. {{provided}} scope
seems to be the most accurate way to do that.
The IT test in KARAF-1537 named test-aggregate-features demonstrates what I
am talking about.
I'll submit a patch after KARAF-1537 is applied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-1972) karaf-maven-plugin should respect scope
[
https://issues.apache.org/jira/browse/KARAF-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1972:
Fix Version/s: (was: 3.0.2)
3.0.3
karaf-maven-plugin should respect scope
---
Key: KARAF-1972
URL: https://issues.apache.org/jira/browse/KARAF-1972
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Andrei Pozolotin
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Attachments: 0001-Fixing-the-scope-handling.patch, KARAF-1972.patch
PROBLEM:
currently, in project with dependencies such as these:
{code}
dependency
groupIdorg.osgi/groupId
artifactIdorg.osgi.core/artifactId
scopeprovided/scope
/dependency
dependency
groupIdorg.osgi/groupId
artifactIdorg.osgi.compendium/artifactId
scopeprovided/scope
/dependency
{code}
karaf-maven-plugin with invocation like this:
{code}
build
plugins
plugin
groupIdorg.apache.karaf.tooling/groupId
artifactIdkaraf-maven-plugin/artifactId
version3.0.0-SNAPSHOT/version
executions
execution
idgenerate-descriptor/id
phasepackage/phase
goals
goalfeatures-generate-descriptor/goal
/goals
configuration
installModeauto/installMode
startLevel90/startLevel
outputFile./target/${project.artifactId}-${project.version}-features.xml/outputFile
/configuration
/execution
/executions
/plugin
/plugins
/build
{code}
will produce features.xml with entries:
{code}
bundle start-level=90mvn:org.osgi/org.osgi.core/4.3.0/bundle
bundle
start-level=90mvn:org.osgi/org.osgi.compendium/4.2.0/bundle
{code}
which is not as expected. scope==provided should not show up there.
SOLUTION:
instead, karaf-maven-plugin should respect scope;
I suggest to add karaf-maven-plugin config parameters such as:
{code}
scopeInclude
scopecompile/scope
/scopeInclude
{code}
or
{code}
scopeExclude
scopeprovided/scope
scoperuntime/scope
scopetest/scope
/scopeExclude
{code}
IMPACT:
current plugin behavior forces to create a separate maven
project to generate features.xml, since scope==provided
is in fact excluded from transitive dependencies in that case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-1972) karaf-maven-plugin should respect scope
[
https://issues.apache.org/jira/browse/KARAF-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148912#comment-14148912
]
Jean-Baptiste Onofré commented on KARAF-1972:
-
I added a ignoreScopeProvided configuration to the features-generate-descriptor
goal.
karaf-maven-plugin should respect scope
---
Key: KARAF-1972
URL: https://issues.apache.org/jira/browse/KARAF-1972
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Andrei Pozolotin
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Attachments: 0001-Fixing-the-scope-handling.patch, KARAF-1972.patch
PROBLEM:
currently, in project with dependencies such as these:
{code}
dependency
groupIdorg.osgi/groupId
artifactIdorg.osgi.core/artifactId
scopeprovided/scope
/dependency
dependency
groupIdorg.osgi/groupId
artifactIdorg.osgi.compendium/artifactId
scopeprovided/scope
/dependency
{code}
karaf-maven-plugin with invocation like this:
{code}
build
plugins
plugin
groupIdorg.apache.karaf.tooling/groupId
artifactIdkaraf-maven-plugin/artifactId
version3.0.0-SNAPSHOT/version
executions
execution
idgenerate-descriptor/id
phasepackage/phase
goals
goalfeatures-generate-descriptor/goal
/goals
configuration
installModeauto/installMode
startLevel90/startLevel
outputFile./target/${project.artifactId}-${project.version}-features.xml/outputFile
/configuration
/execution
/executions
/plugin
/plugins
/build
{code}
will produce features.xml with entries:
{code}
bundle start-level=90mvn:org.osgi/org.osgi.core/4.3.0/bundle
bundle
start-level=90mvn:org.osgi/org.osgi.compendium/4.2.0/bundle
{code}
which is not as expected. scope==provided should not show up there.
SOLUTION:
instead, karaf-maven-plugin should respect scope;
I suggest to add karaf-maven-plugin config parameters such as:
{code}
scopeInclude
scopecompile/scope
/scopeInclude
{code}
or
{code}
scopeExclude
scopeprovided/scope
scoperuntime/scope
scopetest/scope
/scopeExclude
{code}
IMPACT:
current plugin behavior forces to create a separate maven
project to generate features.xml, since scope==provided
is in fact excluded from transitive dependencies in that case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148935#comment-14148935 ] Jean-Philippe CLEMENT commented on KARAF-2920: -- We are using karaf-maven-plugin and we currently have the issue that bootFeatures are not built-in but downloaded on first launch. Is it related to the feature condition you are talking about? Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148940#comment-14148940 ] Jean-Baptiste Onofré commented on KARAF-2920: - Can you share your pom.xml ? If you have bootFeatures/ containing the features, it should be resolved and present in the system folder. Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1728) BundleException: Bundle installation rejected by hook. error when installing from features XML file
[
https://issues.apache.org/jira/browse/KARAF-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1728:
Fix Version/s: (was: 3.0.2)
3.0.3
BundleException: Bundle installation rejected by hook. error when installing
from features XML file
---
Key: KARAF-1728
URL: https://issues.apache.org/jira/browse/KARAF-1728
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 3.0.0
Reporter: Hendy Irawan
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Console:
{code}
karaf@root() feature:install -v commerce-shell
Installing feature commerce-shell 4.0.1-SNAPSHOT
Installing feature commerce-core 4.0.1-SNAPSHOT
Installing feature oss-deps 1.0.0
Installing feature httpclient 4.2.1
Installing feature jpa 1.0.0
Installing feature xml-specs-api 1.9.0
Installing feature soluvas-framework 1.0.0-SNAPSHOT
Installing feature magja 1.0.3-SNAPSHOT
Installing feature http 3.0.0-SNAPSHOT
Installing feature apache-ldap-client 1.0.0-M12
Installing feature drools 5.4.0
Installing feature blueprints-neo4j 1.2
Installing feature neo4j 1.7.2
Installing bundle
wrap:mvn:org.neo4j/neo4j-kernel/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-kernel;=split,*
Installing bundle
wrap:mvn:org.neo4j/neo4j-lucene-index/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-lucene-index;=split,*
Installing bundle wrap:mvn:org.neo4j/neo4j-cypher/1.8.M07
Installing bundle wrap:mvn:org.neo4j/neo4j-rest-graphdb/1.7
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-core/1.2
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-neo4j-graph/1.2
Installing bundle wrap:mvn:com.tinkerpop/frames/0.7
Installing feature soluvas-image-store 1.0.0-SNAPSHOT
Installing bundle wrap:mvn:net.coobird/thumbnailator/0.4.1
Installing bundle mvn:org.soluvas/soluvas-image-store/1.0.0-SNAPSHOT
Installing feature soluvas-ldap 1.0.0-SNAPSHOT
Installing bundle
mvn:org.apache.geronimo.specs/geronimo-validation_1.0_spec/1.1
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-common/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-api/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle mvn:org.soluvas/soluvas-ldap/1.0.0-SNAPSHOT
Installing feature openjpa 2.2.0
Installing feature jndi 1.0.0
Found installed bundle: org.apache.aries.util [9]
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.api/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.core/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.rmi/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.url/1.0.0
Installing bundle
mvn:org.apache.aries.jndi/org.apache.aries.jndi.legacy.support/1.0.0
Installing feature transaction 1.0.0
Installing bundle mvn:commons-pool/commons-pool/1.6
Error executing command: Bundle installation rejected by hook.
{code}
Log and stack trace:
{code}
2012-08-15 18:12:42,454 | INFO | Thread-6 | ShellUtil
| 40 - org.apache.karaf.shell.console - 3.0.0.SNAPSHOT | Exception
caught while executing command
org.osgi.framework.BundleException: Bundle installation rejected by hook.
at org.apache.felix.framework.Felix.installBundle(Felix.java:2872)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:894)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:606)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:450)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:431)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:420)
at Proxyd6c71027_7662_4a47_bbd6_ba300c8a7c7a.installFeature(Unknown
Source)
at
[jira] [Commented] (KARAF-1728) BundleException: Bundle installation rejected by hook. error when installing from features XML file
[
https://issues.apache.org/jira/browse/KARAF-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148945#comment-14148945
]
Jean-Baptiste Onofré commented on KARAF-1728:
-
I'm not able to reproduce your issue (by installing the transaction feature).
Do you have some details (OS, JVM, ...) ?
BundleException: Bundle installation rejected by hook. error when installing
from features XML file
---
Key: KARAF-1728
URL: https://issues.apache.org/jira/browse/KARAF-1728
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 3.0.0
Reporter: Hendy Irawan
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Console:
{code}
karaf@root() feature:install -v commerce-shell
Installing feature commerce-shell 4.0.1-SNAPSHOT
Installing feature commerce-core 4.0.1-SNAPSHOT
Installing feature oss-deps 1.0.0
Installing feature httpclient 4.2.1
Installing feature jpa 1.0.0
Installing feature xml-specs-api 1.9.0
Installing feature soluvas-framework 1.0.0-SNAPSHOT
Installing feature magja 1.0.3-SNAPSHOT
Installing feature http 3.0.0-SNAPSHOT
Installing feature apache-ldap-client 1.0.0-M12
Installing feature drools 5.4.0
Installing feature blueprints-neo4j 1.2
Installing feature neo4j 1.7.2
Installing bundle
wrap:mvn:org.neo4j/neo4j-kernel/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-kernel;=split,*
Installing bundle
wrap:mvn:org.neo4j/neo4j-lucene-index/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-lucene-index;=split,*
Installing bundle wrap:mvn:org.neo4j/neo4j-cypher/1.8.M07
Installing bundle wrap:mvn:org.neo4j/neo4j-rest-graphdb/1.7
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-core/1.2
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-neo4j-graph/1.2
Installing bundle wrap:mvn:com.tinkerpop/frames/0.7
Installing feature soluvas-image-store 1.0.0-SNAPSHOT
Installing bundle wrap:mvn:net.coobird/thumbnailator/0.4.1
Installing bundle mvn:org.soluvas/soluvas-image-store/1.0.0-SNAPSHOT
Installing feature soluvas-ldap 1.0.0-SNAPSHOT
Installing bundle
mvn:org.apache.geronimo.specs/geronimo-validation_1.0_spec/1.1
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-common/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-api/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle mvn:org.soluvas/soluvas-ldap/1.0.0-SNAPSHOT
Installing feature openjpa 2.2.0
Installing feature jndi 1.0.0
Found installed bundle: org.apache.aries.util [9]
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.api/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.core/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.rmi/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.url/1.0.0
Installing bundle
mvn:org.apache.aries.jndi/org.apache.aries.jndi.legacy.support/1.0.0
Installing feature transaction 1.0.0
Installing bundle mvn:commons-pool/commons-pool/1.6
Error executing command: Bundle installation rejected by hook.
{code}
Log and stack trace:
{code}
2012-08-15 18:12:42,454 | INFO | Thread-6 | ShellUtil
| 40 - org.apache.karaf.shell.console - 3.0.0.SNAPSHOT | Exception
caught while executing command
org.osgi.framework.BundleException: Bundle installation rejected by hook.
at org.apache.felix.framework.Felix.installBundle(Felix.java:2872)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:894)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:606)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:450)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:431)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:420)
at
[jira] [Updated] (KARAF-1729) Cannot uninstall bundle, bundle xx is invalid
[
https://issues.apache.org/jira/browse/KARAF-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1729:
Fix Version/s: (was: 3.0.2)
3.0.3
Cannot uninstall bundle, bundle xx is invalid
-
Key: KARAF-1729
URL: https://issues.apache.org/jira/browse/KARAF-1729
Project: Karaf
Issue Type: Bug
Components: karaf-osgi
Affects Versions: 3.0.0
Reporter: Hendy Irawan
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Karaf marks a bundle as installed and active, but I can't uninstall it, stop
it.
{code}
karaf@root() list -t 0 -s | grep pool
[1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
karaf@root() uninstall 1295
Bundle 1295 is invalid
No bundles specified.
karaf@root() uninstall 1295
Bundle 1295 is invalid
No bundles specified.
karaf@root() list -t 0 -s | grep pool
[1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
karaf@root() uninstall org.apache.commons.pool
No bundles specified.
karaf@root() list -t 0 -s | grep pool
[1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
karaf@root() stop 1295
Bundle 1295 is invalid
No bundles specified.
{code}
Workaround: Delete folder karaf/data/cache/bundle1295
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-1729) Cannot uninstall bundle, bundle xx is invalid
[
https://issues.apache.org/jira/browse/KARAF-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148953#comment-14148953
]
Jean-Baptiste Onofré commented on KARAF-1729:
-
I can't reproduce the problem on 3.0.2-SNAPSHOT, even killing the Karaf java
process (kill -9).
Can you try with 3.0.2-SNAPSHOT ?
Cannot uninstall bundle, bundle xx is invalid
-
Key: KARAF-1729
URL: https://issues.apache.org/jira/browse/KARAF-1729
Project: Karaf
Issue Type: Bug
Components: karaf-osgi
Affects Versions: 3.0.0
Reporter: Hendy Irawan
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.3
Karaf marks a bundle as installed and active, but I can't uninstall it, stop
it.
{code}
karaf@root() list -t 0 -s | grep pool
[1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
karaf@root() uninstall 1295
Bundle 1295 is invalid
No bundles specified.
karaf@root() uninstall 1295
Bundle 1295 is invalid
No bundles specified.
karaf@root() list -t 0 -s | grep pool
[1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
karaf@root() uninstall org.apache.commons.pool
No bundles specified.
karaf@root() list -t 0 -s | grep pool
[1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
karaf@root() stop 1295
Bundle 1295 is invalid
No bundles specified.
{code}
Workaround: Delete folder karaf/data/cache/bundle1295
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148975#comment-14148975 ] Jean-Philippe CLEMENT commented on KARAF-2920: -- project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion parent groupIdxxxPARENTGROUPIDxxx/groupId artifactIdxxxPARENTARTIFACTIDxxx/artifactId versionxxxPARENTVERSIONxxx/version relativePath../relativePath /parent artifactIdxxxGROUPIDxxx/artifactId packagingkaraf-assembly/packaging nameAssembly xxxPROJECTxxx/name build plugins plugin groupIdorg.apache.karaf.tooling/groupId artifactIdkaraf-maven-plugin/artifactId configuration bootFeatures featurestandard/feature featuremanagement/feature featureour-feature/feature /bootFeatures /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution configuration artifactItems artifactItem groupIdxxxBRANDINGGROUPIDxxx/groupId artifactIdxxxBRANDINGARTIFACTIDxxx/artifactId versionxxxBRANDINGVERSIONIDxxx/version outputDirectorytarget/assembly/lib/outputDirectory /artifactItem /artifactItems /configuration /execution /executions /plugin /plugins /build dependencies dependency groupIdorg.apache.karaf.features/groupId artifactIdframework/artifactId version3.0.2-SNAPSHOT/version typekar/type /dependency dependency groupIdorg.apache.karaf.features/groupId artifactIdstandard/artifactId version3.0.2-SNAPSHOT/version typexml/type classifierfeatures/classifier scoperuntime/scope /dependency dependency groupIdxxxCUSTOMFEATUREGROUPIDxxx/groupId artifactIdour-feature/artifactId versionxxxCUSTOMFEATUREVERSIONxxx/version typexml/type classifierfeatures/classifier scoperuntime/scope /dependency /dependencies /project Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148978#comment-14148978 ] Jean-Philippe CLEMENT commented on KARAF-2920: -- Note that as dev machine do not have access to internet (neither Maven repos), we use an old version of Karaf 3.0.2-SNAPSHOT. Our feature is starting on first launch but it needs to be downloaded from our Maven repo which is a problem after dev stage. Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148980#comment-14148980 ] Jean-Philippe CLEMENT commented on KARAF-2920: -- I just found that we are using Karaf 3.0.2 but the karaf-maven-plugin is 3.0.1 ... can it be the cause? Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148980#comment-14148980 ] Jean-Philippe CLEMENT edited comment on KARAF-2920 at 9/26/14 9:48 AM: --- I just found that we are using Karaf 3.0.2-SNAPSHOT but the karaf-maven-plugin is 3.0.1 ... can it be the cause? was (Author: jeanphiphi): I just found that we are using Karaf 3.0.2 but the karaf-maven-plugin is 3.0.1 ... can it be the cause? Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148986#comment-14148986 ] Jean-Baptiste Onofré commented on KARAF-2920: - Oh yes, I completely refactored and improved the plugin in 3.0.2-SNAPSHOT. Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 3.0.2) 3.0.3 Review and update documentation --- Key: KARAF-2511 URL: https://issues.apache.org/jira/browse/KARAF-2511 Project: Karaf Issue Type: Task Components: karaf-documentation Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.3 The documentation (manual) should be reviewed: - The subshell part should be described (usage and configuration). - The code samples/screenshots have to be updated with Karaf 3.0.0 use cases - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-2742) karaf-maven-plugin can not include filtered resources in a custom distribution
[
https://issues.apache.org/jira/browse/KARAF-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-2742 started by Jean-Baptiste Onofré.
---
karaf-maven-plugin can not include filtered resources in a custom distribution
--
Key: KARAF-2742
URL: https://issues.apache.org/jira/browse/KARAF-2742
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0
Environment: Fedora 20, Oracle JDK 1.7.0_51, Maven 3.0.4
Reporter: Partha Roy
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Attachments: karaf-filtering-bug.tar.gz
I am trying to build a custom Karaf distribution by following
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html.
I need to add a .cfg file in the karaf/etc directory. However, the maven
resource filtering on that .cfg file does not work.
The sample project looks like:
{code}
karaf-filtering-bug
├── pom.xml
├── readme.txt
└── src
└── main
└── filtered-resources
└── etc
└── filtering.bug.cfg
{code}
The filtering.bug.cfg file should be filtered with maven resource plugin. I
am expecting that the filtered file will get included in the karaf
distribution. I can see that target/classes/etc/filtering.bug.cfg actually
has the correct content but the karaf/etc/filtering.bug.cfg still has the
maven variables.
I'll upload the sample project as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149027#comment-14149027 ] Jean-Philippe CLEMENT commented on KARAF-2920: -- Ok we will move to 3.0.2-SNAPSHOT. Is there any new option so set in the pom.xml Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2920) Karaf freezes during startup
[ https://issues.apache.org/jira/browse/KARAF-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149037#comment-14149037 ] Jean-Baptiste Onofré commented on KARAF-2920: - The only new option is ignoreDependencyFlag (true by default) to ignore the value of dependency attribute in the bundle defintion of a feature. Karaf freezes during startup Key: KARAF-2920 URL: https://issues.apache.org/jira/browse/KARAF-2920 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 3.0.1 Environment: RHEL 6.2 with Java 6 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Karaf freezes during startup. The installation is a clean untar. There is no way to get Karaf running! Logs shows that Karaf tries to get something from Maven and fails. Then some services are missing and so Karaf freezes. The RHEL on which Karaf is starting has access to a local Maven repository but none of RHEL nor Maven have access to internet. I already gave the log on the Karaf mailing list - I can provide it if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2742) karaf-maven-plugin can not include filtered resources in a custom distribution
[
https://issues.apache.org/jira/browse/KARAF-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149121#comment-14149121
]
Jean-Baptiste Onofré commented on KARAF-2742:
-
Actually, it's already possible, you just have to execute the resources plugin
just before the install-kar:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
executions
execution
idprocess-resources/id
goals
goalresources/goal
/goals
/execution
/executions
/plugin
{code}
See your pom.xml updated:
{code}
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdorg.apache.karaf.bugs/groupId
artifactIdresource-filtering-bug/artifactId
version0.1-SNAPSHOT/version
nameDemo project to reproduce resource filtering bug/name
packagingkaraf-assembly/packaging
properties
karaf.version3.0.2-SNAPSHOT/karaf.version
mongo.dbdatabase/mongo.db
mongo.hostlocalhost/mongo.host
mongo.useruser/mongo.user
mongo.passwordpassword/mongo.password
/properties
dependencies
dependency
groupIdorg.apache.karaf.features/groupId
artifactIdframework/artifactId
version${karaf.version}/version
typekar/type
/dependency
dependency
groupIdorg.apache.karaf.features/groupId
artifactIdstandard/artifactId
version${karaf.version}/version
typexml/type
classifierfeatures/classifier
scoperuntime/scope
/dependency
/dependencies
build
resources
resource
directorysrc/main/filtered-resources/directory
filteringtrue/filtering
includes
include**/*/include
/includes
/resource
/resources
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
executions
execution
idprocess-resources/id
goals
goalresources/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.karaf.tooling/groupId
artifactIdkaraf-maven-plugin/artifactId
version${karaf.version}/version
extensionstrue/extensions
configuration
!-- no startupFeatures --
bootFeatures
featurestandard/feature
featuremanagement/feature
/bootFeatures
/configuration
/plugin
/plugins
pluginManagement
plugins
!--This plugin's configuration is used to store Eclipse m2e
settings only. It has no
influence on the Maven build itself. --
plugin
groupIdorg.eclipse.m2e/groupId
artifactIdlifecycle-mapping/artifactId
version1.0.0/version
configuration
lifecycleMappingMetadata
pluginExecutions
pluginExecution
pluginExecutionFilter
groupIdorg.apache.karaf.tooling/groupId
artifactIdkaraf-maven-plugin/artifactId
versionRange[3.0.0,)/versionRange
goals
goalinstall-kars/goal
/goals
/pluginExecutionFilter
action
ignore/ignore
/action
/pluginExecution
/pluginExecutions
/lifecycleMappingMetadata
/configuration
/plugin
/plugins
/pluginManagement
/build
/project
{code}
karaf-maven-plugin can not include filtered resources in a custom distribution
[jira] [Commented] (KARAF-2742) karaf-maven-plugin can not include filtered resources in a custom distribution
[
https://issues.apache.org/jira/browse/KARAF-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149123#comment-14149123
]
Jean-Baptiste Onofré commented on KARAF-2742:
-
Anyway, I'm updating the documentation and the archetype to be more straight
forward.
karaf-maven-plugin can not include filtered resources in a custom distribution
--
Key: KARAF-2742
URL: https://issues.apache.org/jira/browse/KARAF-2742
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0
Environment: Fedora 20, Oracle JDK 1.7.0_51, Maven 3.0.4
Reporter: Partha Roy
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Attachments: karaf-filtering-bug.tar.gz
I am trying to build a custom Karaf distribution by following
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html.
I need to add a .cfg file in the karaf/etc directory. However, the maven
resource filtering on that .cfg file does not work.
The sample project looks like:
{code}
karaf-filtering-bug
├── pom.xml
├── readme.txt
└── src
└── main
└── filtered-resources
└── etc
└── filtering.bug.cfg
{code}
The filtering.bug.cfg file should be filtered with maven resource plugin. I
am expecting that the filtered file will get included in the karaf
distribution. I can see that target/classes/etc/filtering.bug.cfg actually
has the correct content but the karaf/etc/filtering.bug.cfg still has the
maven variables.
I'll upload the sample project as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-2742) karaf-maven-plugin can not include filtered resources in a custom distribution
[
https://issues.apache.org/jira/browse/KARAF-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149141#comment-14149141
]
Jean-Baptiste Onofré commented on KARAF-2742:
-
Documented on karaf-3.0.x:
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=41add7eb13b60dd8f51f6bdd997ea7572d85c2ed
karaf-maven-plugin can not include filtered resources in a custom distribution
--
Key: KARAF-2742
URL: https://issues.apache.org/jira/browse/KARAF-2742
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0
Environment: Fedora 20, Oracle JDK 1.7.0_51, Maven 3.0.4
Reporter: Partha Roy
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Attachments: karaf-filtering-bug.tar.gz
I am trying to build a custom Karaf distribution by following
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html.
I need to add a .cfg file in the karaf/etc directory. However, the maven
resource filtering on that .cfg file does not work.
The sample project looks like:
{code}
karaf-filtering-bug
├── pom.xml
├── readme.txt
└── src
└── main
└── filtered-resources
└── etc
└── filtering.bug.cfg
{code}
The filtering.bug.cfg file should be filtered with maven resource plugin. I
am expecting that the filtered file will get included in the karaf
distribution. I can see that target/classes/etc/filtering.bug.cfg actually
has the correct content but the karaf/etc/filtering.bug.cfg still has the
maven variables.
I'll upload the sample project as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-2742) karaf-maven-plugin can not include filtered resources in a custom distribution
[
https://issues.apache.org/jira/browse/KARAF-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149153#comment-14149153
]
Jean-Baptiste Onofré commented on KARAF-2742:
-
Documented on master:
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=fb66b3141e80157113ad9242d9884b274753f67f
karaf-maven-plugin can not include filtered resources in a custom distribution
--
Key: KARAF-2742
URL: https://issues.apache.org/jira/browse/KARAF-2742
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0
Environment: Fedora 20, Oracle JDK 1.7.0_51, Maven 3.0.4
Reporter: Partha Roy
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Attachments: karaf-filtering-bug.tar.gz
I am trying to build a custom Karaf distribution by following
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html.
I need to add a .cfg file in the karaf/etc directory. However, the maven
resource filtering on that .cfg file does not work.
The sample project looks like:
{code}
karaf-filtering-bug
├── pom.xml
├── readme.txt
└── src
└── main
└── filtered-resources
└── etc
└── filtering.bug.cfg
{code}
The filtering.bug.cfg file should be filtered with maven resource plugin. I
am expecting that the filtered file will get included in the karaf
distribution. I can see that target/classes/etc/filtering.bug.cfg actually
has the correct content but the karaf/etc/filtering.bug.cfg still has the
maven variables.
I'll upload the sample project as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work stopped] (KARAF-3032) Multi-stage boot features function does not support over 3 stages.
[ https://issues.apache.org/jira/browse/KARAF-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-3032 stopped by Jean-Baptiste Onofré. --- Multi-stage boot features function does not support over 3 stages. -- Key: KARAF-3032 URL: https://issues.apache.org/jira/browse/KARAF-3032 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 3.0.0, 3.0.1 Reporter: Rick.Todo Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.0.0, 3.0.3 KARAF-608 Allow for multi-stage boot features installation was already fixed and multi-stage boot is supported now. But It only support 2 stage at most: BootFeaturesInstaller#parseBootFeatures will parse some format such as (obr,war),activemq,cxf,camel, and create stages. But it seems that regular expression should be (\\((.+?))\\),|.+ instead of (\\((.+))\\),|.+. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-2742) karaf-maven-plugin can not include filtered resources in a custom distribution
[
https://issues.apache.org/jira/browse/KARAF-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-2742.
-
Resolution: Fixed
karaf-maven-plugin can not include filtered resources in a custom distribution
--
Key: KARAF-2742
URL: https://issues.apache.org/jira/browse/KARAF-2742
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0
Environment: Fedora 20, Oracle JDK 1.7.0_51, Maven 3.0.4
Reporter: Partha Roy
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Attachments: karaf-filtering-bug.tar.gz
I am trying to build a custom Karaf distribution by following
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html.
I need to add a .cfg file in the karaf/etc directory. However, the maven
resource filtering on that .cfg file does not work.
The sample project looks like:
{code}
karaf-filtering-bug
├── pom.xml
├── readme.txt
└── src
└── main
└── filtered-resources
└── etc
└── filtering.bug.cfg
{code}
The filtering.bug.cfg file should be filtered with maven resource plugin. I
am expecting that the filtered file will get included in the karaf
distribution. I can see that target/classes/etc/filtering.bug.cfg actually
has the correct content but the karaf/etc/filtering.bug.cfg still has the
maven variables.
I'll upload the sample project as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3032) Multi-stage boot features function does not support over 3 stages.
[ https://issues.apache.org/jira/browse/KARAF-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3032: Fix Version/s: (was: 3.0.2) 3.0.3 Multi-stage boot features function does not support over 3 stages. -- Key: KARAF-3032 URL: https://issues.apache.org/jira/browse/KARAF-3032 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 3.0.0, 3.0.1 Reporter: Rick.Todo Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.0.0, 3.0.3 KARAF-608 Allow for multi-stage boot features installation was already fixed and multi-stage boot is supported now. But It only support 2 stage at most: BootFeaturesInstaller#parseBootFeatures will parse some format such as (obr,war),activemq,cxf,camel, and create stages. But it seems that regular expression should be (\\((.+?))\\),|.+ instead of (\\((.+))\\),|.+. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1512) enhancement: add self to generated feature in features-generate-descriptor goal
[ https://issues.apache.org/jira/browse/KARAF-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1512: Fix Version/s: (was: 3.0.3) 3.0.2 enhancement: add self to generated feature in features-generate-descriptor goal - Key: KARAF-1512 URL: https://issues.apache.org/jira/browse/KARAF-1512 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Benjamin Reed Assignee: Jean-Baptiste Onofré Priority: Trivial Attachments: KARAF-1512.patch When generating features in a pom that also creates a bundle artifact of it's own, it would be useful for that generated feature XML to include the project's bundle in the list of bundles for the purposes of publishing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-1512) enhancement: add self to generated feature in features-generate-descriptor goal
[
https://issues.apache.org/jira/browse/KARAF-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-1512.
-
Resolution: Not a Problem
Fix Version/s: (was: 3.0.2)
(was: 4.0.0)
Just use a template features XML file using the Maven data (${project.groupId},
etc).
enhancement: add self to generated feature in features-generate-descriptor
goal
-
Key: KARAF-1512
URL: https://issues.apache.org/jira/browse/KARAF-1512
Project: Karaf
Issue Type: New Feature
Components: karaf-tooling
Reporter: Benjamin Reed
Assignee: Jean-Baptiste Onofré
Priority: Trivial
Attachments: KARAF-1512.patch
When generating features in a pom that also creates a bundle artifact of it's
own, it would be useful for that generated feature XML to include the
project's bundle in the list of bundles for the purposes of publishing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-2961) When a feature is generated from a bundle project, include that bundle in the feature
[
https://issues.apache.org/jira/browse/KARAF-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-2961.
-
Resolution: Not a Problem
Fix Version/s: (was: 3.0.2)
(was: 4.0.0)
You should use a template features XML where you can use the Maven artifact
data (${project.groupId}, etc).
When a feature is generated from a bundle project, include that bundle in the
feature
-
Key: KARAF-2961
URL: https://issues.apache.org/jira/browse/KARAF-2961
Project: Karaf
Issue Type: New Feature
Components: karaf-tooling
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
We're migrating a custom plugin framework over to Karaf and would like to
both create the OSGi bundle and generate the associated Karaf feature in the
same Maven project. Otherwise downstream clients will need to create two
Maven projects for each plugin: one to create the bundle, and one to create
the Karaf feature.
The proposed change is to consider the project packaging, and if it is
bundle then include the main project artifact (ie. the bundle itself) in
the generated feature. This requires no configuration change and should not
affect anyone generating features in isolation. We could also add a new flag
such as includeProjectArtifact so this change has to be explicitly enabled,
if people prefer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2468) karaf-maven-plugin to support creation of partialbundlelists for sling launchpad
[ https://issues.apache.org/jira/browse/KARAF-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2468: Fix Version/s: (was: 3.0.2) 3.0.3 karaf-maven-plugin to support creation of partialbundlelists for sling launchpad Key: KARAF-2468 URL: https://issues.apache.org/jira/browse/KARAF-2468 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Reto Gmür Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.3 Attachments: karaf-maven-plugin.patch The sling launchpad maven plugin (http://sling.apache.org/documentation/development/maven-launchpad-plugin.html) supports the use partialbundlelists to group together related bundles. While with the sling launchpad plugin one can create both partialbundlelists and karaf features the flexibility for creating karaf features is somehow limited. So it would be great to also provide the ability in the karaf-maven-plugin to create partialbundlelist for sling. That is for users who primarily want to create a karaf features to also have the possibility to server sling launchpad using projects without having to duplicate the list of bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2961) When a feature is generated from a bundle project, include that bundle in the feature
[ https://issues.apache.org/jira/browse/KARAF-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149178#comment-14149178 ] Stuart McCulloch commented on KARAF-2961: - Seriously? We have a sizeable number of plugin-style builds and expect customers to write their own plugins. IMHO forcing them all to add copies of the same template feature file to each plugin build is unreasonable when adding support for this is trivial and doesn't affect anyone else (as it's controlled by a simple flag). If this small improvement really is never going to be accepted then we'll have to maintain our own version of the plugin because we're using template feature files at the moment as a workaround and it doesn't scale as a solution. When a feature is generated from a bundle project, include that bundle in the feature - Key: KARAF-2961 URL: https://issues.apache.org/jira/browse/KARAF-2961 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Stuart McCulloch Assignee: Jean-Baptiste Onofré We're migrating a custom plugin framework over to Karaf and would like to both create the OSGi bundle and generate the associated Karaf feature in the same Maven project. Otherwise downstream clients will need to create two Maven projects for each plugin: one to create the bundle, and one to create the Karaf feature. The proposed change is to consider the project packaging, and if it is bundle then include the main project artifact (ie. the bundle itself) in the generated feature. This requires no configuration change and should not affect anyone generating features in isolation. We could also add a new flag such as includeProjectArtifact so this change has to be explicitly enabled, if people prefer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch updated KARAF-3249:
Fix Version/s: 3.0.2
4.0.0
If this small fix to the scripts can get into 3.0.2 (and 4.0.0) that would be
great.
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Fix For: 4.0.0, 3.0.2
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-3249:
---
Assignee: Jean-Baptiste Onofré
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-3249 started by Jean-Baptiste Onofré.
---
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3249:
Fix Version/s: 2.3.9
2.4.1
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2, 2.4.1, 2.3.9
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (KARAF-3103) config:edit does not correctly handle configuration visibility for --factory calls.
[ https://issues.apache.org/jira/browse/KARAF-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-3103: --- Assignee: Jean-Baptiste Onofré (was: Guillaume Nodet) config:edit does not correctly handle configuration visibility for --factory calls. --- Key: KARAF-3103 URL: https://issues.apache.org/jira/browse/KARAF-3103 Project: Karaf Issue Type: Bug Components: karaf-config Affects Versions: 4.0.0, 3.0.2 Reporter: Richard Kaufhold Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.0, 3.0.2 Attachments: patch-ConfigRepositoryImpl-visibility.txt Original Estimate: 10m Remaining Estimate: 10m The ConfigRepositoryImpl does not specify the visibility for created factory configurations. I have tested it using my own ManagedServiceFactory: Inside of the karaf shell I executed: karaf@root() config:edit --factory de.ansii.example.hellofactory karaf@root() config:property-append prop1 value1 karaf@root() config:update The response was: 2014-07-07 15:18:45,038 | ERROR | 04-24cc6aa84094) | configadmin | 5 - org.apache.felix.configadmin - 1.6.0 | Cannot use configuration de.ansii.example.hellofactory.5b076892-5207-4913-a704-24cc6aa84094 for [org.osgi.service.cm.ManagedServiceFactory, id=90, bundle=65/mvn:de.ansii.example/hellofactory]: No visibility to configuration bound to mvn:org.apache.karaf.config/org.apache.karaf.config.core/4.0.0-SNAPSHOT In line 91 of /org.apache.karaf.config.core/src/main/java/org/apache/karaf/config/core/impl/ConfigRepositoryImpl.java the visibility is not specified which leads to the problem that the factory configuration created by config:edit --factory is not usable by factory implementations. (null is a sensible default, as in line 44) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3103) config:edit does not correctly handle configuration visibility for --factory calls.
[ https://issues.apache.org/jira/browse/KARAF-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149292#comment-14149292 ] Jean-Baptiste Onofré commented on KARAF-3103: - I gonna review the getConfiguration() call to add the null second parameter. config:edit does not correctly handle configuration visibility for --factory calls. --- Key: KARAF-3103 URL: https://issues.apache.org/jira/browse/KARAF-3103 Project: Karaf Issue Type: Bug Components: karaf-config Affects Versions: 4.0.0, 3.0.2 Reporter: Richard Kaufhold Assignee: Guillaume Nodet Priority: Blocker Fix For: 4.0.0, 3.0.2 Attachments: patch-ConfigRepositoryImpl-visibility.txt Original Estimate: 10m Remaining Estimate: 10m The ConfigRepositoryImpl does not specify the visibility for created factory configurations. I have tested it using my own ManagedServiceFactory: Inside of the karaf shell I executed: karaf@root() config:edit --factory de.ansii.example.hellofactory karaf@root() config:property-append prop1 value1 karaf@root() config:update The response was: 2014-07-07 15:18:45,038 | ERROR | 04-24cc6aa84094) | configadmin | 5 - org.apache.felix.configadmin - 1.6.0 | Cannot use configuration de.ansii.example.hellofactory.5b076892-5207-4913-a704-24cc6aa84094 for [org.osgi.service.cm.ManagedServiceFactory, id=90, bundle=65/mvn:de.ansii.example/hellofactory]: No visibility to configuration bound to mvn:org.apache.karaf.config/org.apache.karaf.config.core/4.0.0-SNAPSHOT In line 91 of /org.apache.karaf.config.core/src/main/java/org/apache/karaf/config/core/impl/ConfigRepositoryImpl.java the visibility is not specified which leads to the problem that the factory configuration created by config:edit --factory is not usable by factory implementations. (null is a sensible default, as in line 44) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149299#comment-14149299
]
Jean-Baptiste Onofré commented on KARAF-3249:
-
Fixed on karaf-3.0.x:
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=d960892e8de7eabb84c6aef4e0ff6056fd671e6c
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2, 2.4.1, 2.3.9
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149304#comment-14149304
]
Jean-Baptiste Onofré commented on KARAF-3249:
-
Fixed on master:
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=0da0a1392d8e1316cddec82c83c76aef364e3e31
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2, 2.4.1, 2.3.9
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-3249.
-
Resolution: Fixed
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3249) Error: usage: dirname path when Karaf is located under path with spaces
[
https://issues.apache.org/jira/browse/KARAF-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3249:
Fix Version/s: (was: 2.3.9)
(was: 2.4.1)
Error: usage: dirname path when Karaf is located under path with spaces
-
Key: KARAF-3249
URL: https://issues.apache.org/jira/browse/KARAF-3249
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.1
Environment: OS X
Reporter: Stuart McCulloch
Assignee: Jean-Baptiste Onofré
Fix For: 4.0.0, 3.0.2
Unpack apache-karaf-minimal 3.0.1 under a path with spaces.
Change directory to {{apache-karaf-minimal-3.0.1/bin}}
Run {{./status}} and you should see the following output:
{code}
usage: dirname path
javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:192)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:466)
at
sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:519)
at sun.management.Agent.startLocalManagementAgent(Agent.java:144)
at sun.management.Agent.startAgent(Agent.java:264)
at sun.management.Agent.startAgent(Agent.java:456)
Caused by: java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)
... 9 more
Exception thrown by the agent : javax.management.JMRuntimeException: Failed
to load MBeanServerBuilder class
org.apache.karaf.management.boot.KarafMBeanServerBuilder:
java.lang.ClassNotFoundException:
org.apache.karaf.management.boot.KarafMBeanServerBuilder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3035) Use aries transaction jdbc / jms for pooling
[ https://issues.apache.org/jira/browse/KARAF-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Graf updated KARAF-3035: - Attachment: vcs-diff5229324964302838682.patch Use aries transaction jdbc / jms for pooling Key: KARAF-3035 URL: https://issues.apache.org/jira/browse/KARAF-3035 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0 Reporter: Guillaume Nodet Attachments: vcs-diff5229324964302838682.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3035) Use aries transaction jdbc / jms for pooling
[ https://issues.apache.org/jira/browse/KARAF-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149680#comment-14149680 ] Benjamin Graf commented on KARAF-3035: -- JDBC patch for 2.3.x branch Use aries transaction jdbc / jms for pooling Key: KARAF-3035 URL: https://issues.apache.org/jira/browse/KARAF-3035 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0 Reporter: Guillaume Nodet Attachments: vcs-diff5229324964302838682.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
