[jira] [Commented] (KARAF-6448) pax-loggin-log4j2-extra in pax exam causes IllegalStateException: Resource has no uri
[
https://issues.apache.org/jira/browse/KARAF-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953476#comment-16953476
]
Amichai Rothman commented on KARAF-6448:
Thanks for the example, [~ffang] !
I ended up copying it into the system folder from an offline local repo that
contained it, during the pax exam @Config setup, the main part being:
{quote}replaceConfigurationFile("system/org/ops4j/pax/logging/pax-logging-log4j2-extra/1.11.2/pax-logging-log4j2-extra-1.11.2.jar",
log4j2extra)
{quote}
> pax-loggin-log4j2-extra in pax exam causes IllegalStateException: Resource
> has no uri
> -
>
> Key: KARAF-6448
> URL: https://issues.apache.org/jira/browse/KARAF-6448
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.7
> Environment: Kubuntu 18.04, Karaf 4.2.7, Oracle JDK 1.8.0_201
>Reporter: Amichai Rothman
>Assignee: Freeman Yue Fang
>Priority: Major
> Attachments: KARAF-6448.patch
>
>
> When adding the pax-logging-log4j2-extra/1.11.2 bundle to a pax exam karaf
> container, an IllegalStateException is thrown with the message "Resource has
> no uri" and the tests fail.
> To recreate, take the karaf-itst-example project from karaf 4.2.7, and add
> the bundle in ExampleITest.java:
> {quote}mavenBundle("org.ops4j.pax.logging", "pax-logging-log4j2-extra",
> "1.11.2"),
> {quote}
> And build+run the example.
> The test fails with the exception:
> {quote}java.lang.IllegalStateException: Resource has no uri
> at
> org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1630)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:896)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> org.apache.karaf.features.core
> [org.apache.karaf.features.internal.service.BootFeaturesInstaller] ERROR :
> Error installing boot features
> java.lang.IllegalStateException: Resource has no uri
> at
> org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1630)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:896)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
Aleksandar Vasilev created KARAF-6460: - Summary: Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat Key: KARAF-6460 URL: https://issues.apache.org/jira/browse/KARAF-6460 Project: Karaf Issue Type: New Feature Reporter: Aleksandar Vasilev Jars which have embedded jars in them and Bundle-ClassPath are not loaded properly in no OSGi environment. If I try to use such jars with /bin/shell it seems that embedded jars are not loaded in the classpath. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
[
https://issues.apache.org/jira/browse/KARAF-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953677#comment-16953677
]
Jean-Baptiste Onofré commented on KARAF-6460:
-
{{shell}} is specific to some commands/features. It has not been designed to be
used in any context. What's your use case there ?
> Create ClassLoader that recognize bundle-classpath in case of no OSGi usage
> e.g. shell/shell.bat
>
>
> Key: KARAF-6460
> URL: https://issues.apache.org/jira/browse/KARAF-6460
> Project: Karaf
> Issue Type: New Feature
>Reporter: Aleksandar Vasilev
>Priority: Major
>
> Jars which have embedded jars in them and Bundle-ClassPath are not loaded
> properly in no OSGi environment. If I try to use such jars with
> /bin/shell it seems that embedded jars are not loaded in the
> classpath.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
[ https://issues.apache.org/jira/browse/KARAF-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953681#comment-16953681 ] Jean-Baptiste Onofré commented on KARAF-6460: - As discussed on Slack, I have a better understanding of the user case: provide bundles containing Karaf shell commands with dependencies in `Bundle-ClassPath` header. > Create ClassLoader that recognize bundle-classpath in case of no OSGi usage > e.g. shell/shell.bat > > > Key: KARAF-6460 > URL: https://issues.apache.org/jira/browse/KARAF-6460 > Project: Karaf > Issue Type: New Feature >Reporter: Aleksandar Vasilev >Priority: Major > > Jars which have embedded jars in them and Bundle-ClassPath are not loaded > properly in no OSGi environment. If I try to use such jars with > /bin/shell it seems that embedded jars are not loaded in the > classpath. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
[ https://issues.apache.org/jira/browse/KARAF-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6460: Labels: offline shell (was: ) > Create ClassLoader that recognize bundle-classpath in case of no OSGi usage > e.g. shell/shell.bat > > > Key: KARAF-6460 > URL: https://issues.apache.org/jira/browse/KARAF-6460 > Project: Karaf > Issue Type: New Feature > Components: karaf >Reporter: Aleksandar Vasilev >Priority: Major > Labels: offline, shell > > Jars which have embedded jars in them and Bundle-ClassPath are not loaded > properly in no OSGi environment. If I try to use such jars with > /bin/shell it seems that embedded jars are not loaded in the > classpath. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
[ https://issues.apache.org/jira/browse/KARAF-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6460: Component/s: karaf > Create ClassLoader that recognize bundle-classpath in case of no OSGi usage > e.g. shell/shell.bat > > > Key: KARAF-6460 > URL: https://issues.apache.org/jira/browse/KARAF-6460 > Project: Karaf > Issue Type: New Feature > Components: karaf >Reporter: Aleksandar Vasilev >Priority: Major > > Jars which have embedded jars in them and Bundle-ClassPath are not loaded > properly in no OSGi environment. If I try to use such jars with > /bin/shell it seems that embedded jars are not loaded in the > classpath. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
[
https://issues.apache.org/jira/browse/KARAF-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953684#comment-16953684
]
Sascha Vogt commented on KARAF-6460:
We have a bunch of tools from our old JBoss based product which we needed to be
ported to Karaf. Some of them should also be available when the instance is
offline or cannot be started (maintenance tools like changing datasource
configs or exporting stuff from internal datastructure or providing diagnostics
information).
For now we ported them to be commands and currently those are only available
when the instance is running. We wanted to make them available in shell but the
first command Aleks looked at uses a bundle with embedded artifacts. Hence this
request (Aleks would also provide a PR if in general that is an acceptable
feature request).
We are aware that {{shell}} is NOT an OSGi environment so we know that there is
no DS / SCR / etc. stuff, but plain old service locator and only Karaf shell
"@Reference" will work.
> Create ClassLoader that recognize bundle-classpath in case of no OSGi usage
> e.g. shell/shell.bat
>
>
> Key: KARAF-6460
> URL: https://issues.apache.org/jira/browse/KARAF-6460
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Aleksandar Vasilev
>Priority: Major
> Labels: offline, shell
>
> Jars which have embedded jars in them and Bundle-ClassPath are not loaded
> properly in no OSGi environment. If I try to use such jars with
> /bin/shell it seems that embedded jars are not loaded in the
> classpath.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KARAF-6460) Create ClassLoader that recognize bundle-classpath in case of no OSGi usage e.g. shell/shell.bat
[ https://issues.apache.org/jira/browse/KARAF-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953686#comment-16953686 ] Jean-Baptiste Onofré commented on KARAF-6460: - Understood, thanks for the details. > Create ClassLoader that recognize bundle-classpath in case of no OSGi usage > e.g. shell/shell.bat > > > Key: KARAF-6460 > URL: https://issues.apache.org/jira/browse/KARAF-6460 > Project: Karaf > Issue Type: New Feature > Components: karaf >Reporter: Aleksandar Vasilev >Priority: Major > Labels: offline, shell > > Jars which have embedded jars in them and Bundle-ClassPath are not loaded > properly in no OSGi environment. If I try to use such jars with > /bin/shell it seems that embedded jars are not loaded in the > classpath. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6425) Provide a "Simple" Features Resolver
[
https://issues.apache.org/jira/browse/KARAF-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953687#comment-16953687
]
Christian Schneider commented on KARAF-6425:
I dont think this is a good idea.
If the feature resolver does not refresh bundles then its behaviour is pretty
unpredictable. Depending on the current state installation of an additional
feature could have different resolutions.
What you can look into is building a static distribution at build time. This
way you can be absolutely sure what will be deployed. Of course you then can
not install some feature afterwards.
> Provide a "Simple" Features Resolver
>
>
> Key: KARAF-6425
> URL: https://issues.apache.org/jira/browse/KARAF-6425
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0
>
>
> Currently, the "full" features resolver is super powerful but some users
> complain about some effect:
> 1. as it can cause refresh, it's not "predictable"
> 2. it's not easy to determine the features/bundles installed due to
> "underlying" caps/reqs resolution
> Even if I think it makes sense to keep the "full" resolver by default, it
> could be interesting to enable a "simple" resolver (configured via
> {{etc/org.apache.karaf.features.cfg}}) looking like what we had in Karaf 2.x:
> more straight forward, just using the content of the feature, and it's up to
> the user to provide complete features (even by hand or by a tool provided by
> Karaf).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KARAF-6459) Unknown protocol mvn when including eventadmin feature
[
https://issues.apache.org/jira/browse/KARAF-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang reassigned KARAF-6459:
---
Assignee: Freeman Yue Fang
> Unknown protocol mvn when including eventadmin feature
> --
>
> Key: KARAF-6459
> URL: https://issues.apache.org/jira/browse/KARAF-6459
> Project: Karaf
> Issue Type: Question
> Components: karaf
>Affects Versions: 4.1.7, 4.2.6
>Reporter: Timo E aus E
>Assignee: Freeman Yue Fang
>Priority: Major
>
> I'm trying to build a custom Karaf distribution based on version 4.2.6. using
> maven-plugin. I took the example from here
> [https://github.com/apache/karaf/blob/master/examples/karaf-maven-example/karaf-maven-example-assembly/pom.xml]
> and added some boot features I need.
> Distribution is build by {{mvn clean install}}, Maven 3.6.2, Oracle Java
> 1.8.0_202
> My pom.xml is
> {code}
>
> 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";>
>
> 4.0.0
> karaf-demo
> 0.0.1-SNAPSHOT
> karaf-assembly-demo
> Apache Karaf :: Examples :: Maven :: Assembly
> karaf-assembly
>
>
> org.apache.karaf.features
> framework
> 4.2.6
> kar
>
>
> org.apache.karaf.features
> standard
> 4.2.6
> features
> xml
> runtime
>
>
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.2.6
> true
>
> ${project.artifactId}
>
> standard
> bundle
> config
> diagnostic
> feature
> shell
> log
> management
> package
> shell-compat
> ssh
> system
> wrap
> http-whiteboard
> deployer
> service
> kar
> scr
> aries-blueprint
> eventadmin
>
> false
>
>
>
>
>
> {code}
> This works fine as long as I don't include {{eventadmin}}. If it is included
> running the dist by {{target/assembly/bin/karaf clean}} results in
> {code}
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.FeaturesServiceImpl]
> : Unknown protocol: mvn
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.URL.(URL.java:439)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installConfigurationFile(FeatureConfigInstaller.java:268)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installFeatureConfigs(FeatureConfigInstaller.java:155)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.installConfigs(BundleInstallSupportImpl.java:301)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installConfigs(FeaturesServiceImpl.java:1178)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:955)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unknown protocol: mvn
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
> at java.net.URL.(URL.java:622)
> ... 13 more
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.BootFeaturesInstaller]
> : Error installing boot features
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.URL
[jira] [Commented] (KARAF-6459) Unknown protocol mvn when including eventadmin feature
[
https://issues.apache.org/jira/browse/KARAF-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953761#comment-16953761
]
Freeman Yue Fang commented on KARAF-6459:
-
Hi [~timo.e.aus.e],
This is a known issue, caused by bundles refreshment after installing
eventadmin feature.
To avoid this, you need to put
{code}
org.apache.karaf.features
standard
4.2.6
features
xml
compile
{code}
in compile scope but the runtime. Also you need to put eventadmin feature into
instead of , you can take a look at
[discussion
here|http://karaf.922171.n3.nabble.com/Karaf-4-2-4-Custom-distribution-with-ActiveMQ-5-15-9-fails-during-start-td4055549.html]
to get more details
Freeman
> Unknown protocol mvn when including eventadmin feature
> --
>
> Key: KARAF-6459
> URL: https://issues.apache.org/jira/browse/KARAF-6459
> Project: Karaf
> Issue Type: Question
> Components: karaf
>Affects Versions: 4.1.7, 4.2.6
>Reporter: Timo E aus E
>Assignee: Freeman Yue Fang
>Priority: Major
>
> I'm trying to build a custom Karaf distribution based on version 4.2.6. using
> maven-plugin. I took the example from here
> [https://github.com/apache/karaf/blob/master/examples/karaf-maven-example/karaf-maven-example-assembly/pom.xml]
> and added some boot features I need.
> Distribution is build by {{mvn clean install}}, Maven 3.6.2, Oracle Java
> 1.8.0_202
> My pom.xml is
> {code}
>
> 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";>
>
> 4.0.0
> karaf-demo
> 0.0.1-SNAPSHOT
> karaf-assembly-demo
> Apache Karaf :: Examples :: Maven :: Assembly
> karaf-assembly
>
>
> org.apache.karaf.features
> framework
> 4.2.6
> kar
>
>
> org.apache.karaf.features
> standard
> 4.2.6
> features
> xml
> runtime
>
>
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.2.6
> true
>
> ${project.artifactId}
>
> standard
> bundle
> config
> diagnostic
> feature
> shell
> log
> management
> package
> shell-compat
> ssh
> system
> wrap
> http-whiteboard
> deployer
> service
> kar
> scr
> aries-blueprint
> eventadmin
>
> false
>
>
>
>
>
> {code}
> This works fine as long as I don't include {{eventadmin}}. If it is included
> running the dist by {{target/assembly/bin/karaf clean}} results in
> {code}
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.FeaturesServiceImpl]
> : Unknown protocol: mvn
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.URL.(URL.java:439)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installConfigurationFile(FeatureConfigInstaller.java:268)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installFeatureConfigs(FeatureConfigInstaller.java:155)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.installConfigs(BundleInstallSupportImpl.java:301)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installConfigs(FeaturesServiceImpl.java:1178)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:955)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(Threa
[jira] [Resolved] (KARAF-6459) Unknown protocol mvn when including eventadmin feature
[
https://issues.apache.org/jira/browse/KARAF-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang resolved KARAF-6459.
-
Resolution: Information Provided
> Unknown protocol mvn when including eventadmin feature
> --
>
> Key: KARAF-6459
> URL: https://issues.apache.org/jira/browse/KARAF-6459
> Project: Karaf
> Issue Type: Question
> Components: karaf
>Affects Versions: 4.1.7, 4.2.6
>Reporter: Timo E aus E
>Assignee: Freeman Yue Fang
>Priority: Major
>
> I'm trying to build a custom Karaf distribution based on version 4.2.6. using
> maven-plugin. I took the example from here
> [https://github.com/apache/karaf/blob/master/examples/karaf-maven-example/karaf-maven-example-assembly/pom.xml]
> and added some boot features I need.
> Distribution is build by {{mvn clean install}}, Maven 3.6.2, Oracle Java
> 1.8.0_202
> My pom.xml is
> {code}
>
> 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";>
>
> 4.0.0
> karaf-demo
> 0.0.1-SNAPSHOT
> karaf-assembly-demo
> Apache Karaf :: Examples :: Maven :: Assembly
> karaf-assembly
>
>
> org.apache.karaf.features
> framework
> 4.2.6
> kar
>
>
> org.apache.karaf.features
> standard
> 4.2.6
> features
> xml
> runtime
>
>
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.2.6
> true
>
> ${project.artifactId}
>
> standard
> bundle
> config
> diagnostic
> feature
> shell
> log
> management
> package
> shell-compat
> ssh
> system
> wrap
> http-whiteboard
> deployer
> service
> kar
> scr
> aries-blueprint
> eventadmin
>
> false
>
>
>
>
>
> {code}
> This works fine as long as I don't include {{eventadmin}}. If it is included
> running the dist by {{target/assembly/bin/karaf clean}} results in
> {code}
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.FeaturesServiceImpl]
> : Unknown protocol: mvn
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.URL.(URL.java:439)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installConfigurationFile(FeatureConfigInstaller.java:268)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installFeatureConfigs(FeatureConfigInstaller.java:155)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.installConfigs(BundleInstallSupportImpl.java:301)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installConfigs(FeaturesServiceImpl.java:1178)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:955)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unknown protocol: mvn
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
> at java.net.URL.(URL.java:622)
> ... 13 more
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.BootFeaturesInstaller]
> : Error installing boot features
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.UR
[jira] [Commented] (KARAF-6459) Unknown protocol mvn when including eventadmin feature
[
https://issues.apache.org/jira/browse/KARAF-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953799#comment-16953799
]
Timo E aus E commented on KARAF-6459:
-
Thanks you very much. Works now
> Unknown protocol mvn when including eventadmin feature
> --
>
> Key: KARAF-6459
> URL: https://issues.apache.org/jira/browse/KARAF-6459
> Project: Karaf
> Issue Type: Question
> Components: karaf
>Affects Versions: 4.1.7, 4.2.6
>Reporter: Timo E aus E
>Assignee: Freeman Yue Fang
>Priority: Major
>
> I'm trying to build a custom Karaf distribution based on version 4.2.6. using
> maven-plugin. I took the example from here
> [https://github.com/apache/karaf/blob/master/examples/karaf-maven-example/karaf-maven-example-assembly/pom.xml]
> and added some boot features I need.
> Distribution is build by {{mvn clean install}}, Maven 3.6.2, Oracle Java
> 1.8.0_202
> My pom.xml is
> {code}
>
> 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";>
>
> 4.0.0
> karaf-demo
> 0.0.1-SNAPSHOT
> karaf-assembly-demo
> Apache Karaf :: Examples :: Maven :: Assembly
> karaf-assembly
>
>
> org.apache.karaf.features
> framework
> 4.2.6
> kar
>
>
> org.apache.karaf.features
> standard
> 4.2.6
> features
> xml
> runtime
>
>
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.2.6
> true
>
> ${project.artifactId}
>
> standard
> bundle
> config
> diagnostic
> feature
> shell
> log
> management
> package
> shell-compat
> ssh
> system
> wrap
> http-whiteboard
> deployer
> service
> kar
> scr
> aries-blueprint
> eventadmin
>
> false
>
>
>
>
>
> {code}
> This works fine as long as I don't include {{eventadmin}}. If it is included
> running the dist by {{target/assembly/bin/karaf clean}} results in
> {code}
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.FeaturesServiceImpl]
> : Unknown protocol: mvn
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.URL.(URL.java:439)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installConfigurationFile(FeatureConfigInstaller.java:268)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installFeatureConfigs(FeatureConfigInstaller.java:155)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.installConfigs(BundleInstallSupportImpl.java:301)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installConfigs(FeaturesServiceImpl.java:1178)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:955)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unknown protocol: mvn
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
> at java.net.URL.(URL.java:622)
> ... 13 more
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.BootFeaturesInstaller]
> : Error installing boot features
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.ne
[jira] [Commented] (KARAF-6425) Provide a "Simple" Features Resolver
[
https://issues.apache.org/jira/browse/KARAF-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954015#comment-16954015
]
Jean-Baptiste Onofré commented on KARAF-6425:
-
[~cschneider] a refresh only happens if you later install a bundle that resolve
an optional import. If you first install the bundle and then the second one,
you won't have the refresh (as the optional import will be resolved). As I
consider the resolution should be "prepared" at build time, it's an expected
behavior.
So I disagree with you: static is one thing (and already possible), simple
resolution at runtime if another use case.
Anyway, the users will have the choice with the pluggable resolver I'm
proposing.
> Provide a "Simple" Features Resolver
>
>
> Key: KARAF-6425
> URL: https://issues.apache.org/jira/browse/KARAF-6425
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0
>
>
> Currently, the "full" features resolver is super powerful but some users
> complain about some effect:
> 1. as it can cause refresh, it's not "predictable"
> 2. it's not easy to determine the features/bundles installed due to
> "underlying" caps/reqs resolution
> Even if I think it makes sense to keep the "full" resolver by default, it
> could be interesting to enable a "simple" resolver (configured via
> {{etc/org.apache.karaf.features.cfg}}) looking like what we had in Karaf 2.x:
> more straight forward, just using the content of the feature, and it's up to
> the user to provide complete features (even by hand or by a tool provided by
> Karaf).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KARAF-6425) Provide a "Simple" Features Resolver
[
https://issues.apache.org/jira/browse/KARAF-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954032#comment-16954032
]
Christian Schneider commented on KARAF-6425:
Oh .. there is also another best practice when not using the static distro.
Install all features in one command. That allows the resolver to minimize
refreshs.
> Provide a "Simple" Features Resolver
>
>
> Key: KARAF-6425
> URL: https://issues.apache.org/jira/browse/KARAF-6425
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0
>
>
> Currently, the "full" features resolver is super powerful but some users
> complain about some effect:
> 1. as it can cause refresh, it's not "predictable"
> 2. it's not easy to determine the features/bundles installed due to
> "underlying" caps/reqs resolution
> Even if I think it makes sense to keep the "full" resolver by default, it
> could be interesting to enable a "simple" resolver (configured via
> {{etc/org.apache.karaf.features.cfg}}) looking like what we had in Karaf 2.x:
> more straight forward, just using the content of the feature, and it's up to
> the user to provide complete features (even by hand or by a tool provided by
> Karaf).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6425) Provide a "Simple" Features Resolver
[
https://issues.apache.org/jira/browse/KARAF-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954032#comment-16954032
]
Christian Schneider edited comment on KARAF-6425 at 10/17/19 7:13 PM:
--
Oh .. there is also another best practice when not using the static distro.
Install all features in one command. That allows the resolver to minimize
refreshs.
... and of course: Avoid optional imports :)
was (Author: ch...@die-schneider.net):
Oh .. there is also another best practice when not using the static distro.
Install all features in one command. That allows the resolver to minimize
refreshs.
> Provide a "Simple" Features Resolver
>
>
> Key: KARAF-6425
> URL: https://issues.apache.org/jira/browse/KARAF-6425
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0
>
>
> Currently, the "full" features resolver is super powerful but some users
> complain about some effect:
> 1. as it can cause refresh, it's not "predictable"
> 2. it's not easy to determine the features/bundles installed due to
> "underlying" caps/reqs resolution
> Even if I think it makes sense to keep the "full" resolver by default, it
> could be interesting to enable a "simple" resolver (configured via
> {{etc/org.apache.karaf.features.cfg}}) looking like what we had in Karaf 2.x:
> more straight forward, just using the content of the feature, and it's up to
> the user to provide complete features (even by hand or by a tool provided by
> Karaf).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KARAF-6459) Unknown protocol mvn when including eventadmin feature
[
https://issues.apache.org/jira/browse/KARAF-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954252#comment-16954252
]
Jean-Baptiste Onofré commented on KARAF-6459:
-
Actually, the minimum is to set {{eventadmin}} as {{startupFeature}}. See
https://github.com/apache/karaf/blob/master/assemblies/apache-karaf/pom.xml#L139
> Unknown protocol mvn when including eventadmin feature
> --
>
> Key: KARAF-6459
> URL: https://issues.apache.org/jira/browse/KARAF-6459
> Project: Karaf
> Issue Type: Question
> Components: karaf
>Affects Versions: 4.1.7, 4.2.6
>Reporter: Timo E aus E
>Assignee: Freeman Yue Fang
>Priority: Major
>
> I'm trying to build a custom Karaf distribution based on version 4.2.6. using
> maven-plugin. I took the example from here
> [https://github.com/apache/karaf/blob/master/examples/karaf-maven-example/karaf-maven-example-assembly/pom.xml]
> and added some boot features I need.
> Distribution is build by {{mvn clean install}}, Maven 3.6.2, Oracle Java
> 1.8.0_202
> My pom.xml is
> {code}
>
> 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";>
>
> 4.0.0
> karaf-demo
> 0.0.1-SNAPSHOT
> karaf-assembly-demo
> Apache Karaf :: Examples :: Maven :: Assembly
> karaf-assembly
>
>
> org.apache.karaf.features
> framework
> 4.2.6
> kar
>
>
> org.apache.karaf.features
> standard
> 4.2.6
> features
> xml
> runtime
>
>
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.2.6
> true
>
> ${project.artifactId}
>
> standard
> bundle
> config
> diagnostic
> feature
> shell
> log
> management
> package
> shell-compat
> ssh
> system
> wrap
> http-whiteboard
> deployer
> service
> kar
> scr
> aries-blueprint
> eventadmin
>
> false
>
>
>
>
>
> {code}
> This works fine as long as I don't include {{eventadmin}}. If it is included
> running the dist by {{target/assembly/bin/karaf clean}} results in
> {code}
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.FeaturesServiceImpl]
> : Unknown protocol: mvn
> java.net.MalformedURLException: Unknown protocol: mvn
> at java.net.URL.(URL.java:627)
> at java.net.URL.(URL.java:490)
> at java.net.URL.(URL.java:439)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installConfigurationFile(FeatureConfigInstaller.java:268)
> at
> org.apache.karaf.features.internal.service.FeatureConfigInstaller.installFeatureConfigs(FeatureConfigInstaller.java:155)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.installConfigs(BundleInstallSupportImpl.java:301)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installConfigs(FeaturesServiceImpl.java:1178)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:955)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unknown protocol: mvn
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
> at java.net.URL.(URL.java:622)
> ... 13 more
> org.apache.karaf.features.core[org.apache.karaf.features.internal.service.BootFeaturesInstaller]
> : Erro
[jira] [Created] (KARAF-6461) Upgrade to Pax JDBC 1.4.2
Jean-Baptiste Onofré created KARAF-6461: --- Summary: Upgrade to Pax JDBC 1.4.2 Key: KARAF-6461 URL: https://issues.apache.org/jira/browse/KARAF-6461 Project: Karaf Issue Type: Dependency upgrade Components: karaf Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.3.0, 4.2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6461) Upgrade to Pax JDBC 1.4.2
[ https://issues.apache.org/jira/browse/KARAF-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954265#comment-16954265 ] ASF GitHub Bot commented on KARAF-6461: --- jbonofre commented on pull request #960: [KARAF-6461] Upgrade to Pax JDBC 1.4.2 URL: https://github.com/apache/karaf/pull/960 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Pax JDBC 1.4.2 > - > > Key: KARAF-6461 > URL: https://issues.apache.org/jira/browse/KARAF-6461 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.8 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
