[jira] [Resolved] (KARAF-3888) Karaf refreshes a lot of unrelated bundles during feature installation
[
https://issues.apache.org/jira/browse/KARAF-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved KARAF-3888.
Resolution: Fixed
Karaf refreshes a lot of unrelated bundles during feature installation
--
Key: KARAF-3888
URL: https://issues.apache.org/jira/browse/KARAF-3888
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.0.0
Reporter: Ievgen Tarasov
Assignee: Christian Schneider
Fix For: 4.0.1
Attachments: karaf-refresh-problem
To reproduce the problem:
{noformat}
feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.1/xml/features
feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.15.2/xml/features
feature:repo-add
mvn:org.apache.activemq/activemq-karaf/5.11-SNAPSHOT/xml/features
feature:install activemq
feature:install activemq-client
feature:install camel
feature:install cxf
feature:install -v -t cxf-ws-policy
{noformat}
The result of the last command is in file [^karaf-refresh-problem] which is
attached to this bug. In short:
{noformat}
karaf@root() feature:install -v -t cxf-ws-policy
Adding features: cxf-ws-policy/[3.1.1,3.1.1]
No deployment change.
Bundles to refresh:
activemq-karaf/5.11.0.SNAPSHOT (Wired to
org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT which is being refreshed)
javax.mail/1.4.4 (Wired to
org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT which is being refreshed)
jline/2.12.1 (Wired to org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT
which is being refreshed)
net.sf.ehcache/2.9.0 (Wired to org.apache.aries.transaction.manager/1.0.0
which is being refreshed)
(about 90 other bundles)
karaf@root()
{noformat}
In the same time, if I slightly change the order of feature installation
(install activemq-client _before_ activemq), then the refresh doesn't happen:
{noformat}
karaf@root() feature:install -v -t cxf-ws-policy
Adding features: cxf-ws-policy/[3.1.1,3.1.1]
No deployment change.
karaf@root()
{noformat}
Note regarding AMQ vesrion - I'm using 5.11-SNAPSHOT because of a fix for
another bundle refresh problem: https://issues.apache.org/jira/browse/AMQ-5821
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3919) Upgrade to JPA 2.1.0
[ https://issues.apache.org/jira/browse/KARAF-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-3919. Resolution: Fixed Upgrade to JPA 2.1.0 Key: KARAF-3919 URL: https://issues.apache.org/jira/browse/KARAF-3919 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3924) Upgrade to transaction.blueprint 1.1.1
Christian Schneider created KARAF-3924: -- Summary: Upgrade to transaction.blueprint 1.1.1 Key: KARAF-3924 URL: https://issues.apache.org/jira/browse/KARAF-3924 Project: Karaf Issue Type: Dependency upgrade Affects Versions: 4.0.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3908) shell:new does not work for most classes
[ https://issues.apache.org/jira/browse/KARAF-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-3908. Resolution: Fixed shell:new does not work for most classes Key: KARAF-3908 URL: https://issues.apache.org/jira/browse/KARAF-3908 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.0.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.0.1 If you do shell:new for a class that is not directly known to the shell.command bundle you get a ClassNotFoundException. The reason is that the DefaultConverter is used to convert from String to Class which uses the bundle classloader. The shell.commands bundle can not know all possible classes. A workaround is the do dynamic-import org.apache.karaf.shell.commands to make all packages available to the bundle. This opens a lot of possible problems though. So I think a proper solution would be to use the capabilties to find the bundle that exports the package and use the classloader of this bundle to load the class. In case there are multiple versions of the package we could allow to specify a bundle to import the package from or allow to specify a version range for the package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3925) Release Apache Karaf 4.0.1
Jamie goodyear created KARAF-3925: - Summary: Release Apache Karaf 4.0.1 Key: KARAF-3925 URL: https://issues.apache.org/jira/browse/KARAF-3925 Project: Karaf Issue Type: Task Reporter: Jamie goodyear Assignee: Jamie goodyear Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3924) Upgrade to transaction.blueprint 1.1.1
[ https://issues.apache.org/jira/browse/KARAF-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-3924. Resolution: Fixed Upgrade to transaction.blueprint 1.1.1 -- Key: KARAF-3924 URL: https://issues.apache.org/jira/browse/KARAF-3924 Project: Karaf Issue Type: Dependency upgrade Affects Versions: 4.0.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3925) Release Apache Karaf 4.0.1
[ https://issues.apache.org/jira/browse/KARAF-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682024#comment-14682024 ] Jean-Baptiste Onofré commented on KARAF-3925: - I think it would make sense to fix the ssh issue and cleanup transaction connector features for 4.0.1 release. I'm trying to do it tonight. If I can't, I will send an update on the mailing list to postpone the release a bit. Release Apache Karaf 4.0.1 -- Key: KARAF-3925 URL: https://issues.apache.org/jira/browse/KARAF-3925 Project: Karaf Issue Type: Task Reporter: Jamie goodyear Assignee: Jamie goodyear Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-3927) karaf-maven-plugin:assembly goal should chmod bin shell scripts a+x
Hiram Chirino created KARAF-3927: Summary: karaf-maven-plugin:assembly goal should chmod bin shell scripts a+x Key: KARAF-3927 URL: https://issues.apache.org/jira/browse/KARAF-3927 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Hiram Chirino Assignee: Hiram Chirino Would be nice if the produced assembly directory mirrored what unpacking the tar does which is leave the bin scripts executable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3920) Provide OpenJPA 2.4.0 feature
[ https://issues.apache.org/jira/browse/KARAF-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3920: Fix Version/s: 4.0.1 Provide OpenJPA 2.4.0 feature - Key: KARAF-3920 URL: https://issues.apache.org/jira/browse/KARAF-3920 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3928) karaf-maven-plugin:archive goal should support a pathPrefix config setting to control the prefix added to each entry in the archives that are produced.
[
https://issues.apache.org/jira/browse/KARAF-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved KARAF-3928.
--
Resolution: Fixed
Fix Version/s: 4.0.1
For example, if you want to avoid using a path prefix, add:
{code}pathPrefix./pathPrefix{code}
to the plugin's configuration section
karaf-maven-plugin:archive goal should support a pathPrefix config setting to
control the prefix added to each entry in the archives that are produced.
---
Key: KARAF-3928
URL: https://issues.apache.org/jira/browse/KARAF-3928
Project: Karaf
Issue Type: New Feature
Components: karaf-tooling
Reporter: Hiram Chirino
Assignee: Hiram Chirino
Fix For: 4.0.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3928) karaf-maven-plugin:archive goal should support a pathPrefix config setting to control the prefix added to each entry in the archives that are produced.
Hiram Chirino created KARAF-3928: Summary: karaf-maven-plugin:archive goal should support a pathPrefix config setting to control the prefix added to each entry in the archives that are produced. Key: KARAF-3928 URL: https://issues.apache.org/jira/browse/KARAF-3928 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Hiram Chirino Assignee: Hiram Chirino -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-3922) Upgrade to jline 2.13
[ https://issues.apache.org/jira/browse/KARAF-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened KARAF-3922: - Upgrade to jline 2.13 - Key: KARAF-3922 URL: https://issues.apache.org/jira/browse/KARAF-3922 Project: Karaf Issue Type: Dependency upgrade Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.1 Even if jline 2.13 contains an issue about SSH console (I have to figure out a possible workaround directly in Karaf), this release brings fixes, especially around dynamic import. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3913) Provide Spring 4.2.0.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3913: Fix Version/s: 3.0.5 Provide Spring 4.2.0.RELEASE feature Key: KARAF-3913 URL: https://issues.apache.org/jira/browse/KARAF-3913 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.5, 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3913) Provide Spring 4.2.0.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682352#comment-14682352 ] Jean-Baptiste Onofré commented on KARAF-3913: - Fixed on karaf-3.0.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=25045b3674a8c1d984cbac6cd1fb3ec0fbc2c653 https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=a71b54f15e24dc7dab73e8c9203d9ee418df3b64 Provide Spring 4.2.0.RELEASE feature Key: KARAF-3913 URL: https://issues.apache.org/jira/browse/KARAF-3913 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.5, 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3913) Provide Spring 4.2.0.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-3913. - Resolution: Fixed Provide Spring 4.2.0.RELEASE feature Key: KARAF-3913 URL: https://issues.apache.org/jira/browse/KARAF-3913 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.5, 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-3911) bin/client and ssh doesn't work in interactive mode (can't type only one character)
[
https://issues.apache.org/jira/browse/KARAF-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680174#comment-14680174
]
Jean-Baptiste Onofré edited comment on KARAF-3911 at 8/11/15 7:37 PM:
--
The following jline commit is the cause of the problem:
{code}
commit 3b0c474af7b46245109487083f1c0a0fd053165e
Author: Guillaume Nodet gno...@apache.org
Date: Fri Jul 24 01:04:21 2015 +0200
Support for infocmp capabilities.
Rewrite the display of readLine() to leverage those capabilities instead of
harcoding some stuff.
{code}
I'm looking for a workaround in Karaf.
was (Author: jbonofre):
The following jline commit is the cause of the problem:
{code}
commit 3b0c474af7b46245109487083f1c0a0fd053165e
Author: Guillaume Nodet gno...@apache.org
Date: Fri Jul 24 01:04:21 2015 +0200
Support for infocmp capabilities.
Rewrite the display of readLine() to leverage those capabilities instead of
harcoding some stuff.
{code}
I'm fixing it.
bin/client and ssh doesn't work in interactive mode (can't type only one
character)
---
Key: KARAF-3911
URL: https://issues.apache.org/jira/browse/KARAF-3911
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.0.1
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Priority: Blocker
When connecting to a running instance (4.0.1-SNAPSHOT) using ssh client or
bin/client, it's possible only to type one character.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3911) bin/client and ssh doesn't work in interactive mode (can't type only one character)
[ https://issues.apache.org/jira/browse/KARAF-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682359#comment-14682359 ] Jean-Baptiste Onofré commented on KARAF-3911: - Something interesting is if I update to jline 2.13 on Karaf 3.0.5-SNAPSHOT, it works fine on ssh. So, I'm pretty sure, I can find a workaround on Karaf 4.x ;) bin/client and ssh doesn't work in interactive mode (can't type only one character) --- Key: KARAF-3911 URL: https://issues.apache.org/jira/browse/KARAF-3911 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.0.1 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Priority: Blocker When connecting to a running instance (4.0.1-SNAPSHOT) using ssh client or bin/client, it's possible only to type one character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3913) Provide Spring 4.2.0.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682334#comment-14682334 ] Jean-Baptiste Onofré commented on KARAF-3913: - Fixed on master: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=60a29b3cd854ac0fd3e4e868038955a7472532cc Provide Spring 4.2.0.RELEASE feature Key: KARAF-3913 URL: https://issues.apache.org/jira/browse/KARAF-3913 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3913) Provide Spring 4.2.0.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3913: Fix Version/s: 4.0.1 Provide Spring 4.2.0.RELEASE feature Key: KARAF-3913 URL: https://issues.apache.org/jira/browse/KARAF-3913 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3922) Upgrade to jline 2.13
[ https://issues.apache.org/jira/browse/KARAF-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3922: Fix Version/s: 3.0.5 Upgrade to jline 2.13 - Key: KARAF-3922 URL: https://issues.apache.org/jira/browse/KARAF-3922 Project: Karaf Issue Type: Dependency upgrade Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.5, 4.0.1 Even if jline 2.13 contains an issue about SSH console (I have to figure out a possible workaround directly in Karaf), this release brings fixes, especially around dynamic import. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3922) Upgrade to jline 2.13
[ https://issues.apache.org/jira/browse/KARAF-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682364#comment-14682364 ] Jean-Baptiste Onofré commented on KARAF-3922: - Fixed on karaf-3.0.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=f4997c240d71cc560d6e9dbb7af22f83303906ac Upgrade to jline 2.13 - Key: KARAF-3922 URL: https://issues.apache.org/jira/browse/KARAF-3922 Project: Karaf Issue Type: Dependency upgrade Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.5, 4.0.1 Even if jline 2.13 contains an issue about SSH console (I have to figure out a possible workaround directly in Karaf), this release brings fixes, especially around dynamic import. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3922) Upgrade to jline 2.13
[ https://issues.apache.org/jira/browse/KARAF-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-3922. - Resolution: Fixed Upgrade to jline 2.13 - Key: KARAF-3922 URL: https://issues.apache.org/jira/browse/KARAF-3922 Project: Karaf Issue Type: Dependency upgrade Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.5, 4.0.1 Even if jline 2.13 contains an issue about SSH console (I have to figure out a possible workaround directly in Karaf), this release brings fixes, especially around dynamic import. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3909) Starting the osgi feature using the org.ops4j.pax.web.cfg does not work as expected.
[
https://issues.apache.org/jira/browse/KARAF-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Patel updated KARAF-3909:
--
Description:
When we install the osgi feature using the org.ops4j.pax.web.cfg. we are
getting below exception but when we try to install the same feature though
Karaf command prompt it works fine. Let me know what we are missing. we will
provide you more info if you need.
Note:If we install and uninstall the feature it works fine. it does work on
first installation and we using also groovy and java code.
It is bloker for us because we deploy the application on multiple nodes and we
don't want to install the feature using the Karaf command prompt. Our
production node does not have internet access.
custom feature file.
==
feature name='service-war' version='0.0.1-SNAPSHOT' description=service-war
featurespring-ajsc/feature
featuredme2-jars/feature
featureatt-camel-jars/feature
featurecamel-cxf-2.15.2/feature
featurecamel-2.15.2/feature
featurewar/feature
bundlefile:${ajsc.repo.dir}/ajsc-jars/ajscwar/${project.version}/ajscwar-${project.version}.war/bundle
/feature
ERROR
===
01.359 [pool-4-thread-1] ERROR
org.springframework.web.servlet.DispatcherServlet - Context initialization
failed
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1
in XML document from ServletContext resource [/WEB-INF/spring-servlet.xml] is
invalid; nested exception is org.xml.sax.SAXParseException; systemId:
http://cso.att.com/FAQs/URLFiltering/ProxyWarning.html; lineNumber: 1;
columnNumber: 63; White spaces are required between publicId and systemId.
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader
was:
When we install the osgi feature using the org.ops4j.pax.web.cfg. we are
getting below exception but when we try to install the same feature though
Karaf command prompt it works fine. Let me know what we are missing. we will
provide you more info if you need.
Note:If install and uninstall the feature it works fine.
It is bloker for us because we deploy the application on multiple nodes and we
don't want to install the feature using the Karaf command prompt. Our
production node does not have internet access.
custom feature file.
==
feature name='service-war' version='0.0.1-SNAPSHOT' description=service-war
featurespring-ajsc/feature
featuredme2-jars/feature
featureatt-camel-jars/feature
featurecamel-cxf-2.15.2/feature
featurecamel-2.15.2/feature
featurewar/feature
bundlefile:${ajsc.repo.dir}/ajsc-jars/ajscwar/${project.version}/ajscwar-${project.version}.war/bundle
/feature
ERROR
===
01.359 [pool-4-thread-1] ERROR
org.springframework.web.servlet.DispatcherServlet - Context initialization
failed
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1
in XML document from ServletContext resource [/WEB-INF/spring-servlet.xml] is
invalid; nested exception is org.xml.sax.SAXParseException; systemId:
http://cso.att.com/FAQs/URLFiltering/ProxyWarning.html; lineNumber: 1;
columnNumber: 63; White spaces are required between publicId and systemId.
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader
Starting the osgi feature using the org.ops4j.pax.web.cfg does not work as
expected.
Key: KARAF-3909
URL: https://issues.apache.org/jira/browse/KARAF-3909
Project: Karaf
Issue Type: Bug
[jira] [Resolved] (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é resolved KARAF-2468. - Resolution: Not A Problem 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é Attachments: karaf-maven-plugin.patch The sling launchpad maven plugin (http://sling.apache.org/documentation/development/maven-launchpad-plugin.html) supports the use partialbundlelists to group together related bundles. While with the sling launchpad plugin one can create both partialbundlelists and karaf features the flexibility for creating karaf features is somehow limited. So it would be great to also provide the ability in the karaf-maven-plugin to create partialbundlelist for sling. That is for users who primarily want to create a karaf features to also have the possibility to server sling launchpad using projects without having to duplicate the list of bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-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: 4.0.1) (was: 3.0.5) karaf-maven-plugin to support creation of partialbundlelists for sling launchpad Key: KARAF-2468 URL: https://issues.apache.org/jira/browse/KARAF-2468 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Reto Gmür Assignee: Jean-Baptiste Onofré Attachments: karaf-maven-plugin.patch The sling launchpad maven plugin (http://sling.apache.org/documentation/development/maven-launchpad-plugin.html) supports the use partialbundlelists to group together related bundles. While with the sling launchpad plugin one can create both partialbundlelists and karaf features the flexibility for creating karaf features is somehow limited. So it would be great to also provide the ability in the karaf-maven-plugin to create partialbundlelist for sling. That is for users who primarily want to create a karaf features to also have the possibility to server sling launchpad using projects without having to duplicate the list of bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2508) make osgi:find-class a more useful command
[ https://issues.apache.org/jira/browse/KARAF-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2508: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) make osgi:find-class a more useful command -- Key: KARAF-2508 URL: https://issues.apache.org/jira/browse/KARAF-2508 Project: Karaf Issue Type: Improvement Components: karaf-shell Affects Versions: 2.3.3 Reporter: Amichai Rothman Priority: Minor I recently had to track down which bundle contains a certain class, and found the find-class command wanting. A few simple improvements would make it much more useful: 1. Add an --exact/-e option which doesn't automatically add asterisks at both ends of the string. In my case I was looking for the javax.jms.Connection class, and since the search is only on the last part of the name, this returned all classes in all packages which have the word Connection in their name, which added up to hundreds of results. with --exact I could look for what I want exactly, or choose to add asterisks at one or both ends explicitly in the search string if I wanted to. 2. Add a --local/-l option which adds BundleWiring.LISTRESOURCES_LOCAL to the listResources method call bitmask. With the current implementation, it returns both bundles containing the given class name and classes that import it from other bundles, which is useful in some cases. But with the --local option it could show only the bundles that actually contain the class (whether exported or not, unlike the exports command), which is far more useful in tracking down some classloading issues. 3. Add the bundle ID (at least) on the beginning of every printed line. This makes it amenable to grepping (without it a grep loses all bundle information, which is the whole point of using this command). 4. As a somewhat more complex alternative to #3, it would be nice if you could specify a fully qualified class name and not only the last part of the name. The command can split the search string around periods, pass the last part to listResources, then internally grep/match the full name. That would make it truly flexible in finding classes. Asterisks would have to be treated accordingly. I think adding these options (#1-#3 are trivial implementations), or at least some of them, would make the command extremely useful when performing classloading diagnosis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files - via ${ENV.foo}?
[
https://issues.apache.org/jira/browse/KARAF-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2466:
Fix Version/s: (was: 2.4.4)
(was: 4.0.1)
(was: 3.0.5)
make it easy to access environment variables inside karaf configuration
properties files - via ${ENV.foo}?
--
Key: KARAF-2466
URL: https://issues.apache.org/jira/browse/KARAF-2466
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Reporter: james strachan
Assignee: Jean-Baptiste Onofré
when using karaf in clouds PaaS infrastructures like OpenShift, Docker,
OpenStack et al; its common to use environment variables to pass in
environment specific values; then keep a single disk image. It would be nice
if there was an easy way to reference environment variables similar to the
${foo.bar} syntax for accessing system properties.
Maybe karaf should support some kind of environment variable expansion like
{code}
# define a property based on an env var
foo = ${ENV.nameOfEnvVar}
# e.g. here's the host name
host = ${ENV.HOSTNAME}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2266) Warn and override when feature can not install files
[ https://issues.apache.org/jira/browse/KARAF-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2266: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Warn and override when feature can not install files Key: KARAF-2266 URL: https://issues.apache.org/jira/browse/KARAF-2266 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 3.0.0.RC1 Reporter: Christian Schneider Assignee: Jean-Baptiste Onofré karaf can deploy files like config files during the installation of a feature. If the file is already present then it is not overwritten. I wonder if we should print a warning in this case. One use case for this is a new version of a feature that adds a new needed property to a config file. If the old feature was already present then the old config will be present and the user may also have done changes. So there might be cases where a feature works if it can install its default configs but does not work when they are already present but invalid. So we could write for each file that is already present: Warning: file path to be deployed is already present and will not be changed. We could also provide an option in feature:install like -f that forces all files to be overwritten if someone wants to make sure the feature installation should use the defaults. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2266) Warn and override when feature can not install files
[ https://issues.apache.org/jira/browse/KARAF-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2266: Assignee: (was: Jean-Baptiste Onofré) Warn and override when feature can not install files Key: KARAF-2266 URL: https://issues.apache.org/jira/browse/KARAF-2266 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 3.0.0.RC1 Reporter: Christian Schneider karaf can deploy files like config files during the installation of a feature. If the file is already present then it is not overwritten. I wonder if we should print a warning in this case. One use case for this is a new version of a feature that adds a new needed property to a config file. If the old feature was already present then the old config will be present and the user may also have done changes. So there might be cases where a feature works if it can install its default configs but does not work when they are already present but invalid. So we could write for each file that is already present: Warning: file path to be deployed is already present and will not be changed. We could also provide an option in feature:install like -f that forces all files to be overwritten if someone wants to make sure the feature installation should use the defaults. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2613) Add group/role supports in LDAPLoginModule and JDBCLoginModule
[ https://issues.apache.org/jira/browse/KARAF-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2613: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add group/role supports in LDAPLoginModule and JDBCLoginModule -- Key: KARAF-2613 URL: https://issues.apache.org/jira/browse/KARAF-2613 Project: Karaf Issue Type: Bug Components: karaf-security Reporter: Jean-Baptiste Onofré Currently, on the PropertiesLoginModule fully supports users groups. The other login modules (JDBCLoginModule and LDAPLoginModule) only supports roles. As now, Karaf uses roles in OSGi services, commands, and JMX MBeans ACL definition, it makes sense to support roles and groups in all login modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2508) make osgi:find-class a more useful command
[ https://issues.apache.org/jira/browse/KARAF-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2508: Assignee: (was: Jean-Baptiste Onofré) make osgi:find-class a more useful command -- Key: KARAF-2508 URL: https://issues.apache.org/jira/browse/KARAF-2508 Project: Karaf Issue Type: Improvement Components: karaf-shell Affects Versions: 2.3.3 Reporter: Amichai Rothman Priority: Minor I recently had to track down which bundle contains a certain class, and found the find-class command wanting. A few simple improvements would make it much more useful: 1. Add an --exact/-e option which doesn't automatically add asterisks at both ends of the string. In my case I was looking for the javax.jms.Connection class, and since the search is only on the last part of the name, this returned all classes in all packages which have the word Connection in their name, which added up to hundreds of results. with --exact I could look for what I want exactly, or choose to add asterisks at one or both ends explicitly in the search string if I wanted to. 2. Add a --local/-l option which adds BundleWiring.LISTRESOURCES_LOCAL to the listResources method call bitmask. With the current implementation, it returns both bundles containing the given class name and classes that import it from other bundles, which is useful in some cases. But with the --local option it could show only the bundles that actually contain the class (whether exported or not, unlike the exports command), which is far more useful in tracking down some classloading issues. 3. Add the bundle ID (at least) on the beginning of every printed line. This makes it amenable to grepping (without it a grep loses all bundle information, which is the whole point of using this command). 4. As a somewhat more complex alternative to #3, it would be nice if you could specify a fully qualified class name and not only the last part of the name. The command can split the search string around periods, pass the last part to listResources, then internally grep/match the full name. That would make it truly flexible in finding classes. Asterisks would have to be treated accordingly. I think adding these options (#1-#3 are trivial implementations), or at least some of them, would make the command extremely useful when performing classloading diagnosis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2538) Per user command history
[ https://issues.apache.org/jira/browse/KARAF-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2538: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Per user command history Key: KARAF-2538 URL: https://issues.apache.org/jira/browse/KARAF-2538 Project: Karaf Issue Type: Improvement Components: karaf-shell Reporter: Jonathan Anstey As mentioned in KARAF-2503, it would be nice to have command history per user. This is what folks used to a shell environment would expect I think. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2495) reverse lookup of feature by bundle
[ https://issues.apache.org/jira/browse/KARAF-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2495: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) reverse lookup of feature by bundle --- Key: KARAF-2495 URL: https://issues.apache.org/jira/browse/KARAF-2495 Project: Karaf Issue Type: New Feature Components: karaf-shell Affects Versions: 2.3.2 Reporter: Jason Reilly Assignee: Jean-Baptiste Onofré Priority: Minor Lookup feature from bundle information. Where did a particular bundle come from? Similar to how features:info feature lists the bundles, but the reverse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3344) Unable to define war as part of the feature
[
https://issues.apache.org/jira/browse/KARAF-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3344:
Fix Version/s: (was: 4.0.1)
(was: 3.0.5)
Unable to define war as part of the feature
---
Key: KARAF-3344
URL: https://issues.apache.org/jira/browse/KARAF-3344
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.2
Environment: Windows 7 64
Reporter: Maciej Mraczek
Assignee: Jean-Baptiste Onofré
Labels: feature, war
I'm trying to deploy WAR as part of Karaf startup feature inside my Karaf
custom distribution.
WAR definition inside feature tag in feature.xml:
{quote}
bundle
start-level=83webbundle:mvn:org.karaf.abc/angular-frontend/$\{project.version\}/war?Web-ContextPath=/angular-frontend/bundle
{quote}
Maven error:
{quote}
\[ERROR\] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:3.0.2:install-kars
(default-install-kars) on project abc-distribution: Can not install abc-full
feature: Couldn't resolve artifact
org.karaf.abc:angular-frontend:war?Web-ContextPath=:angular-frontend:1.0-SNAPSHOT:
Could not find artifact
org.karaf.abc:angular-frontend:war?Web-ContextPath=:angular-frontend:1.0-SNAPSHOT
- \[Help 1\]
{quote}
The error is also reproduced when using karaf-maven-plugin 4.0.0.M1
The custom distribution with WAR can be created using Karaf 2.x
The WAR artifact can be installed inside Karaf by bundle:install -s without
any problems.
It looks like install-kars goal does not ignore install parameters after ?
sign.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3324) Document prod/dev mode of etc/org.ops4j.pax.url.mvn.cfg file
[ https://issues.apache.org/jira/browse/KARAF-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3324: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Document prod/dev mode of etc/org.ops4j.pax.url.mvn.cfg file Key: KARAF-3324 URL: https://issues.apache.org/jira/browse/KARAF-3324 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-documentation Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré http://karaf.922171.n3.nabble.com/Best-practice-question-development-cycle-for-a-bundle-td4036017.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3334) Change Karaf to (from) dev mode
[ https://issues.apache.org/jira/browse/KARAF-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3334: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Change Karaf to (from) dev mode --- Key: KARAF-3334 URL: https://issues.apache.org/jira/browse/KARAF-3334 Project: Karaf Issue Type: Improvement Affects Versions: 3.0.2 Reporter: Jean-Philippe CLEMENT Assignee: Jean-Baptiste Onofré Karaf assembly plugin creates a configuration which first looks for artifacts from its internal repository. A side effect is that assembled bundles would not be updated from user Maven repositories. This is ennoying in dev phase where updating bundles is a daily job :) Two solutions can be done. Either change the configuration (3 lines must be modified), or remove bundles from the system sub-directory. At present time we are using the second solution as it is more simple. We would suggest to add a Karaf command line to go to dev mode without manually affect the configuration. PS: A simple flag inside configuration could also be welcome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3310) Upgrade to XBean 4.1
[ https://issues.apache.org/jira/browse/KARAF-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3310: Fix Version/s: (was: 4.0.1) Upgrade to XBean 4.1 Key: KARAF-3310 URL: https://issues.apache.org/jira/browse/KARAF-3310 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3278) Display warning message when trying to install an already installed bundle
[ https://issues.apache.org/jira/browse/KARAF-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3278: Assignee: (was: Jean-Baptiste Onofré) Display warning message when trying to install an already installed bundle -- Key: KARAF-3278 URL: https://issues.apache.org/jira/browse/KARAF-3278 Project: Karaf Issue Type: Improvement Components: karaf-shell Reporter: Jean-Baptiste Onofré Using bundle:install command (or install() operation on the BundleMBean) with an already installed bundle (same location or symbolic name/version) just do nothing. It would be helpful to display a warning message to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3323) Upgrade Maven dependencies (aether, plugin, etc)
[ https://issues.apache.org/jira/browse/KARAF-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3323: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Upgrade Maven dependencies (aether, plugin, etc) Key: KARAF-3323 URL: https://issues.apache.org/jira/browse/KARAF-3323 Project: Karaf Issue Type: Dependency upgrade Components: karaf-tooling Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3344) Unable to define war as part of the feature
[
https://issues.apache.org/jira/browse/KARAF-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3344:
Assignee: (was: Jean-Baptiste Onofré)
Unable to define war as part of the feature
---
Key: KARAF-3344
URL: https://issues.apache.org/jira/browse/KARAF-3344
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.2
Environment: Windows 7 64
Reporter: Maciej Mraczek
Labels: feature, war
I'm trying to deploy WAR as part of Karaf startup feature inside my Karaf
custom distribution.
WAR definition inside feature tag in feature.xml:
{quote}
bundle
start-level=83webbundle:mvn:org.karaf.abc/angular-frontend/$\{project.version\}/war?Web-ContextPath=/angular-frontend/bundle
{quote}
Maven error:
{quote}
\[ERROR\] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:3.0.2:install-kars
(default-install-kars) on project abc-distribution: Can not install abc-full
feature: Couldn't resolve artifact
org.karaf.abc:angular-frontend:war?Web-ContextPath=:angular-frontend:1.0-SNAPSHOT:
Could not find artifact
org.karaf.abc:angular-frontend:war?Web-ContextPath=:angular-frontend:1.0-SNAPSHOT
- \[Help 1\]
{quote}
The error is also reproduced when using karaf-maven-plugin 4.0.0.M1
The custom distribution with WAR can be created using Karaf 2.x
The WAR artifact can be installed inside Karaf by bundle:install -s without
any problems.
It looks like install-kars goal does not ignore install parameters after ?
sign.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3925) Release Apache Karaf 4.0.1
[ https://issues.apache.org/jira/browse/KARAF-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692923#comment-14692923 ] Jean-Baptiste Onofré commented on KARAF-3925: - I fixed the jline/ssh issue. So 4.0.1 is ready to go on vote. Even if it's not a blocker (critical IMHO), if someone can try to reproduce and take a look on KARAF-3893, it would be great. But I could be fixed in a 4.0.2 and should not hold the 4.0.1 release. Release Apache Karaf 4.0.1 -- Key: KARAF-3925 URL: https://issues.apache.org/jira/browse/KARAF-3925 Project: Karaf Issue Type: Task Reporter: Jamie goodyear Assignee: Jamie goodyear Fix For: 4.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-397) Allow completion of non Karaf based osgi commands
[ https://issues.apache.org/jira/browse/KARAF-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-397: --- Fix Version/s: (was: 4.0.1) Allow completion of non Karaf based osgi commands - Key: KARAF-397 URL: https://issues.apache.org/jira/browse/KARAF-397 Project: Karaf Issue Type: Improvement Components: karaf-shell Reporter: Guillaume Nodet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-222) Provide karaf:run, karaf:deploy, karaf:client Maven goals
[ https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-222: --- Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Provide karaf:run, karaf:deploy, karaf:client Maven goals - Key: KARAF-222 URL: https://issues.apache.org/jira/browse/KARAF-222 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: james strachan Assignee: Jean-Baptiste Onofré Attachments: KARAF-222-run-mojo-1.diff Did a quick google couldn't see one yet - please close if there is one already :) The really nice thing about jetty:run is it watches the source code target/classes dir auto redeploys on change, so there's no deploy step - you just hack compile (which your IDE or incremental compile can do - e.g. mvn scala:cc). For added bonus would be being able to add some extra bundles, so it can be a RAD way to hack bundles. Maybe folks could have some integration junit tests automatically rerun whenever the bundle is redeployed? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-511) When updating a bundle, completers are not always refreshed
[ https://issues.apache.org/jira/browse/KARAF-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-511: --- Fix Version/s: (was: 4.0.1) (was: 3.0.5) When updating a bundle, completers are not always refreshed --- Key: KARAF-511 URL: https://issues.apache.org/jira/browse/KARAF-511 Project: Karaf Issue Type: Bug Components: karaf-shell Reporter: Guillaume Nodet Priority: Minor The problem is that the CommandsCompleter#checkData checks for new/removed commands, but if the names are the same, completers aren't refreshed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3779) Be able to define the copied location of the kar files
[ https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3779: Affects Version/s: 3.0.4 4.0.0 2.4.3 Be able to define the copied location of the kar files -- Key: KARAF-3779 URL: https://issues.apache.org/jira/browse/KARAF-3779 Project: Karaf Issue Type: Improvement Components: karaf-kar Affects Versions: 2.3.8, 3.0.4, 4.0.0, 2.4.3 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré On Karaf 2.3.x, the kar files are copied into the system folder. It would be great to configure where Karaf copies the kar files (in the kar service blueprint xml) using a property in etc/org.apache.karaf.kar.cfg. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3770) Add support for installing libraries from the features service
[ https://issues.apache.org/jira/browse/KARAF-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3770: Fix Version/s: (was: 4.0.1) Add support for installing libraries from the features service -- Key: KARAF-3770 URL: https://issues.apache.org/jira/browse/KARAF-3770 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.0.M3 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Libraries are currently only supported by the assembly builder. CXF in particular requires quite a few libraries to work properly (those are added in the apache-karaf distribution, but not in the minimal one). Those libraries should be referenced in the CXF features instead, and the features service should support installing the libraries and restarting the framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3779) Be able to define the copied location of the kar files
[ https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3779: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) (was: 2.3.12) Be able to define the copied location of the kar files -- Key: KARAF-3779 URL: https://issues.apache.org/jira/browse/KARAF-3779 Project: Karaf Issue Type: Improvement Components: karaf-kar Affects Versions: 2.3.8, 3.0.4, 4.0.0, 2.4.3 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré On Karaf 2.3.x, the kar files are copied into the system folder. It would be great to configure where Karaf copies the kar files (in the kar service blueprint xml) using a property in etc/org.apache.karaf.kar.cfg. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1618) Exception when restarting Karaf with shutdown -r . Can not delete jansi.dll
[ https://issues.apache.org/jira/browse/KARAF-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1618: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Exception when restarting Karaf with shutdown -r . Can not delete jansi.dll --- Key: KARAF-1618 URL: https://issues.apache.org/jira/browse/KARAF-1618 Project: Karaf Issue Type: Bug Components: karaf-shell Reporter: Christian Schneider Assignee: Jean-Baptiste Onofré karaf@root() shutdown -r Confirm: reboot instance root (yes/no): karaf@root() Could not launch framework: java.io.IOException: Unable to delete file: C:\java\apache-karaf-3.0.0-SNAPSHOT\data\cache\bundle37\version0.0\bundle.jar-lib\0\META-INF\native\windows32\jansi.dll java.io.IOException: Unable to delete file: C:\java\apache-karaf-3.0.0-SNAPSHOT\data\cache\bundle37\version0.0\bundle.jar-lib\0\META-INF\native\windows32\jansi.dll at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:204) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) at org.apache.karaf.main.ConfigProperties.init(ConfigProperties.java:143) at org.apache.karaf.main.Main.launch(Main.java:212) at org.apache.karaf.main.Main.main(Main.java:169) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1886) Create transaction-jdbc and transaction-jms enterprise features
[ https://issues.apache.org/jira/browse/KARAF-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1886: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Create transaction-jdbc and transaction-jms enterprise features --- Key: KARAF-1886 URL: https://issues.apache.org/jira/browse/KARAF-1886 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Aries transaction now replaces the wrappers by jdbc and jms provider. It makes sense to let the user choose the provider installing a given feature (for JDBC or JMS). -- 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: 4.0.1)
(was: 3.0.5)
BundleException: Bundle installation rejected by hook. error when installing
from features XML file
---
Key: KARAF-1728
URL: https://issues.apache.org/jira/browse/KARAF-1728
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 3.0.0
Reporter: Hendy Irawan
Assignee: Jean-Baptiste Onofré
Console:
{code}
karaf@root() feature:install -v commerce-shell
Installing feature commerce-shell 4.0.1-SNAPSHOT
Installing feature commerce-core 4.0.1-SNAPSHOT
Installing feature oss-deps 1.0.0
Installing feature httpclient 4.2.1
Installing feature jpa 1.0.0
Installing feature xml-specs-api 1.9.0
Installing feature soluvas-framework 1.0.0-SNAPSHOT
Installing feature magja 1.0.3-SNAPSHOT
Installing feature http 3.0.0-SNAPSHOT
Installing feature apache-ldap-client 1.0.0-M12
Installing feature drools 5.4.0
Installing feature blueprints-neo4j 1.2
Installing feature neo4j 1.7.2
Installing bundle
wrap:mvn:org.neo4j/neo4j-kernel/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-kernel;=split,*
Installing bundle
wrap:mvn:org.neo4j/neo4j-lucene-index/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-lucene-index;=split,*
Installing bundle wrap:mvn:org.neo4j/neo4j-cypher/1.8.M07
Installing bundle wrap:mvn:org.neo4j/neo4j-rest-graphdb/1.7
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-core/1.2
Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-neo4j-graph/1.2
Installing bundle wrap:mvn:com.tinkerpop/frames/0.7
Installing feature soluvas-image-store 1.0.0-SNAPSHOT
Installing bundle wrap:mvn:net.coobird/thumbnailator/0.4.1
Installing bundle mvn:org.soluvas/soluvas-image-store/1.0.0-SNAPSHOT
Installing feature soluvas-ldap 1.0.0-SNAPSHOT
Installing bundle
mvn:org.apache.geronimo.specs/geronimo-validation_1.0_spec/1.1
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-common/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle
wrap:mvn:org.picketlink.idm/picketlink-idm-api/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
Installing bundle mvn:org.soluvas/soluvas-ldap/1.0.0-SNAPSHOT
Installing feature openjpa 2.2.0
Installing feature jndi 1.0.0
Found installed bundle: org.apache.aries.util [9]
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.api/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.core/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.rmi/1.0.0
Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.url/1.0.0
Installing bundle
mvn:org.apache.aries.jndi/org.apache.aries.jndi.legacy.support/1.0.0
Installing feature transaction 1.0.0
Installing bundle mvn:commons-pool/commons-pool/1.6
Error executing command: Bundle installation rejected by hook.
{code}
Log and stack trace:
{code}
2012-08-15 18:12:42,454 | INFO | Thread-6 | ShellUtil
| 40 - org.apache.karaf.shell.console - 3.0.0.SNAPSHOT | Exception
caught while executing command
org.osgi.framework.BundleException: Bundle installation rejected by hook.
at org.apache.felix.framework.Felix.installBundle(Felix.java:2872)
at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:894)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:606)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:450)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:431)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:420)
at Proxyd6c71027_7662_4a47_bbd6_ba300c8a7c7a.installFeature(Unknown
Source)
at
[jira] [Updated] (KARAF-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: 4.0.1)
(was: 3.0.5)
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é
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] [Updated] (KARAF-3809) Create assembly fails under Windows
[
https://issues.apache.org/jira/browse/KARAF-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3809:
Fix Version/s: (was: 4.0.1)
Create assembly fails under Windows
---
Key: KARAF-3809
URL: https://issues.apache.org/jira/browse/KARAF-3809
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 4.0.0
Environment: Windows 7
java version 1.7.0_65
Java(TM) SE Runtime Environment (build 1.7.0_65-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
Reporter: Andreas Kuhtz
Assignee: Jean-Baptiste Onofré
Create an assembly with the karaf-maven-plugin fails under Windows.
This is the first problem:
{code}
[ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.0.0:assembly
(process-resources) on project distribution: Unable to build assembly: Error
- [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.karaf.tooling:karaf-maven-plugin:4.0.0:assembly
(process-resources) on project distribution: Unable to build assembly
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build
assembly
at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:170)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: org.apache.karaf.features.internal.util.MultiException: Error
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.init(MavenDownloadManager.java:84)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
at
org.apache.karaf.profile.assembly.Builder.loadRepositories(Builder.java:1029)
at org.apache.karaf.profile.assembly.Builder.bootStage(Builder.java:703)
at
org.apache.karaf.profile.assembly.Builder.doGenerateAssembly(Builder.java:554)
at
org.apache.karaf.profile.assembly.Builder.generateAssembly(Builder.java:352)
at
org.apache.karaf.tooling.AssemblyMojo.doExecute(AssemblyMojo.java:296)
at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:164)
... 21 more
Suppressed: java.nio.file.InvalidPathException: Illegal char : at
index 4: file:/D:/svn/some of my
directories/distribution/target/assembly/system/org/apache/karaf/features/framework/4.0.0/framework-4.0.0-features.xml
at
sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
at
sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
at
sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
at
[jira] [Updated] (KARAF-3789) Be able to define the instances storage location
[ https://issues.apache.org/jira/browse/KARAF-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3789: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) (was: 2.3.12) Be able to define the instances storage location Key: KARAF-3789 URL: https://issues.apache.org/jira/browse/KARAF-3789 Project: Karaf Issue Type: Improvement Components: karaf-instance Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré The users should have the ability to change the location of the instances folder. Right now, it's based on the KARAF_BASE. Adding etc/org.apache.karaf.instances.cfg configuration containing storage property where users can provide their folder would be helpful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3809) Create assembly fails under Windows
[
https://issues.apache.org/jira/browse/KARAF-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3809:
Assignee: (was: Jean-Baptiste Onofré)
Create assembly fails under Windows
---
Key: KARAF-3809
URL: https://issues.apache.org/jira/browse/KARAF-3809
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 4.0.0
Environment: Windows 7
java version 1.7.0_65
Java(TM) SE Runtime Environment (build 1.7.0_65-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
Reporter: Andreas Kuhtz
Create an assembly with the karaf-maven-plugin fails under Windows.
This is the first problem:
{code}
[ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.0.0:assembly
(process-resources) on project distribution: Unable to build assembly: Error
- [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.karaf.tooling:karaf-maven-plugin:4.0.0:assembly
(process-resources) on project distribution: Unable to build assembly
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build
assembly
at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:170)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: org.apache.karaf.features.internal.util.MultiException: Error
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.init(MavenDownloadManager.java:84)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
at
org.apache.karaf.profile.assembly.Builder.loadRepositories(Builder.java:1029)
at org.apache.karaf.profile.assembly.Builder.bootStage(Builder.java:703)
at
org.apache.karaf.profile.assembly.Builder.doGenerateAssembly(Builder.java:554)
at
org.apache.karaf.profile.assembly.Builder.generateAssembly(Builder.java:352)
at
org.apache.karaf.tooling.AssemblyMojo.doExecute(AssemblyMojo.java:296)
at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:164)
... 21 more
Suppressed: java.nio.file.InvalidPathException: Illegal char : at
index 4: file:/D:/svn/some of my
directories/distribution/target/assembly/system/org/apache/karaf/features/framework/4.0.0/framework-4.0.0-features.xml
at
sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
at
sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
at
sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53)
[jira] [Updated] (KARAF-3789) Be able to define the instances storage location
[ https://issues.apache.org/jira/browse/KARAF-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3789: Assignee: (was: Jean-Baptiste Onofré) Be able to define the instances storage location Key: KARAF-3789 URL: https://issues.apache.org/jira/browse/KARAF-3789 Project: Karaf Issue Type: Improvement Components: karaf-instance Reporter: Jean-Baptiste Onofré The users should have the ability to change the location of the instances folder. Right now, it's based on the KARAF_BASE. Adding etc/org.apache.karaf.instances.cfg configuration containing storage property where users can provide their folder would be helpful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3779) Be able to define the copied location of the kar files
[ https://issues.apache.org/jira/browse/KARAF-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3779: Assignee: (was: Jean-Baptiste Onofré) Be able to define the copied location of the kar files -- Key: KARAF-3779 URL: https://issues.apache.org/jira/browse/KARAF-3779 Project: Karaf Issue Type: Improvement Components: karaf-kar Affects Versions: 2.3.8, 3.0.4, 4.0.0, 2.4.3 Reporter: Jean-Baptiste Onofré On Karaf 2.3.x, the kar files are copied into the system folder. It would be great to configure where Karaf copies the kar files (in the kar service blueprint xml) using a property in etc/org.apache.karaf.kar.cfg. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2684) Create tests for Hibernate and OpenJPA features
[ https://issues.apache.org/jira/browse/KARAF-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2684: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Create tests for Hibernate and OpenJPA features --- Key: KARAF-2684 URL: https://issues.apache.org/jira/browse/KARAF-2684 Project: Karaf Issue Type: Task Components: karaf-test Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré A couple of users reported issues with both OpenJPA and Hibernate features. If our itests currently test the right installation of the features, they don't actually test the right behaviour of the features. It would make sense to use Aries examples (ariestrader and blog) or our own simple examples to test the right behaviour. These examples should be part of the Karaf distribution including a section in the developers guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2784) Add -p (--persist) to the bundle:install and feature:install commands
[ https://issues.apache.org/jira/browse/KARAF-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2784: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add -p (--persist) to the bundle:install and feature:install commands - Key: KARAF-2784 URL: https://issues.apache.org/jira/browse/KARAF-2784 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré In addition of populating the bundle cache, it would be great to add a -p (--persist) option to bundle:install and feature:install commands (and corresponding operations in the MBeans). The purpose is: - to store the artifacts in the system repository (or any repository defined in etc/org.ops4j.pax.url.mvn.cfg file) - in the case of features, eventually update the featuresBoot property in etc/org.apache.karaf.features.cfg file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2630) GenerateDescriptorMojo does not resolve conflicts
[
https://issues.apache.org/jira/browse/KARAF-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2630:
Fix Version/s: (was: 4.0.1)
(was: 3.0.5)
GenerateDescriptorMojo does not resolve conflicts
-
Key: KARAF-2630
URL: https://issues.apache.org/jira/browse/KARAF-2630
Project: Karaf
Issue Type: New Feature
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Maarten Winkels
Assignee: Jean-Baptiste Onofré
Attachments: karaf-2630.patch
When a feature project has two different versions of a dependency in its
graph, both versions are included in the generated feature.xml
e.g.:
DependencyTree:
{code}...
| +- org.activiti:activiti-engine:jar:5.15-SNAPSHOT:compile
| | +- org.activiti:activiti-bpmn-converter:jar:5.15-SNAPSHOT:compile
| | | +- org.activiti:activiti-bpmn-model:jar:5.15-SNAPSHOT:compile
| | | | +- (org.apache.commons:commons-lang3:jar:3.1:compile -
omitted for duplicate)
| | | | \- (org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile
- version managed from 1.9.9; omitted for duplicate)
| | | +- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed
from 1.7.2; scope managed from compile; omitted for duplicate)
| | | +- (org.slf4j:jcl-over-slf4j:jar:1.7.2:compile - omitted for
duplicate)
| | | \- (org.apache.commons:commons-lang3:jar:3.1:compile - omitted
for duplicate)
| | +- org.apache.commons:commons-email:jar:1.2:compile
| | | +- javax.mail:mail:jar:1.4.1:provided (scope managed from
compile)
| | | | \- (javax.activation:activation:jar:1.1.1:provided - version
managed from 1.1; scope managed from compile; omitted for duplicate)
| | | \- javax.activation:activation:jar:1.1.1:provided
| | +- org.apache.commons:commons-lang3:jar:3.1:compile
| | +- org.mybatis:mybatis:jar:3.2.2:compile
| | +- (org.springframework:spring-beans:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
| | +- joda-time:joda-time:jar:2.1:compile
| | +- org.slf4j:slf4j-api:jar:1.7.5:provided
| | \- org.slf4j:jcl-over-slf4j:jar:1.7.2:compile
| | \- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed
from 1.7.2; scope managed from compile; omitted for duplicate)
| \- org.activiti:activiti-spring:jar:5.14:compile
|+- (org.activiti:activiti-engine:jar:5.14:compile - omitted for
conflict with 5.15-SNAPSHOT)
|+- (org.springframework:spring-context:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- (org.springframework:spring-jdbc:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- (org.springframework:spring-tx:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- (org.apache.commons:commons-lang3:jar:3.1:compile - omitted for
duplicate)
|+- org.springframework:spring-orm:jar:3.2.4.RELEASE:provided
(version managed from 3.1.2.RELEASE; scope managed from compile)
|| +- (aopalliance:aopalliance:jar:1.0:provided - scope managed
from compile; omitted for duplicate)
|| +- (org.springframework:spring-beans:jar:3.2.4.RELEASE:provided
- version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|| +- (org.springframework:spring-core:jar:3.2.4.RELEASE:provided -
version managed from 3.0.7.RELEASE; scope managed from compile; omitted for
duplicate)
|| +- (org.springframework:spring-jdbc:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|| \- (org.springframework:spring-tx:jar:3.2.4.RELEASE:provided -
version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
duplicate)
|+- commons-dbcp:commons-dbcp:jar:1.4:compile
|| \- commons-pool:commons-pool:jar:1.5.4:compile
|+- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed from
1.7.2; scope managed from compile; omitted for duplicate)
|\- (org.slf4j:jcl-over-slf4j:jar:1.7.2:compile - omitted for
duplicate)
...{code}
generated feature.xml:
{code}...
bundlemvn:org.activiti/activiti-engine/5.15-SNAPSHOT/bundle
bundlemvn:org.activiti/activiti-bpmn-converter/5.15-SNAPSHOT/bundle
bundlemvn:org.activiti/activiti-bpmn-model/5.15-SNAPSHOT/bundle
bundlemvn:org.apache.commons/commons-lang3/3.1/bundle
[jira] [Updated] (KARAF-2784) Add -p (--persist) to the bundle:install and feature:install commands
[ https://issues.apache.org/jira/browse/KARAF-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2784: Assignee: (was: Jean-Baptiste Onofré) Add -p (--persist) to the bundle:install and feature:install commands - Key: KARAF-2784 URL: https://issues.apache.org/jira/browse/KARAF-2784 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-feature Reporter: Jean-Baptiste Onofré In addition of populating the bundle cache, it would be great to add a -p (--persist) option to bundle:install and feature:install commands (and corresponding operations in the MBeans). The purpose is: - to store the artifacts in the system repository (or any repository defined in etc/org.ops4j.pax.url.mvn.cfg file) - in the case of features, eventually update the featuresBoot property in etc/org.apache.karaf.features.cfg file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2688) Karaf info - Add memory details about perm gen pool
[
https://issues.apache.org/jira/browse/KARAF-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2688:
Fix Version/s: (was: 2.4.4)
(was: 4.0.1)
(was: 3.0.5)
Karaf info - Add memory details about perm gen pool
---
Key: KARAF-2688
URL: https://issues.apache.org/jira/browse/KARAF-2688
Project: Karaf
Issue Type: Improvement
Components: karaf-core, karaf-shell
Affects Versions: 2.3.3
Reporter: Claus Ibsen
Assignee: Jean-Baptiste Onofré
Priority: Minor
Attachments: Screen Shot 2014-01-16 at 3.05.16 PM.png
When running the info command you get some JVM details
For memory you get
{code}
Memory
Current heap size 90,407 kbytes
Maximum heap size 521,216 kbytes
Committed heap size 106,496 kbytes
{code}
It would be good to have the perm-gen pool as well. As if you are running out
of perm gen you are fucked. The GC cannot reclaim perm gen memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2612) jaas:group-* and jaas:group-role-* commands have not effect
[
https://issues.apache.org/jira/browse/KARAF-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2612:
Fix Version/s: (was: 4.0.1)
(was: 3.0.5)
jaas:group-* and jaas:group-role-* commands have not effect
---
Key: KARAF-2612
URL: https://issues.apache.org/jira/browse/KARAF-2612
Project: Karaf
Issue Type: Bug
Components: karaf-security
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
When doing:
karaf@root() jaas:realm-manage --index 1
karaf@root() jaas:group-add karaf mygroup
karaf@root() jaas:update
the group doesn't appear with the jaas:user-list.
More over the {{etc/users.properties}} file is not updated.
Same thing when using the {{jaas:group-role-add}}.
I set fix version as 3.0.0 for now, but depending to the time frame, it may
be postponed to 3.0.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2614) Add new operations in the SecurityMBean
[
https://issues.apache.org/jira/browse/KARAF-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2614:
Fix Version/s: (was: 2.4.4)
(was: 4.0.1)
(was: 3.0.5)
Add new operations in the SecurityMBean
---
Key: KARAF-2614
URL: https://issues.apache.org/jira/browse/KARAF-2614
Project: Karaf
Issue Type: New Feature
Components: karaf-security
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
With the new RBAC and groups features that we added, we also added a MBean
where we find the canInvoke() operation to know if an user/role can perform
an operation.
This MBean object name is org.apache.karaf:type=security,area=jmx.
It would make sense to provide another area where we can administrate the
realms, users, groups, roles, as we can do with the {{jaas:*}} commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3909) Starting the osgi feature using the org.ops4j.pax.web.cfg does not work as expected.
[
https://issues.apache.org/jira/browse/KARAF-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Patel updated KARAF-3909:
--
Description:
When we install the osgi feature using the org.ops4j.pax.web.cfg. we are
getting below exception but when we try to install the same feature though
Karaf command prompt it works fine. Let me know what we are missing. we will
provide you more info if you need.
Note:If install and uninstall the feature it works fine.
It is bloker for us because we deploy the application on multiple nodes and we
don't want to install the feature using the Karaf command prompt. Our
production node does not have internet access.
custom feature file.
==
feature name='service-war' version='0.0.1-SNAPSHOT' description=service-war
featurespring-ajsc/feature
featuredme2-jars/feature
featureatt-camel-jars/feature
featurecamel-cxf-2.15.2/feature
featurecamel-2.15.2/feature
featurewar/feature
bundlefile:${ajsc.repo.dir}/ajsc-jars/ajscwar/${project.version}/ajscwar-${project.version}.war/bundle
/feature
ERROR
===
01.359 [pool-4-thread-1] ERROR
org.springframework.web.servlet.DispatcherServlet - Context initialization
failed
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1
in XML document from ServletContext resource [/WEB-INF/spring-servlet.xml] is
invalid; nested exception is org.xml.sax.SAXParseException; systemId:
http://cso.att.com/FAQs/URLFiltering/ProxyWarning.html; lineNumber: 1;
columnNumber: 63; White spaces are required between publicId and systemId.
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader
was:
When we install the osgi feature using the org.ops4j.pax.web.cfg. we are
getting below exception but when we try to install the same feature though
Karaf command prompt it works fine. Let me know what we are missing. we will
provide you more info if you need.
It is bloker for us because we deploy the application on multiple nodes and we
don't want to install the feature using the Karaf command prompt. Our
production node does not have internet access.
custom feature file.
==
feature name='service-war' version='0.0.1-SNAPSHOT' description=service-war
featurespring-ajsc/feature
featuredme2-jars/feature
featureatt-camel-jars/feature
featurecamel-cxf-2.15.2/feature
featurecamel-2.15.2/feature
featurewar/feature
bundlefile:${ajsc.repo.dir}/ajsc-jars/ajscwar/${project.version}/ajscwar-${project.version}.war/bundle
/feature
ERROR
===
01.359 [pool-4-thread-1] ERROR
org.springframework.web.servlet.DispatcherServlet - Context initialization
failed
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1
in XML document from ServletContext resource [/WEB-INF/spring-servlet.xml] is
invalid; nested exception is org.xml.sax.SAXParseException; systemId:
http://cso.att.com/FAQs/URLFiltering/ProxyWarning.html; lineNumber: 1;
columnNumber: 63; White spaces are required between publicId and systemId.
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
[org.springframework.beans:3.2.4.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader
Starting the osgi feature using the org.ops4j.pax.web.cfg does not work as
expected.
Key: KARAF-3909
URL: https://issues.apache.org/jira/browse/KARAF-3909
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.3
Reporter: Amit Patel
Priority: Blocker
When we install the osgi feature using the
[jira] [Updated] (KARAF-3725) Improve diagnosing of unresolved optional requirements
[ https://issues.apache.org/jira/browse/KARAF-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3725: Fix Version/s: (was: 4.0.1) Improve diagnosing of unresolved optional requirements -- Key: KARAF-3725 URL: https://issues.apache.org/jira/browse/KARAF-3725 Project: Karaf Issue Type: Improvement Reporter: Guillaume Nodet KARAF-3722 is a good example of the problem. Diagnosing that the optional requirement is not resolved is the first problem, then understanding why is another big problem. We need a way to inform the user when / why optional requirements are not resolved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3744) CLONE - Exception at Karaf startup
[
https://issues.apache.org/jira/browse/KARAF-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3744:
Fix Version/s: (was: 4.0.1)
CLONE - Exception at Karaf startup
--
Key: KARAF-3744
URL: https://issues.apache.org/jira/browse/KARAF-3744
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 4.0.0.M3
Reporter: Jean-Baptiste Onofré
Assignee: Guillaume Nodet
After the upgrade to Felix Framework 5.0.0, starting Karaf displays the
following exception:
{code}
java.lang.NoSuchMethodException:
org.apache.felix.framework.Logger.setLogger(java.lang.Object)
at java.lang.Class.getDeclaredMethod(Class.java:2004)
at org.apache.karaf.main.Main.launch(Main.java:255)
at org.apache.karaf.main.Main.main(Main.java:175)
{code}
I think we can delete the code (in main) dealing with Felix logger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3726) Be able to remotely access to the JNDI InitialContextFactory
[ https://issues.apache.org/jira/browse/KARAF-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3726: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) (was: 2.3.12) Be able to remotely access to the JNDI InitialContextFactory Key: KARAF-3726 URL: https://issues.apache.org/jira/browse/KARAF-3726 Project: Karaf Issue Type: Improvement Components: karaf-jndi Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Right now, the only way to use the Karaf InitialContextFactory is in a local bundle (using new InitialContextFactory()). It would be interesting to be able to remotely access to the InitialContextFactory (as we do in an JEE application server). I'm not sure if it should be directly in the Karaf JNDI service or in the Cellar JNDI wrapper. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3718) Be able to change the log level in BootstrapLogManager
[ https://issues.apache.org/jira/browse/KARAF-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3718: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Be able to change the log level in BootstrapLogManager -- Key: KARAF-3718 URL: https://issues.apache.org/jira/browse/KARAF-3718 Project: Karaf Issue Type: Improvement Components: karaf-core Affects Versions: 3.0.3 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré The Karaf Main BootstrapLogManager loads etc/org.ops4j.pax.logging.cfg file, but now, just to load the out appender file location. It would be great to try to load a property defining the log level (for instance log4j.logger.org.apache.karaf.main) to use a given log level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3911) bin/client and ssh doesn't work in interactive mode (can't type only one character)
[ https://issues.apache.org/jira/browse/KARAF-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-3911. - Resolution: Fixed bin/client and ssh doesn't work in interactive mode (can't type only one character) --- Key: KARAF-3911 URL: https://issues.apache.org/jira/browse/KARAF-3911 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.0.1 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.1 When connecting to a running instance (4.0.1-SNAPSHOT) using ssh client or bin/client, it's possible only to type one character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3911) bin/client and ssh doesn't work in interactive mode (can't type only one character)
[ https://issues.apache.org/jira/browse/KARAF-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3911: Fix Version/s: 4.0.1 bin/client and ssh doesn't work in interactive mode (can't type only one character) --- Key: KARAF-3911 URL: https://issues.apache.org/jira/browse/KARAF-3911 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.0.1 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.1 When connecting to a running instance (4.0.1-SNAPSHOT) using ssh client or bin/client, it's possible only to type one character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3911) bin/client and ssh doesn't work in interactive mode (can't type only one character)
[ https://issues.apache.org/jira/browse/KARAF-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692891#comment-14692891 ] Jean-Baptiste Onofré commented on KARAF-3911: - Workaround implemented on master: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=a4213aef6e6db8ca7cf4168cca54b089df90cc2b bin/client and ssh doesn't work in interactive mode (can't type only one character) --- Key: KARAF-3911 URL: https://issues.apache.org/jira/browse/KARAF-3911 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.0.1 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Priority: Blocker Fix For: 4.0.1 When connecting to a running instance (4.0.1-SNAPSHOT) using ssh client or bin/client, it's possible only to type one character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2843) Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features
[ https://issues.apache.org/jira/browse/KARAF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2843: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features - Key: KARAF-2843 URL: https://issues.apache.org/jira/browse/KARAF-2843 Project: Karaf Issue Type: New Feature Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2836) Be able to define multiple keys per user in etc/keys.properties
[
https://issues.apache.org/jira/browse/KARAF-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2836:
Fix Version/s: (was: 2.4.4)
(was: 4.0.1)
(was: 3.0.5)
Be able to define multiple keys per user in etc/keys.properties
---
Key: KARAF-2836
URL: https://issues.apache.org/jira/browse/KARAF-2836
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Currently, if we define multiple keys in etc/keys.properties like this:
{code}
karaf=key,admin
karaf=other,admin
{code}
only the latest one is used/loaded (for instance other here).
It would be great to be able to load multiple keys for one given user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2925) Add JMXMP support
[ https://issues.apache.org/jira/browse/KARAF-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2925: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add JMXMP support - Key: KARAF-2925 URL: https://issues.apache.org/jira/browse/KARAF-2925 Project: Karaf Issue Type: New Feature Components: karaf-core Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré In addition of our JMX RMI standard connector, it would be great to provide support for JMXMP protocol. The JMX Messaging Protocol (JMXMP) connector is a configuration of the generic connector where the transport protocol is based on TCP and the object wrapping is native Java serialization. Security is more advanced than for the RMI connector. Security is based on the Java Secure Socket Extension (JSSE), the Java Authentication and Authorization Service (JAAS), and the Simple Authentication and Security Layer (SASL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2810) Add feature installation date and a flag indicating if it's a boot feature
[ https://issues.apache.org/jira/browse/KARAF-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2810: Assignee: (was: Jean-Baptiste Onofré) Add feature installation date and a flag indicating if it's a boot feature -- Key: KARAF-2810 URL: https://issues.apache.org/jira/browse/KARAF-2810 Project: Karaf Issue Type: Improvement Components: karaf-feature Reporter: Jean-Baptiste Onofré Now, there is no way to know when a feature has been installed. And so, it's not easy to find if the feature has been installed as a boot features, or by an user. It would be great to add some metadata like the feature installation date, displayed in feature:list/feature:info commands output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2810) Add feature installation date and a flag indicating if it's a boot feature
[ https://issues.apache.org/jira/browse/KARAF-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2810: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add feature installation date and a flag indicating if it's a boot feature -- Key: KARAF-2810 URL: https://issues.apache.org/jira/browse/KARAF-2810 Project: Karaf Issue Type: Improvement Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Now, there is no way to know when a feature has been installed. And so, it's not easy to find if the feature has been installed as a boot features, or by an user. It would be great to add some metadata like the feature installation date, displayed in feature:list/feature:info commands output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3893) Unable to start offline container
[
https://issues.apache.org/jira/browse/KARAF-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3893:
Fix Version/s: (was: 4.0.1)
Unable to start offline container
-
Key: KARAF-3893
URL: https://issues.apache.org/jira/browse/KARAF-3893
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 4.0.1
Reporter: Bernhard Schuhmann
Assignee: Jean-Baptiste Onofré
Priority: Blocker
Due to a fix for KARAF-3805 a Karaf container from a 4.0.1-SNAPSHOT assembly
doesn't start if no (remote) repository is available. The container requires
to find {{org.apache.kara.profile.assembly}} and
{{org.apache.kara.diagnostic.boot}} in the system (local) repository in order
to start. These two bundles are only deployed into the {{lib/boot}} folder,
but (because of the change in
{{org.apache.karaf.profile.assembly.Builder.java}}) not placed in the system
repository.
To reproduce uncompress a vanilla distribution, disconnect from internet and
move away your local maven repository. Karaf container won't start, hangs
even before the welcome message from the shell.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3323) Upgrade Maven dependencies (aether, plugin, etc)
[ https://issues.apache.org/jira/browse/KARAF-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-3323. - Resolution: Not A Problem Already updated on master. Upgrade Maven dependencies (aether, plugin, etc) Key: KARAF-3323 URL: https://issues.apache.org/jira/browse/KARAF-3323 Project: Karaf Issue Type: Dependency upgrade Components: karaf-tooling Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3270) Add command/MBean operation to give current user and his roles
[ https://issues.apache.org/jira/browse/KARAF-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3270: Assignee: (was: Jean-Baptiste Onofré) Add command/MBean operation to give current user and his roles -- Key: KARAF-3270 URL: https://issues.apache.org/jira/browse/KARAF-3270 Project: Karaf Issue Type: New Feature Components: karaf-shell Reporter: Jean-Baptiste Onofré When logged on with an user (on the local console, ssh, MBean), it would be great to get the current username (even if we have in the prompt and in the console session), but also with current user roles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3270) Add command/MBean operation to give current user and his roles
[ https://issues.apache.org/jira/browse/KARAF-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3270: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add command/MBean operation to give current user and his roles -- Key: KARAF-3270 URL: https://issues.apache.org/jira/browse/KARAF-3270 Project: Karaf Issue Type: New Feature Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré When logged on with an user (on the local console, ssh, MBean), it would be great to get the current username (even if we have in the prompt and in the console session), but also with current user roles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3262) Being able to use ${karaf.etc} in feature configfile/ element
[
https://issues.apache.org/jira/browse/KARAF-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3262:
Assignee: (was: Jean-Baptiste Onofré)
Being able to use ${karaf.etc} in feature configfile/ element
---
Key: KARAF-3262
URL: https://issues.apache.org/jira/browse/KARAF-3262
Project: Karaf
Issue Type: Improvement
Components: karaf-feature
Reporter: Jean-Baptiste Onofré
The configfile/ element in a feature accepts a finalname attribute to
define where the configfile has to be copied.
However, finalname is relative to ${karaf.base}, whereas it should be able to
use ${karaf.etc} (and so relative to ${karaf.etc}).
In order to be backward compatible, if finalname starts with /etc/ it will be
relative to ${karaf.base}, else it will be related to ${karaf.etc}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3278) Display warning message when trying to install an already installed bundle
[ https://issues.apache.org/jira/browse/KARAF-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3278: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Display warning message when trying to install an already installed bundle -- Key: KARAF-3278 URL: https://issues.apache.org/jira/browse/KARAF-3278 Project: Karaf Issue Type: Improvement Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Using bundle:install command (or install() operation on the BundleMBean) with an already installed bundle (same location or symbolic name/version) just do nothing. It would be helpful to display a warning message to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3262) Being able to use ${karaf.etc} in feature configfile/ element
[
https://issues.apache.org/jira/browse/KARAF-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3262:
Fix Version/s: (was: 2.4.4)
(was: 4.0.1)
(was: 3.0.5)
Being able to use ${karaf.etc} in feature configfile/ element
---
Key: KARAF-3262
URL: https://issues.apache.org/jira/browse/KARAF-3262
Project: Karaf
Issue Type: Improvement
Components: karaf-feature
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
The configfile/ element in a feature accepts a finalname attribute to
define where the configfile has to be copied.
However, finalname is relative to ${karaf.base}, whereas it should be able to
use ${karaf.etc} (and so relative to ${karaf.etc}).
In order to be backward compatible, if finalname starts with /etc/ it will be
relative to ${karaf.base}, else it will be related to ${karaf.etc}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3235) Extend karaf-test jar
[ https://issues.apache.org/jira/browse/KARAF-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3235: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Extend karaf-test jar - Key: KARAF-3235 URL: https://issues.apache.org/jira/browse/KARAF-3235 Project: Karaf Issue Type: Improvement Components: karaf-test Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré End userscan easily implement itest by extending the KarafTestSupport provided in the karaf-test jar. In that case, the KarafTestSupport should provide most of the methods as public to be able to directly use executeCommand(), etc. It would simplify writing utest/itest for end users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1505) Add a -i option for bin/client and ssh:ssh command to specify a private key to use
[ https://issues.apache.org/jira/browse/KARAF-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1505: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add a -i option for bin/client and ssh:ssh command to specify a private key to use -- Key: KARAF-1505 URL: https://issues.apache.org/jira/browse/KARAF-1505 Project: Karaf Issue Type: Improvement Reporter: Guillaume Nodet bin/client and ssh:ssh by default use a fixed private key that is deployed in the karaf.ssh jar. To use public key auth in a secure way this key needs to be exchanged by the user. We should have a default location for a private key file that is used instead of the built in private key if it exists. Additionally the -i option should allow to specify a path to an alternative private key file. The default location for the privat key should be ~/.sshkaraf/id_dsa and etc/id_dsa -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1379) Provide exit alias and improve shell:logout command
[ https://issues.apache.org/jira/browse/KARAF-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1379: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Provide exit alias and improve shell:logout command --- Key: KARAF-1379 URL: https://issues.apache.org/jira/browse/KARAF-1379 Project: Karaf Issue Type: New Feature Components: karaf-shell Affects Versions: 2.2.6 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Currently, the shell:logout command allow to exit from Karaf shell. The problem is that it kills the Karaf process (shell:logout is called with CRTL-D). shell:logout should not kill the main Karaf process (the shutdown command is dedicated for that) and an exit alias to shell:logout could be interesting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1385) Be able to disable the default PropertiesLoginModule
[ https://issues.apache.org/jira/browse/KARAF-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1385: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Be able to disable the default PropertiesLoginModule Key: KARAF-1385 URL: https://issues.apache.org/jira/browse/KARAF-1385 Project: Karaf Issue Type: Improvement Components: karaf-core Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Currently, the default PropertiesLoginModule is configured in the jaas.modules bundle (in the blueprint descriptor). It means that an user can't disable this login module easily. I propose to isolate the default PropertiesLoginModule configuration in a dedicated bundle in order to be able to uninstall it easily if needed (and replaced by another config bundle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1381) Use a history file per instance when possible
[ https://issues.apache.org/jira/browse/KARAF-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1381: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Use a history file per instance when possible - Key: KARAF-1381 URL: https://issues.apache.org/jira/browse/KARAF-1381 Project: Karaf Issue Type: New Feature Components: karaf-core, karaf-shell Reporter: Jean-Baptiste Onofré Currently, all instances launched with the same system user share the same history file ($USER/.karaf/history), so we got the commands runned on another instance. A workaround is to use -Dkaraf.history property to use a history file specific to each instance. However, the user has to change the startup configuration to add this property. When the instances are clearly identified (root, foobar, other, etc), Karaf could store the history file in a dedicated location by default, for instance: $USER/.karaf/history.root $USER/.karaf/history.foobar $USER/.karaf/history.other -- 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: 4.0.1)
(was: 3.0.5)
karaf-maven-plugin ignores dependency on feature
Key: KARAF-1583
URL: https://issues.apache.org/jira/browse/KARAF-1583
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Brian Topping
Assignee: Jean-Baptiste Onofré
When a project has a dependency on a feature, the dependency should be
rendered in the features.xml generated by
{{karaf-maven-plugin:features-generate-descriptor}} as a {{repository}}
element.
I thought I added this, but it must have gotten lost in the patches and will
submit another patch after KARAF-1537 is applied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3828) Document resourceRepositories property in etc/org.apache.karaf.features.cfg
[ https://issues.apache.org/jira/browse/KARAF-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3828: Fix Version/s: (was: 4.0.1) Document resourceRepositories property in etc/org.apache.karaf.features.cfg --- Key: KARAF-3828 URL: https://issues.apache.org/jira/browse/KARAF-3828 Project: Karaf Issue Type: Improvement Components: karaf-documentation, karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré The new features resolver is able to use different resource repositories to deal with resources capabilities. Especially, it can use a Cave repository (using the Cave repository generated repository.xml). To add new resource repositories, we have to modify the resourceRepositories property in etc/org.apache.karaf.features.cfg. However, this property is not documented, and doesn't appear at least in a comment in the cfg file. I will document this and add comment in etc/org.apache.karaf.features.cfg. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3829) Add feature:* commands (and MBean operations) to manipulate resource repositories
[ https://issues.apache.org/jira/browse/KARAF-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3829: Fix Version/s: (was: 4.0.1) Add feature:* commands (and MBean operations) to manipulate resource repositories - Key: KARAF-3829 URL: https://issues.apache.org/jira/browse/KARAF-3829 Project: Karaf Issue Type: Improvement Components: karaf-feature, karaf-shell Reporter: Jean-Baptiste Onofré Karaf features resolver is now able to use different resource repositories. A resource repositories is basically a artifact repository providing all the associated metadata (requirements capabilities). Right now, the only way to manipulate the resource repositories is by editing the resourceRepositories property in etc/org.apache.karaf.features.cfg. It would be great to provide specific commands: - to list the resource repositories, add, remove a resource repositories - to list the resources (with requirements and capabilities) - in feature:install/feature:start mention the repository providing the resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3838) Document profiles
[ https://issues.apache.org/jira/browse/KARAF-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3838: Fix Version/s: (was: 4.0.1) Document profiles - Key: KARAF-3838 URL: https://issues.apache.org/jira/browse/KARAF-3838 Project: Karaf Issue Type: Task Components: karaf-documentation Reporter: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3858) Update wrapper install output for systemd based system
[ https://issues.apache.org/jira/browse/KARAF-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3858: Fix Version/s: (was: 4.0.1) Update wrapper install output for systemd based system -- Key: KARAF-3858 URL: https://issues.apache.org/jira/browse/KARAF-3858 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin
[ https://issues.apache.org/jira/browse/KARAF-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3100: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin - Key: KARAF-3100 URL: https://issues.apache.org/jira/browse/KARAF-3100 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 3.0.1 Reporter: Gareth Collins Assignee: Jean-Baptiste Onofré I have created a pull request for this here: https://github.com/apache/karaf/pull/43 As the title says, this allows karaf to be configured to output feature configurations to config file...which I believe are easier to manage. Let me know what you think. If it looks OK, would it be possible to merge soon (e.g. karaf 3.0.2 :))? The changes are very localized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3194) Add feature-generate-doc mojo
[ https://issues.apache.org/jira/browse/KARAF-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3194: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Add feature-generate-doc mojo - Key: KARAF-3194 URL: https://issues.apache.org/jira/browse/KARAF-3194 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré In order to generate a documentation on the resources containing: - the feature description - the feature transitive features - the feature bundles - the feature configs it would be great to have karaf:feature-generate-doc as we have karaf:commands-generate-doc mojo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3193) Add diag webconsole plugin
[ https://issues.apache.org/jira/browse/KARAF-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3193: Fix Version/s: (was: 2.4.4) (was: 4.0.1) (was: 3.0.5) Add diag webconsole plugin -- Key: KARAF-3193 URL: https://issues.apache.org/jira/browse/KARAF-3193 Project: Karaf Issue Type: New Feature Components: karaf-webconsole Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré The bundle:diag command (and other diag:* commands) is helpful for end user to get some details about the current bundle state. It would be helpful to provide a Diagnostic view on the Karaf WebConsole, providing the same information as in the commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2960) Optional KAR feature installation
[ https://issues.apache.org/jira/browse/KARAF-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2960: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Optional KAR feature installation - Key: KARAF-2960 URL: https://issues.apache.org/jira/browse/KARAF-2960 Project: Karaf Issue Type: Improvement Components: karaf-kar Affects Versions: 3.0.1 Reporter: Simon Watson Assignee: Jean-Baptiste Onofré Priority: Minor I find the KAR feature of Karaf very useful, and a great way to manage server deployments. I notice that when a KAR is installed (via console, or from deploy dir), that all features are automatically installed. Is it possible to only install the KAR's feature-repos and leave the features to be installed manually? This would help where we have feature A and feature B, both depending on feature C. It's easy to include all three in one features XML but we might not want both A and B installing on every server. As things stand, we have to manually uninstall the ones we don't want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3193) Add diag webconsole plugin
[ https://issues.apache.org/jira/browse/KARAF-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3193: Assignee: (was: Jean-Baptiste Onofré) Add diag webconsole plugin -- Key: KARAF-3193 URL: https://issues.apache.org/jira/browse/KARAF-3193 Project: Karaf Issue Type: New Feature Components: karaf-webconsole Reporter: Jean-Baptiste Onofré The bundle:diag command (and other diag:* commands) is helpful for end user to get some details about the current bundle state. It would be helpful to provide a Diagnostic view on the Karaf WebConsole, providing the same information as in the commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3194) Add feature-generate-doc mojo
[ https://issues.apache.org/jira/browse/KARAF-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3194: Assignee: (was: Jean-Baptiste Onofré) Add feature-generate-doc mojo - Key: KARAF-3194 URL: https://issues.apache.org/jira/browse/KARAF-3194 Project: Karaf Issue Type: New Feature Components: karaf-tooling Reporter: Jean-Baptiste Onofré In order to generate a documentation on the resources containing: - the feature description - the feature transitive features - the feature bundles - the feature configs it would be great to have karaf:feature-generate-doc as we have karaf:commands-generate-doc mojo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3160) Kar installer/deployer should use the feature install attribute
[ https://issues.apache.org/jira/browse/KARAF-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3160: Fix Version/s: (was: 4.0.1) (was: 3.0.5) Kar installer/deployer should use the feature install attribute --- Key: KARAF-3160 URL: https://issues.apache.org/jira/browse/KARAF-3160 Project: Karaf Issue Type: Improvement Components: karaf-kar Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Priority: Minor By default, when installing a kar file (by directly dropping the kar file into the deploy folder, or using kar:* commands), all features contained in the kar file will be installed by default. Karaf doesn't check the feature install attribute. The feature install attribute can contains auto indicating that this feature should be automatically installed. The kar deployer should check the feature install attribute to determine if the feature should be installed automatically or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
