[jira] Assigned: (KARAF-59) Introduce a ${karaf.data} system property to be able to easily move the data directory to a different location
[
https://issues.apache.org/jira/browse/KARAF-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-59:
-
Assignee: Jean-Baptiste Onofré
> Introduce a ${karaf.data} system property to be able to easily move the data
> directory to a different location
> --
>
> Key: KARAF-59
> URL: https://issues.apache.org/jira/browse/KARAF-59
> Project: Karaf
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
>
> The default would be:
> karaf.data = ${karaf.base}/data
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-53) Provide XML Schema for feature descriptors and support it's validation
[ https://issues.apache.org/jira/browse/KARAF-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883845#action_12883845 ] Łukasz Dywicki commented on KARAF-53: - Sure, I can provide path with validation for features core and features deployer. The maxOccurs for repositories is mistaken. > Provide XML Schema for feature descriptors and support it's validation > -- > > Key: KARAF-53 > URL: https://issues.apache.org/jira/browse/KARAF-53 > Project: Karaf > Issue Type: Improvement >Reporter: Łukasz Dywicki > > Current version of feature service does not validate structure of document. > It would be nice to add XML Schema from next reasons: > - better tooling in IDEs > - less mistakes > - semantic correctness -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-34: - Assignee: Jean-Baptiste Onofré > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883897#action_12883897 ] Jean-Baptiste Onofré commented on KARAF-34: --- The code/decode logic will be added in the ProxyLoginModule of the jaas/boot module. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-59) Introduce a ${karaf.data} system property to be able to easily move the data directory to a different location
[
https://issues.apache.org/jira/browse/KARAF-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884163#action_12884163
]
Jean-Baptiste Onofré commented on KARAF-59:
---
The files affected to add the karaf.data system property are in the main module:
- Main to add data environment variable and system property
- Utils to manage the data variable
I'm gonna dig to find the replacement of karaf.data system property in other
classes.
> Introduce a ${karaf.data} system property to be able to easily move the data
> directory to a different location
> --
>
> Key: KARAF-59
> URL: https://issues.apache.org/jira/browse/KARAF-59
> Project: Karaf
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
>
> The default would be:
> karaf.data = ${karaf.base}/data
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-59) Introduce a ${karaf.data} system property to be able to easily move the data directory to a different location
[
https://issues.apache.org/jira/browse/KARAF-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-59.
---
Fix Version/s: 2.0.0
Resolution: Fixed
Revision 960853.
> Introduce a ${karaf.data} system property to be able to easily move the data
> directory to a different location
> --
>
> Key: KARAF-59
> URL: https://issues.apache.org/jira/browse/KARAF-59
> Project: Karaf
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
> Fix For: 2.0.0
>
>
> The default would be:
> karaf.data = ${karaf.base}/data
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-5) [karaf] admin:create should support a -r, --rmi-registry-port option to allow the RMI registry port to be configured
[ https://issues.apache.org/jira/browse/KARAF-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5: Assignee: Jean-Baptiste Onofré > [karaf] admin:create should support a -r, --rmi-registry-port option to allow > the RMI registry port to be configured > - > > Key: KARAF-5 > URL: https://issues.apache.org/jira/browse/KARAF-5 > Project: Karaf > Issue Type: Bug >Reporter: Eoghan Glynn >Assignee: Jean-Baptiste Onofré > > By default the JMX/RMI serviceURL is configured for child instances with the > same RMI registry port as the root instance. > As a result, the monitoring of the child can depend on the live-ness of the > root instance, depending on the startup sequence. > For example if the child is created via "admin:create foo" in the root's > shell, but then started via the $KARAF_HOME/instances/foo/bin/start script, > the child shares the single RMI registry hosted by the root instance. > If the root instance is then stopped, the child may no longer be monitored > over JMX. Even if the root is restarted, the child still cannot be monitored > as there is no auto-reregistration. > Instead it should be possible to create a child instance with an > instance-specific RMI registry port so that its not dependent on an RMI > registry shared with another instance, e.g. "admin:create --rmi-registry-port > 1199 foo" so that rmiRegistryPort=1199 > is configured in > $KARAF_HOME/instances/foo/etc/org.apache.felix.karaf.management.cfg -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-60) Improve history support by using the !
[ https://issues.apache.org/jira/browse/KARAF-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-60: - Assignee: Jean-Baptiste Onofré > Improve history support by using the ! > --- > > Key: KARAF-60 > URL: https://issues.apache.org/jira/browse/KARAF-60 > Project: Karaf > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > Attachments: SMX4KNL-237.patch > > > the history command is cool but it would be nice to be able to use things > like: > * !142 (run the command from the history with index 142) > * !os (run last command starting with "os") > = > See http://www.gnu.org/software/bash/manual/html_node/Event-Designators.html > = > with this patch, we can access history command list with > ! indext > ! commandPrefix > for example, history we get > 345 osgi/list > then > "! 345" or "! os" we get "osgi/list" execute again > seems we have to add a whitespace between ! and the index number or > commandPrefix, so the syntax is not exactly same as bash (which no whitespace > between ! and index number) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-179) Upgrade to felix framework 3.0.2
[ https://issues.apache.org/jira/browse/KARAF-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-179: -- Assignee: Jean-Baptiste Onofré > Upgrade to felix framework 3.0.2 > > > Key: KARAF-179 > URL: https://issues.apache.org/jira/browse/KARAF-179 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.0.0 >Reporter: Wolfgang Glas >Assignee: Jean-Baptiste Onofré > > Please upgrade to felix 3.0.2, because it fixes a rather nasty problem during > the classpath resolution of a bundle. felix-3.0.1 does not show the root > cause of aclass resolution problems, which has been fixed in felix-3.0.2. > If I have a bundle, which imports it's own package and this imported package > has a missing dependency, I have to use the debugger to find out about such > indirectly missing packages. felix-3.02 would improve this situation > dramatically show ing the whole dependency path leading up to the resolution > problem. > TIA for fixing and best regards, >Wolfgang -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-179) Upgrade to felix framework 3.0.2
[ https://issues.apache.org/jira/browse/KARAF-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-179. Resolution: Duplicate Already done by Guillaume in KARAF-168. Included in revision 989547. > Upgrade to felix framework 3.0.2 > > > Key: KARAF-179 > URL: https://issues.apache.org/jira/browse/KARAF-179 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.0.0 >Reporter: Wolfgang Glas >Assignee: Jean-Baptiste Onofré > > Please upgrade to felix 3.0.2, because it fixes a rather nasty problem during > the classpath resolution of a bundle. felix-3.0.1 does not show the root > cause of aclass resolution problems, which has been fixed in felix-3.0.2. > If I have a bundle, which imports it's own package and this imported package > has a missing dependency, I have to use the debugger to find out about such > indirectly missing packages. felix-3.02 would improve this situation > dramatically show ing the whole dependency path leading up to the resolution > problem. > TIA for fixing and best regards, >Wolfgang -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904585#action_12904585 ] Jean-Baptiste Onofré commented on KARAF-34: --- @Charles, thanks, it looks good to me. @Guillaume, agree, it's more elegant to put it in the PropertiesLoginModule. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-179) Upgrade to felix framework 3.0.2
[ https://issues.apache.org/jira/browse/KARAF-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904605#action_12904605 ] Jean-Baptiste Onofré commented on KARAF-179: No problem. You can take the latest Karaf snapshot, it should include the new Felix framework version ;) > Upgrade to felix framework 3.0.2 > > > Key: KARAF-179 > URL: https://issues.apache.org/jira/browse/KARAF-179 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.0.0 >Reporter: Wolfgang Glas >Assignee: Jean-Baptiste Onofré > > Please upgrade to felix 3.0.2, because it fixes a rather nasty problem during > the classpath resolution of a bundle. felix-3.0.1 does not show the root > cause of aclass resolution problems, which has been fixed in felix-3.0.2. > If I have a bundle, which imports it's own package and this imported package > has a missing dependency, I have to use the debugger to find out about such > indirectly missing packages. felix-3.02 would improve this situation > dramatically show ing the whole dependency path leading up to the resolution > problem. > TIA for fixing and best regards, >Wolfgang -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-182) Upgrade to Aries 0.2-incubating
Upgrade to Aries 0.2-incubating --- Key: KARAF-182 URL: https://issues.apache.org/jira/browse/KARAF-182 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré As Apache Aries 0.2-incubating has been released, we can use it in Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-183) Upgrade to the latest release of ServiceMix Bundle
[ https://issues.apache.org/jira/browse/KARAF-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-183. Resolution: Fixed Revision 991461. > Upgrade to the latest release of ServiceMix Bundle > -- > > Key: KARAF-183 > URL: https://issues.apache.org/jira/browse/KARAF-183 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > As a new Apache ServiceMix Bundles set has been released, we can use it in > Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-183) Upgrade to the latest release of ServiceMix Bundle
Upgrade to the latest release of ServiceMix Bundle -- Key: KARAF-183 URL: https://issues.apache.org/jira/browse/KARAF-183 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré As a new Apache ServiceMix Bundles set has been released, we can use it in Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-163) Generate Features XML should handle artifact types
[ https://issues.apache.org/jira/browse/KARAF-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-163: -- Assignee: Jean-Baptiste Onofré > Generate Features XML should handle artifact types > -- > > Key: KARAF-163 > URL: https://issues.apache.org/jira/browse/KARAF-163 > Project: Karaf > Issue Type: Improvement >Reporter: Ioannis Canellos >Assignee: Jean-Baptiste Onofré > Attachments: maven-features-patch.txt > > > The Generate Features XML does not append to the generated elements the type > of the artifact. > For jar artifact that is no problem. However, for other types (e.g. war) this > cause problems, because the generated feature cannot be installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-163) Generate Features XML should handle artifact types
[ https://issues.apache.org/jira/browse/KARAF-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-163. Resolution: Fixed Patch reviewed and commited. Revision 991463. > Generate Features XML should handle artifact types > -- > > Key: KARAF-163 > URL: https://issues.apache.org/jira/browse/KARAF-163 > Project: Karaf > Issue Type: Improvement >Reporter: Ioannis Canellos >Assignee: Jean-Baptiste Onofré > Attachments: maven-features-patch.txt > > > The Generate Features XML does not append to the generated elements the type > of the artifact. > For jar artifact that is no problem. However, for other types (e.g. war) this > cause problems, because the generated feature cannot be installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (KARAF-163) Generate Features XML should handle artifact types
[ https://issues.apache.org/jira/browse/KARAF-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened KARAF-163: Jar should be the default type to get the same current behavior. > Generate Features XML should handle artifact types > -- > > Key: KARAF-163 > URL: https://issues.apache.org/jira/browse/KARAF-163 > Project: Karaf > Issue Type: Improvement >Reporter: Ioannis Canellos >Assignee: Jean-Baptiste Onofré > Attachments: maven-features-patch.txt > > > The Generate Features XML does not append to the generated elements the type > of the artifact. > For jar artifact that is no problem. However, for other types (e.g. war) this > cause problems, because the generated feature cannot be installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-163) Generate Features XML should handle artifact types
[ https://issues.apache.org/jira/browse/KARAF-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904991#action_12904991 ] Jean-Baptiste Onofré commented on KARAF-163: To be clear, the purpose is to test if the artifact type is not jar. If it's not a jar, we include it in the URL, else, if it's a jar, we can avoid it in the URL. Like this, the URL is shorter and cleaner as majority of artifacts is jar type. > Generate Features XML should handle artifact types > -- > > Key: KARAF-163 > URL: https://issues.apache.org/jira/browse/KARAF-163 > Project: Karaf > Issue Type: Improvement >Reporter: Ioannis Canellos >Assignee: Jean-Baptiste Onofré > Attachments: maven-features-patch.txt > > > The Generate Features XML does not append to the generated elements the type > of the artifact. > For jar artifact that is no problem. However, for other types (e.g. war) this > cause problems, because the generated feature cannot be installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-182) Upgrade to Aries 0.2-incubating
[ https://issues.apache.org/jira/browse/KARAF-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-182. Fix Version/s: 2.1.0 Resolution: Fixed Revision 993130. > Upgrade to Aries 0.2-incubating > --- > > Key: KARAF-182 > URL: https://issues.apache.org/jira/browse/KARAF-182 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré > Fix For: 2.1.0 > > > As Apache Aries 0.2-incubating has been released, we can use it in Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-180) JAAS Database Login Module
[ https://issues.apache.org/jira/browse/KARAF-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906896#action_12906896 ] Jean-Baptiste Onofré commented on KARAF-180: It's a good idea Ioannis. In the same way, I created a LDAP JAAS login module for Karaf. I will commit it. > JAAS Database Login Module > -- > > Key: KARAF-180 > URL: https://issues.apache.org/jira/browse/KARAF-180 > Project: Karaf > Issue Type: New Feature >Reporter: Ioannis Canellos >Assignee: Ioannis Canellos > > I think it would be nice if karaf provided a JAAS Database Login Module. > That module could have the following properties: > * Data Source (required) passed as a filter (e.g. osgi.jndi.service.name). > * Password Retrieval Query (optional) > * Role Retrieval Query (optional) > * Digest Algorithm (optional) > Example configuration: > > className="org.apache.karaf.jaas.modules.database.DatabaseLoginModule" > flags="required"> > datasource = jdbc/somedb > passwordQuery = "SELECT PASSWORDD FROM USERS WHERE USERNAME=?" > roleQuery = "SELECT ROLE FROM ROLES WHERE USERNAME=?" > diggest = MD5 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906909#action_12906909 ] Jean-Baptiste Onofré commented on KARAF-34: --- I think that we need to consider two kinds of passwords: - the passwords used in JAAS. This kind of passwords can be one-way crypted as the user retype it. I'm fine to implement the enhancement in the KarafAbstractLoginModule. - the "resources" passwords used internally in Karaf. This kind of passwords is not related at all to JAAS. For example, we can imagine that Karaf provide a kind of cypher service to crypt/uncrypt some properties such as database connection password, RMI registry connection password, etc. We can consider the enhancement in two steps. I begin with the first one. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906944#action_12906944 ] Jean-Baptiste Onofré commented on KARAF-34: --- For now, I implement it in the PropertiesLoginModule. Implementing in the login() method of the AbstractKarafLoginModule can be interesting but I prefer to focus on the PropertiesLoginModule first as it will update the users properties file. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907109#action_12907109 ] Jean-Baptiste Onofré commented on KARAF-34: --- Usage of Jasypt in the PropertiesLoginModule involve that the JAAS module bundle has a new import package (org.jasypt). I raised a task on ServiceMix Jira to provide a Jasypt OSGi bundle (as it's not one by default): https://issues.apache.org/activemq/browse/SMX4-590 > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907114#action_12907114 ] Jean-Baptiste Onofré commented on KARAF-34: --- ServiceMix Jasypt OSGi bundle created and deployed on the maven snapshot repository. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907121#action_12907121 ] Jean-Baptiste Onofré commented on KARAF-34: --- After discussing with Ioannis: - the AbstractKarafLoginModule will contain a new "crypt" attribute. It contains the encryption algorithm. If the crypt attribute is "plain" or null, no encryption is used. - all *LoginModule will embed the crypt logic module as they extend the AbstractKarafLoginModule - it means that the etc/users.properties file should contain password encrypted using the AbstractKarafLoginModule "crypt" algorithm (it can be plain as currently). We have to provide a user: shell commands to manage the user add/delete and password encryption (and write the etc/users.properties file in the case of the PropertiesLoginModule usage). > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-188) Provide commands to manage users, passwords and roles
[ https://issues.apache.org/jira/browse/KARAF-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907127#action_12907127 ] Jean-Baptiste Onofré commented on KARAF-188: I think that the jass:useradd and jaas:passwd should get the encryption from the LoginModule crypt attribute by default. > Provide commands to manage users, passwords and roles > - > > Key: KARAF-188 > URL: https://issues.apache.org/jira/browse/KARAF-188 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907216#action_12907216 ] Jean-Baptiste Onofré commented on KARAF-34: --- After thinking again about this, it's not easy to implement the encryption login in the AbstractKarafLoginModule as the login() method is delegated to each login module. The encryption login should be located in the login() method. The "common" part between all login module is that they call passwordCallback() in the login() method to get the password provided by the user. I propose to make a kind of encryptedPasswordCallback() on top of the passwordCallback(). It will get the plain password provided by the user and crypt using the crypt algorithm defined as attribute of the AbstractKarafLoginModule. Like this, each login module which uses the encryptedPasswordCallback() in place of passwordCallback() will get encrypted password. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-191) Create a Karaf Util bundle gathering all util classes
Create a Karaf Util bundle gathering all util classes - Key: KARAF-191 URL: https://issues.apache.org/jira/browse/KARAF-191 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.1.0 Some resources are spread in the different Karaf bundle. For example, Properties can be found in: - shell/config/src/main/java/org/apache/karaf/shell/config/Properties.java - shell/dev/src/main/java/org/apache/karaf/shell/dev/util/Properties.java I'm gonna create a util bundle which gather this kind of resources. I prefer a bundle as, in the future, if we have some util which required dependencies (for example commons-lang), we can use constraint resolution (better than embedded dependencies). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907771#action_12907771 ] Jean-Baptiste Onofré commented on KARAF-34: --- After discussing with Guillaume, overriding callback has a huge impact on JAAS clients. I updated the AbstractKarafLoginModule to use jasypt and provide "util" methods to manipulate password. See revision 995565. The Karaf distributions have been updated too to load Apache ServiceMix Jasypt bundle at startup (required by JAAS Module bundle). Next steps are: - use these password methods in login modules (such as the PropertiesLoginModule) - update the PropertiesLoginModule to automatically crypt password provided in clear Any comments are welcome. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907772#action_12907772 ] Jean-Baptiste Onofré commented on KARAF-34: --- NB: to be able to use Jasypt, I added commons-codec and commons-lang ServiceMix bundles in the startup. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907910#action_12907910 ] Jean-Baptiste Onofré commented on KARAF-34: --- Yes, Guillaume. I propose: - to create an encryption feature including commons-codec, commons-lang and jasypt servicemix bundle + a karaf encryption bundle which register two password related services: one to encrypt, one to check password - in the AbstractKarafLoginModule, the default encryption algorithm is plain (no encryption) - if the encryption algorithm is different from plain (MD5, SHA-1, etc), the AbstractKarafLoginModule delegates the check and encrypt to the encryption service. If the service is not registered, I raise an IllegalStateException. What do you think ? > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907918#action_12907918 ] Jean-Baptiste Onofré commented on KARAF-34: --- NB: it means that we have a Karaf encryption interface and we will have a first implementation using jasypt. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908165#action_12908165 ] Jean-Baptiste Onofré commented on KARAF-34: --- I have rollbacked my latest changes. I begin to add an ecnryption feature. In the Karaf feature core, we will have the encryption interface and the encryption feature bundle will implement the interface using Jasypt. Revision 995953. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-163) Generate Features XML should handle artifact types
[ https://issues.apache.org/jira/browse/KARAF-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-163. Fix Version/s: 2.1.0 Resolution: Fixed Revision 996279. > Generate Features XML should handle artifact types > -- > > Key: KARAF-163 > URL: https://issues.apache.org/jira/browse/KARAF-163 > Project: Karaf > Issue Type: Improvement >Reporter: Ioannis Canellos >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0 > > Attachments: maven-features-patch.txt > > > The Generate Features XML does not append to the generated elements the type > of the artifact. > For jar artifact that is no problem. However, for other types (e.g. war) this > cause problems, because the generated feature cannot be installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[
https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908658#action_12908658
]
Jean-Baptiste Onofré commented on KARAF-34:
---
After discussing with Guillaume, as the LoginModule is loaded by the JRE, it's
not easy to "inject" something on it.
The only way is to create a ThreadLocal in OsgiConfiguration storing the
Encryption service reference (or the BundleContext):
protected static ThreadLocal> params;
public static void setParams(Map params) {
AbstractKarafLoginModule.params.set(params);
}
and push it into the AbstractKarafLoginModule.
Like this any LoginModule will get at least the BundleContext and so be able to
use the Encryption service when needed.
> Provide a way to have passwords encrypted and not in clear in the
> configuration files
> -
>
> Key: KARAF-34
> URL: https://issues.apache.org/jira/browse/KARAF-34
> Project: Karaf
> Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908983#action_12908983 ] Jean-Baptiste Onofré commented on KARAF-34: --- Revision 996679. Performed: - move jasypt encryption feature in jaas module - upgrade the encryption feature description - modify the Config JaasRealm to add the bundleContext in the login module options map - use the encryption service in the AbstractKarafLoginModule TODO: - add a AdminConfig property placeholder to inject the encryption attribute - use encryption it in the PropertiesLoginModule - crypt password when need and store it in the user properties file (in the PropertiesLoginModule). > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-34) Provide a way to have passwords encrypted and not in clear in the configuration files
[ https://issues.apache.org/jira/browse/KARAF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-34. --- Fix Version/s: 2.2.0 Resolution: Fixed Revision 996922. > Provide a way to have passwords encrypted and not in clear in the > configuration files > - > > Key: KARAF-34 > URL: https://issues.apache.org/jira/browse/KARAF-34 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-191) Create a Karaf Util module gathering all util classes
[ https://issues.apache.org/jira/browse/KARAF-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-191: --- Summary: Create a Karaf Util module gathering all util classes (was: Create a Karaf Util bundle gathering all util classes) Description: Some resources are spread in the different Karaf bundle. For example, Properties can be found in: - shell/config/src/main/java/org/apache/karaf/shell/config/Properties.java - shell/dev/src/main/java/org/apache/karaf/shell/dev/util/Properties.java In the same way, the variable substitution mechanism (spread across several util classes). I'm gonna create a util module which gather this kind of resources. The question is the format of this module: - a simple jar, usable directly in the Main (required for variables subsitution) - a bundle was: Some resources are spread in the different Karaf bundle. For example, Properties can be found in: - shell/config/src/main/java/org/apache/karaf/shell/config/Properties.java - shell/dev/src/main/java/org/apache/karaf/shell/dev/util/Properties.java I'm gonna create a util bundle which gather this kind of resources. I prefer a bundle as, in the future, if we have some util which required dependencies (for example commons-lang), we can use constraint resolution (better than embedded dependencies). > Create a Karaf Util module gathering all util classes > - > > Key: KARAF-191 > URL: https://issues.apache.org/jira/browse/KARAF-191 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0 > > > Some resources are spread in the different Karaf bundle. > For example, Properties can be found in: > - shell/config/src/main/java/org/apache/karaf/shell/config/Properties.java > - shell/dev/src/main/java/org/apache/karaf/shell/dev/util/Properties.java > In the same way, the variable substitution mechanism (spread across several > util classes). > I'm gonna create a util module which gather this kind of resources. > The question is the format of this module: > - a simple jar, usable directly in the Main (required for variables > subsitution) > - a bundle -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-202) Create la alias in shell.init.script
Create la alias in shell.init.script Key: KARAF-202 URL: https://issues.apache.org/jira/browse/KARAF-202 Project: Karaf Issue Type: Improvement Components: runtime Affects Versions: 2.0.0 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.1.0, 2.2.0 Now, to list all available bundle, the user has to type "osgi:list -t 0" (change from previous versions). To give easier usage to the end user, I will create a "la" alias in the shell.init.script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-191) Create a Karaf Util module gathering all util classes
[ https://issues.apache.org/jira/browse/KARAF-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-191. Resolution: Fixed Revision 997058. > Create a Karaf Util module gathering all util classes > - > > Key: KARAF-191 > URL: https://issues.apache.org/jira/browse/KARAF-191 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0 > > > Some resources are spread in the different Karaf bundle. > For example, Properties can be found in: > - shell/config/src/main/java/org/apache/karaf/shell/config/Properties.java > - shell/dev/src/main/java/org/apache/karaf/shell/dev/util/Properties.java > In the same way, the variable substitution mechanism (spread across several > util classes). > I'm gonna create a util module which gather this kind of resources. > The question is the format of this module: > - a simple jar, usable directly in the Main (required for variables > subsitution) > - a bundle -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-202) Create la alias in shell.init.script
[ https://issues.apache.org/jira/browse/KARAF-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-202. Resolution: Fixed Revision 997074. > Create la alias in shell.init.script > > > Key: KARAF-202 > URL: https://issues.apache.org/jira/browse/KARAF-202 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0, 2.2.0 > > > Now, to list all available bundle, the user has to type "osgi:list -t 0" > (change from previous versions). > To give easier usage to the end user, I will create a "la" alias in the > shell.init.script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-205) Rename encryption feature to jasypt-encryption
Rename encryption feature to jasypt-encryption -- Key: KARAF-205 URL: https://issues.apache.org/jira/browse/KARAF-205 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré The current encryption feature is based on Jasypt. As other encryption feature could be added, it's more clear to rename the encryption feature to jasypt-encryption. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-205) Rename encryption feature to jasypt-encryption
[ https://issues.apache.org/jira/browse/KARAF-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-205. Resolution: Fixed Revision 997245. > Rename encryption feature to jasypt-encryption > -- > > Key: KARAF-205 > URL: https://issues.apache.org/jira/browse/KARAF-205 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > The current encryption feature is based on Jasypt. > As other encryption feature could be added, it's more clear to rename the > encryption feature to jasypt-encryption. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-199) WarDeploymentListener: doesn't handle the default Webapp-Context correct on a Windows System
[ https://issues.apache.org/jira/browse/KARAF-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-199: -- Assignee: Jean-Baptiste Onofré (was: Guillaume Nodet) > WarDeploymentListener: doesn't handle the default Webapp-Context correct on a > Windows System > > > Key: KARAF-199 > URL: https://issues.apache.org/jira/browse/KARAF-199 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.0.0 > Environment: Windows >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0 > > Attachments: org.apache.karaf.deployer.war.patch, > WarDeploymentListener.java.patch > > > The WarDeploymentListener checks for the File.seperator which is dependent on > the system runtime. > Since the incoming path is an URL path it is always a slash. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-199) WarDeploymentListener: doesn't handle the default Webapp-Context correct on a Windows System
[ https://issues.apache.org/jira/browse/KARAF-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-199. Resolution: Fixed Revision 999087. Patch commited and tests performed. It looks fine for me. > WarDeploymentListener: doesn't handle the default Webapp-Context correct on a > Windows System > > > Key: KARAF-199 > URL: https://issues.apache.org/jira/browse/KARAF-199 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.0.0 > Environment: Windows >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0 > > Attachments: org.apache.karaf.deployer.war.patch, > WarDeploymentListener.java.patch > > > The WarDeploymentListener checks for the File.seperator which is dependent on > the system runtime. > Since the incoming path is an URL path it is always a slash. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-199) WarDeploymentListener: doesn't handle the default Webapp-Context correct on a Windows System
[ https://issues.apache.org/jira/browse/KARAF-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912690#action_12912690 ] Jean-Baptiste Onofré commented on KARAF-199: Merged on the 2.1.x branch. > WarDeploymentListener: doesn't handle the default Webapp-Context correct on a > Windows System > > > Key: KARAF-199 > URL: https://issues.apache.org/jira/browse/KARAF-199 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.0.0 > Environment: Windows >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.0 > > Attachments: org.apache.karaf.deployer.war.patch, > WarDeploymentListener.java.patch > > > The WarDeploymentListener checks for the File.seperator which is dependent on > the system runtime. > Since the incoming path is an URL path it is always a slash. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-5) [karaf] admin:create should support a -r, --rmi-registry-port option to allow the RMI registry port to be configured
[ https://issues.apache.org/jira/browse/KARAF-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915025#action_12915025 ] Jean-Baptiste Onofré commented on KARAF-5: -- Previous step is to rename port in admin to sshPort to avoid mistake between the RMI and SSH port. After, I will introduce the SSH port attribute. > [karaf] admin:create should support a -r, --rmi-registry-port option to allow > the RMI registry port to be configured > - > > Key: KARAF-5 > URL: https://issues.apache.org/jira/browse/KARAF-5 > Project: Karaf > Issue Type: Bug >Reporter: Eoghan Glynn >Assignee: Jean-Baptiste Onofré > > By default the JMX/RMI serviceURL is configured for child instances with the > same RMI registry port as the root instance. > As a result, the monitoring of the child can depend on the live-ness of the > root instance, depending on the startup sequence. > For example if the child is created via "admin:create foo" in the root's > shell, but then started via the $KARAF_HOME/instances/foo/bin/start script, > the child shares the single RMI registry hosted by the root instance. > If the root instance is then stopped, the child may no longer be monitored > over JMX. Even if the root is restarted, the child still cannot be monitored > as there is no auto-reregistration. > Instead it should be possible to create a child instance with an > instance-specific RMI registry port so that its not dependent on an RMI > registry shared with another instance, e.g. "admin:create --rmi-registry-port > 1199 foo" so that rmiRegistryPort=1199 > is configured in > $KARAF_HOME/instances/foo/etc/org.apache.felix.karaf.management.cfg -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-233) Add a log:clear command
Add a log:clear command --- Key: KARAF-233 URL: https://issues.apache.org/jira/browse/KARAF-233 Project: Karaf Issue Type: New Feature Reporter: Jean-Baptiste Onofré Using the command log:display quickly becomes unuseable when the log grows to 1MB and beyond. It would be nice if the log could be cleared from the command line using log:clear. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-236) Command Features:info with tree switch displays partial information
Command Features:info with tree switch displays partial information
---
Key: KARAF-236
URL: https://issues.apache.org/jira/browse/KARAF-236
Project: Karaf
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Łukasz Dywicki
If we add -t (tree) switch to features:info command result list contains
toString method results:
{code}
ka...@root> features:info -t jbi
Description of jbi 1.3.0-fuse-00-00 feature
Feature has no configuration
Feature depends on:
naming 1.3.0-fuse-00-00
transaction 0.1-r964701
nmr 1.3.0-fuse-00-00
woodstox 4.0.8
Feature contains followed bundles:
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/1.5.0
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jbi-api-1.0/1.5.0
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.wsdl4j/1.6.2_2
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_3
mvn:org.apache.servicemix/servicemix-common/2010.02.0-fuse-00-00
mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.runtime/1.3.0-fuse-00-00
mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.osgi/1.3.0-fuse-00-00
mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.deployer/1.3.0-fuse-00-00
mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.commands/1.3.0-fuse-00-00
Feature tree
jbi 1.3.0-fuse-00-00
+ org.apache.karaf.features.internal.bundleinfoi...@779005c4
+ org.apache.karaf.features.internal.bundleinfoi...@106ac42f
+ org.apache.karaf.features.internal.bundleinfoi...@5175f214
+ org.apache.karaf.features.internal.bundleinfoi...@166828d4
+ org.apache.karaf.features.internal.bundleinfoi...@105081ca
+ org.apache.karaf.features.internal.bundleinfoi...@1578fd24
+ org.apache.karaf.features.internal.bundleinfoi...@3a33517f
+ org.apache.karaf.features.internal.bundleinfoi...@7f2b86b2
\ org.apache.karaf.features.internal.bundleinfoi...@2985158
naming 1.3.0-fuse-00-00
\ org.apache.karaf.features.internal.bundleinfoi...@5e0469bc
transaction 0.1-r964701
\ org.apache.karaf.features.internal.bundleinfoi...@73b9e5dc
nmr 1.3.0-fuse-00-00
+ org.apache.karaf.features.internal.bundleinfoi...@31a209df
+ org.apache.karaf.features.internal.bundleinfoi...@53628ee
+ org.apache.karaf.features.internal.bundleinfoi...@26b923ee
+ org.apache.karaf.features.internal.bundleinfoi...@44e5f21e
+ org.apache.karaf.features.internal.bundleinfoi...@547ab2e8
+ org.apache.karaf.features.internal.bundleinfoi...@4377c8ac
\ org.apache.karaf.features.internal.bundleinfoi...@6d17b6ce
document 1.3.0-fuse-00-00
\ org.apache.karaf.features.internal.bundleinfoi...@2fe2c656
woodstox 4.0.8
+ org.apache.karaf.features.internal.bundleinfoi...@514b50a9
+ org.apache.karaf.features.internal.bundleinfoi...@279cb0f1
\ org.apache.karaf.features.internal.bundleinfoi...@2024b288
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-236) Command Features:info with tree switch displays partial information
[
https://issues.apache.org/jira/browse/KARAF-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Łukasz Dywicki updated KARAF-236:
-
Attachment: org.apache.karaf.features.command.patch
Patch with fix. Root of attached diff is features/command directory.
> Command Features:info with tree switch displays partial information
> ---
>
> Key: KARAF-236
> URL: https://issues.apache.org/jira/browse/KARAF-236
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
> Attachments: org.apache.karaf.features.command.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> If we add -t (tree) switch to features:info command result list contains
> toString method results:
> {code}
> ka...@root> features:info -t jbi
> Description of jbi 1.3.0-fuse-00-00 feature
>
> Feature has no configuration
> Feature depends on:
> naming 1.3.0-fuse-00-00
> transaction 0.1-r964701
> nmr 1.3.0-fuse-00-00
> woodstox 4.0.8
> Feature contains followed bundles:
>
> mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/1.5.0
>
> mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jbi-api-1.0/1.5.0
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.wsdl4j/1.6.2_2
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_3
> mvn:org.apache.servicemix/servicemix-common/2010.02.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.runtime/1.3.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.osgi/1.3.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.deployer/1.3.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.commands/1.3.0-fuse-00-00
> Feature tree
> jbi 1.3.0-fuse-00-00
> + org.apache.karaf.features.internal.bundleinfoi...@779005c4
> + org.apache.karaf.features.internal.bundleinfoi...@106ac42f
> + org.apache.karaf.features.internal.bundleinfoi...@5175f214
> + org.apache.karaf.features.internal.bundleinfoi...@166828d4
> + org.apache.karaf.features.internal.bundleinfoi...@105081ca
> + org.apache.karaf.features.internal.bundleinfoi...@1578fd24
> + org.apache.karaf.features.internal.bundleinfoi...@3a33517f
> + org.apache.karaf.features.internal.bundleinfoi...@7f2b86b2
> \ org.apache.karaf.features.internal.bundleinfoi...@2985158
> naming 1.3.0-fuse-00-00
> \ org.apache.karaf.features.internal.bundleinfoi...@5e0469bc
> transaction 0.1-r964701
> \ org.apache.karaf.features.internal.bundleinfoi...@73b9e5dc
> nmr 1.3.0-fuse-00-00
> + org.apache.karaf.features.internal.bundleinfoi...@31a209df
> + org.apache.karaf.features.internal.bundleinfoi...@53628ee
> + org.apache.karaf.features.internal.bundleinfoi...@26b923ee
> + org.apache.karaf.features.internal.bundleinfoi...@44e5f21e
> + org.apache.karaf.features.internal.bundleinfoi...@547ab2e8
> + org.apache.karaf.features.internal.bundleinfoi...@4377c8ac
> \ org.apache.karaf.features.internal.bundleinfoi...@6d17b6ce
>document 1.3.0-fuse-00-00
>\ org.apache.karaf.features.internal.bundleinfoi...@2fe2c656
> woodstox 4.0.8
> + org.apache.karaf.features.internal.bundleinfoi...@514b50a9
> + org.apache.karaf.features.internal.bundleinfoi...@279cb0f1
> \ org.apache.karaf.features.internal.bundleinfoi...@2024b288
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-236) Command Features:info with tree switch displays partial information
[
https://issues.apache.org/jira/browse/KARAF-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Łukasz Dywicki reassigned KARAF-236:
Assignee: Guillaume Nodet (was: Łukasz Dywicki)
> Command Features:info with tree switch displays partial information
> ---
>
> Key: KARAF-236
> URL: https://issues.apache.org/jira/browse/KARAF-236
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Łukasz Dywicki
>Assignee: Guillaume Nodet
> Attachments: org.apache.karaf.features.command.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> If we add -t (tree) switch to features:info command result list contains
> toString method results:
> {code}
> ka...@root> features:info -t jbi
> Description of jbi 1.3.0-fuse-00-00 feature
>
> Feature has no configuration
> Feature depends on:
> naming 1.3.0-fuse-00-00
> transaction 0.1-r964701
> nmr 1.3.0-fuse-00-00
> woodstox 4.0.8
> Feature contains followed bundles:
>
> mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/1.5.0
>
> mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jbi-api-1.0/1.5.0
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.wsdl4j/1.6.2_2
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_3
> mvn:org.apache.servicemix/servicemix-common/2010.02.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.runtime/1.3.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.osgi/1.3.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.deployer/1.3.0-fuse-00-00
>
> mvn:org.apache.servicemix.jbi/org.apache.servicemix.jbi.commands/1.3.0-fuse-00-00
> Feature tree
> jbi 1.3.0-fuse-00-00
> + org.apache.karaf.features.internal.bundleinfoi...@779005c4
> + org.apache.karaf.features.internal.bundleinfoi...@106ac42f
> + org.apache.karaf.features.internal.bundleinfoi...@5175f214
> + org.apache.karaf.features.internal.bundleinfoi...@166828d4
> + org.apache.karaf.features.internal.bundleinfoi...@105081ca
> + org.apache.karaf.features.internal.bundleinfoi...@1578fd24
> + org.apache.karaf.features.internal.bundleinfoi...@3a33517f
> + org.apache.karaf.features.internal.bundleinfoi...@7f2b86b2
> \ org.apache.karaf.features.internal.bundleinfoi...@2985158
> naming 1.3.0-fuse-00-00
> \ org.apache.karaf.features.internal.bundleinfoi...@5e0469bc
> transaction 0.1-r964701
> \ org.apache.karaf.features.internal.bundleinfoi...@73b9e5dc
> nmr 1.3.0-fuse-00-00
> + org.apache.karaf.features.internal.bundleinfoi...@31a209df
> + org.apache.karaf.features.internal.bundleinfoi...@53628ee
> + org.apache.karaf.features.internal.bundleinfoi...@26b923ee
> + org.apache.karaf.features.internal.bundleinfoi...@44e5f21e
> + org.apache.karaf.features.internal.bundleinfoi...@547ab2e8
> + org.apache.karaf.features.internal.bundleinfoi...@4377c8ac
> \ org.apache.karaf.features.internal.bundleinfoi...@6d17b6ce
>document 1.3.0-fuse-00-00
>\ org.apache.karaf.features.internal.bundleinfoi...@2fe2c656
> woodstox 4.0.8
> + org.apache.karaf.features.internal.bundleinfoi...@514b50a9
> + org.apache.karaf.features.internal.bundleinfoi...@279cb0f1
> \ org.apache.karaf.features.internal.bundleinfoi...@2024b288
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-239) Equinox Framework Extensions
Equinox Framework Extensions Key: KARAF-239 URL: https://issues.apache.org/jira/browse/KARAF-239 Project: Karaf Issue Type: Bug Affects Versions: 2.1.0 Environment: Linux (Ubuntu 10.04), Java 1.6.0_20, equinox Reporter: Joachim Bäck Installing the Equinox Aspects Framework Extension [1] into Equinox fails in 2.1.0 with an error in KARAF_HOME/data/cache/xxx.log This was possible in 2.0.0 by simply putting the jar containing the extension into the lib folder of Karaf (the documentation states that the system property: "osgi.framework.extensions=org.eclipse.equinox.weaving.hook" must be set in order for equinox to load the extension - this however was not needed). [1] http://www.eclipse.org/equinox/incubator/aspects/index.php -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-239) Equinox Framework Extensions
[ https://issues.apache.org/jira/browse/KARAF-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joachim Bäck updated KARAF-239: --- Attachment: org.eclipse.equinox.weaving.hook_1.0.0.jar 1285688419852.log > Equinox Framework Extensions > > > Key: KARAF-239 > URL: https://issues.apache.org/jira/browse/KARAF-239 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.1.0 > Environment: Linux (Ubuntu 10.04), Java 1.6.0_20, equinox >Reporter: Joachim Bäck > Attachments: 1285688419852.log, > org.eclipse.equinox.weaving.hook_1.0.0.jar > > > Installing the Equinox Aspects Framework Extension [1] into Equinox fails in > 2.1.0 with an error in KARAF_HOME/data/cache/xxx.log > This was possible in 2.0.0 by simply putting the jar containing the extension > into the lib folder of Karaf (the documentation states that the system > property: "osgi.framework.extensions=org.eclipse.equinox.weaving.hook" must > be set in order for equinox to load the extension - this however was not > needed). > [1] http://www.eclipse.org/equinox/incubator/aspects/index.php -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-240) Cleanup Karaf pom to use version and groupId from the parent pom
Cleanup Karaf pom to use version and groupId from the parent pom Key: KARAF-240 URL: https://issues.apache.org/jira/browse/KARAF-240 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.2.0 To simplify Karaf modules, the pom should use (when possible) version and groupId from the parent pom. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-240) Cleanup Karaf pom to use version and groupId from the parent pom
[ https://issues.apache.org/jira/browse/KARAF-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-240. Resolution: Fixed Revision 1003648. > Cleanup Karaf pom to use version and groupId from the parent pom > > > Key: KARAF-240 > URL: https://issues.apache.org/jira/browse/KARAF-240 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.0 > > > To simplify Karaf modules, the pom should use (when possible) version and > groupId from the parent pom. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-52) Provide shell commands for SCR
[ https://issues.apache.org/jira/browse/KARAF-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918009#action_12918009 ] Łukasz Dywicki commented on KARAF-52: - Hi Daniel, Could you give more details about commands you would get? Would you get similar functionality like Spring/Blueprint? Best regards, Lukasz > Provide shell commands for SCR > -- > > Key: KARAF-52 > URL: https://issues.apache.org/jira/browse/KARAF-52 > Project: Karaf > Issue Type: Improvement >Reporter: Daniel Bimschas > > Currently, commands for inspecting the status of the Service Component > Runtime (SCR) are missing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-52) Provide shell commands for SCR
[ https://issues.apache.org/jira/browse/KARAF-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918021#action_12918021 ] Łukasz Dywicki commented on KARAF-52: - It is not a problem to provide these commands - by default Blueprint and Spring DM publishes context as service. We can use these instances to manage. For example spring:stop , blueprint:stop , scr:stop . However I don't know yet how to make this in blueprint because org.osgi.service.blueprint.container.BlueprintContainer does not have any stop/start methods. Spring exposes context with additional interface org.springframework.context.Lifecycle wchich allows stopping or starting context. > Provide shell commands for SCR > -- > > Key: KARAF-52 > URL: https://issues.apache.org/jira/browse/KARAF-52 > Project: Karaf > Issue Type: Improvement >Reporter: Daniel Bimschas > > Currently, commands for inspecting the status of the Service Component > Runtime (SCR) are missing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-242) Action cannot be used as reference listener
Action cannot be used as reference listener --- Key: KARAF-242 URL: https://issues.apache.org/jira/browse/KARAF-242 Project: Karaf Issue Type: Bug Components: console Affects Versions: 2.0.0, 2.1.0 Reporter: Łukasz Dywicki At this moment actions created by Shell namespace handler have auto-generated ID's. We should allow to set action ID and create references between actions and other blueprint container components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-242) Action cannot be used as reference listener
[ https://issues.apache.org/jira/browse/KARAF-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918821#action_12918821 ] Łukasz Dywicki commented on KARAF-242: -- Proposed resolution is commited to my github fork: http://github.com/splatch/karaf/commit/45ab791bcd00498e4f6ef1e2bcf26dc7749334eb > Action cannot be used as reference listener > --- > > Key: KARAF-242 > URL: https://issues.apache.org/jira/browse/KARAF-242 > Project: Karaf > Issue Type: Bug > Components: console >Affects Versions: 2.0.0, 2.1.0 >Reporter: Łukasz Dywicki > > At this moment actions created by Shell namespace handler have auto-generated > ID's. We should allow to set action ID and create references between actions > and other blueprint container components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (KARAF-242) Action cannot be used as reference listener
[ https://issues.apache.org/jira/browse/KARAF-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918821#action_12918821 ] Łukasz Dywicki edited comment on KARAF-242 at 10/7/10 4:08 AM: --- Proposed resolution is commited to my github fork: http://github.com/splatch/karaf/commit/46a825411482004d14c0ae4463b9ef210cf1bc0b was (Author: splatch): Proposed resolution is commited to my github fork: http://github.com/splatch/karaf/commit/45ab791bcd00498e4f6ef1e2bcf26dc7749334eb > Action cannot be used as reference listener > --- > > Key: KARAF-242 > URL: https://issues.apache.org/jira/browse/KARAF-242 > Project: Karaf > Issue Type: Bug > Components: console >Affects Versions: 2.0.0, 2.1.0 >Reporter: Łukasz Dywicki > > At this moment actions created by Shell namespace handler have auto-generated > ID's. We should allow to set action ID and create references between actions > and other blueprint container components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-209) Allow the info command to display custom information such as Apache ServiceMix version number
[
https://issues.apache.org/jira/browse/KARAF-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918824#action_12918824
]
Łukasz Dywicki commented on KARAF-209:
--
On github Karaf fork I've created extension wchich allows using static manifest
entries to add additional info:
http://github.com/splatch/karaf/commit/45ab791bcd00498e4f6ef1e2bcf26dc7749334eb
Extension uses Karaf-Info manifest entry to create InfoProvider with given
data. Manifest entry format is: category;(item=value);(item=value)..., for
example: Camel;Version=2.2.0;Release-date=10/10/2010 will add following info
entry:
{code}
Camel
Version 2.2.0
Release-date 10/10/2010
{code}
> Allow the info command to display custom information such as Apache
> ServiceMix version number
> -
>
> Key: KARAF-209
> URL: https://issues.apache.org/jira/browse/KARAF-209
> Project: Karaf
> Issue Type: New Feature
> Components: console
>Affects Versions: 2.0.0
>Reporter: Claus Ibsen
>Assignee: Ioannis Canellos
>Priority: Minor
> Fix For: 2.2.0
>
>
> The info command lists nice basic information about the OS, JVM, Karaf etc.
> All important information for support etc.
> But when using Apache ServiceMix it does not display information about
> ServiceMix, which would be nice to display SMX version number etc.
> And for companies distributing ServiceMix under their own label, it would be
> nice for them to add custom information / version as well.
> Maybe allow it to load some fixed information from a etc or properties file
> so custom/fixed information can be displayed. Kinda like a header to the info
> command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
changing the default JMX service uri to be more enterprise frendly -- Key: KARAF-253 URL: https://issues.apache.org/jira/browse/KARAF-253 Project: Karaf Issue Type: Improvement Affects Versions: 2.1.0 Reporter: Christian Müller Fix For: 2.1.1, 2.2.0 Please see Nabble for details: http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
[ https://issues.apache.org/jira/browse/KARAF-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated KARAF-253: --- Attachment: KARAF-253_fix_for_2.2.0.patch Attached the patch for KARAF 2.2.0 (based on the current 2.1.99-SNAPSHOT) > changing the default JMX service uri to be more enterprise frendly > -- > > Key: KARAF-253 > URL: https://issues.apache.org/jira/browse/KARAF-253 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Christian Müller > Fix For: 2.1.1, 2.2.0 > > Attachments: KARAF-253_fix_for_2.2.0.patch > > > Please see Nabble for details: > http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html > Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
[ https://issues.apache.org/jira/browse/KARAF-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated KARAF-253: --- Attachment: KARAF-253_fix_for_2.1.1.patch Attached the patch for KARAF 2.1.1 (based on the current 2.1.1-SNAPSHOT) > changing the default JMX service uri to be more enterprise frendly > -- > > Key: KARAF-253 > URL: https://issues.apache.org/jira/browse/KARAF-253 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Christian Müller > Fix For: 2.1.1, 2.2.0 > > Attachments: KARAF-253_fix_for_2.1.1.patch, > KARAF-253_fix_for_2.2.0.patch > > > Please see Nabble for details: > http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html > Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
[ https://issues.apache.org/jira/browse/KARAF-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923352#action_12923352 ] Christian Müller commented on KARAF-253: There are some wiki or documentation pages which should also be updated? > changing the default JMX service uri to be more enterprise frendly > -- > > Key: KARAF-253 > URL: https://issues.apache.org/jira/browse/KARAF-253 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Christian Müller > Fix For: 2.1.1, 2.2.0 > > Attachments: KARAF-253_fix_for_2.1.1.patch, > KARAF-253_fix_for_2.2.0.patch > > > Please see Nabble for details: > http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html > Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-233) Add a log:clear command
[ https://issues.apache.org/jira/browse/KARAF-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-233: -- Assignee: Jean-Baptiste Onofré > Add a log:clear command > --- > > Key: KARAF-233 > URL: https://issues.apache.org/jira/browse/KARAF-233 > Project: Karaf > Issue Type: New Feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > Using the command log:display quickly becomes unuseable when the log grows to > 1MB and beyond. It would be nice if the log could be cleared from the command > line using log:clear. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (KARAF-233) Add a log:clear command
[ https://issues.apache.org/jira/browse/KARAF-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-233 started by Jean-Baptiste Onofré. > Add a log:clear command > --- > > Key: KARAF-233 > URL: https://issues.apache.org/jira/browse/KARAF-233 > Project: Karaf > Issue Type: New Feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > Using the command log:display quickly becomes unuseable when the log grows to > 1MB and beyond. It would be nice if the log could be cleared from the command > line using log:clear. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-245) Export SUN packages in config.properties like done in ServiceMix
[ https://issues.apache.org/jira/browse/KARAF-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923467#action_12923467 ] Jean-Baptiste Onofré commented on KARAF-245: Not sure it should be make by default as it's JDK vendor dependant. The etc/jre.properties is only JRE version dependant, not vendor. We have to enhance the jre.properties or the config.properties to define the Sun packages running on a JDK Sun vendor. > Export SUN packages in config.properties like done in ServiceMix > > > Key: KARAF-245 > URL: https://issues.apache.org/jira/browse/KARAF-245 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.0.0, 2.1.0 > Environment: davsclaus:/opt$ mvn -version > Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_20 > Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac" >Reporter: Claus Ibsen > > I am updating chapter 13 about OSGi and I hit a problem with camel-cxf > and Karaf 2.1 > He is what I do > davsclaus:/opt$ mvn -version > Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_20 > Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac" > davsclaus:/opt$ tar -xf ~/Downloads/apache-karaf-2.1.0.tar.gz > davsclaus:/opt/apache-karaf-2.1.0$ bin/karaf > ka...@root> features:addurl > mvn:org.apache.camel.karaf/apache-camel/2.5-SNAPSHOT/xml/features > ka...@root> features:install camel-cxf > Error executing command: Could not start bundle > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1 > in feature(s) : Unresolved constraint in bundle > org.apache.servicemix.bundles.saaj-impl [90]: Unable to resolve 90.0: > missing requirement [90.0] package; > (package=com.sun.org.apache.xerces.internal.dom) > And I get the above problem with the SUN package. > I have not changed any configuration settings on Karaf. > I just tried with equinox instead of felix as osgi container. Same problem > ka...@root> features:install camel > ka...@root> features: > features:addurl features:info > features:install features:list > features:listrepositoriesfeatures:listurl > features:listversionsfeatures:refreshurl > features:removerepositoryfeatures:removeurl features:uninstall > ka...@root> features:install camel-cxf > Refreshing bundles org.springframework.context (38), > org.springframework.context.support (39), > org.apache.servicemix.bundles.cglib (47), org.apache.camel.camel-core > (46), org.springframework.aop (34), > org.apache.servicemix.bundles.jaxb-impl (44) > Error executing command: Could not start bundle > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1 > in feature(s) : The bundle > "org.apache.servicemix.bundles.saaj-impl_1.3.2.1 [90]" could not be > resolved. Reason: Missing Constraint: Import-Package: > com.sun.org.apache.xerces.internal.dom; version="0.0.0" > And the solution suggested by Willem Jiang > Hi Claus, > ServiceMix is using a different etc/config.properties from the karaf, and it > exports these sun packages > com.sun.org.apache.xalan.internal.xsltc.trax, \ > com.sun.org.apache.xerces.internal.dom, \ > com.sun.org.apache.xerces.internal.jaxp, \ > com.sun.org.apache.xerces.internal.xni, \ > I'm afraid you need to do the same thing in karaf etc/config.properties file > if you are try to using the saaj-impl from sun. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-246) Documentation - How to stop karaf without using KILL
[ https://issues.apache.org/jira/browse/KARAF-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-246: --- Component/s: documentation > Documentation - How to stop karaf without using KILL > > > Key: KARAF-246 > URL: https://issues.apache.org/jira/browse/KARAF-246 > Project: Karaf > Issue Type: Improvement > Components: documentation >Affects Versions: 2.1.0 >Reporter: Claus Ibsen >Priority: Trivial > > In the installation guide > http://karaf.apache.org/3-installation.html > In the bottom its discussed how to stop karaf. Its a bit abrupt to stop it > using a KILL. There is a stop script in the bin holder. > Please document how to use it. > There are some pieces here > http://karaf.apache.org/47-administration.html > Maybe refer to that page, and improve it with more details and examples. > I suppose if you have security enabled you would need to provide credentials > to be able to stop it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-246) Documentation - How to stop karaf without using KILL
[ https://issues.apache.org/jira/browse/KARAF-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923479#action_12923479 ] Jean-Baptiste Onofré commented on KARAF-246: I let the task open as I'm gonna upgrade the documentation in svn. > Documentation - How to stop karaf without using KILL > > > Key: KARAF-246 > URL: https://issues.apache.org/jira/browse/KARAF-246 > Project: Karaf > Issue Type: Improvement > Components: documentation >Affects Versions: 2.1.0 >Reporter: Claus Ibsen >Priority: Trivial > > In the installation guide > http://karaf.apache.org/3-installation.html > In the bottom its discussed how to stop karaf. Its a bit abrupt to stop it > using a KILL. There is a stop script in the bin holder. > Please document how to use it. > There are some pieces here > http://karaf.apache.org/47-administration.html > Maybe refer to that page, and improve it with more details and examples. > I suppose if you have security enabled you would need to provide credentials > to be able to stop it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-246) Documentation - How to stop karaf without using KILL
[ https://issues.apache.org/jira/browse/KARAF-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923478#action_12923478 ] Jean-Baptiste Onofré commented on KARAF-246: The documentation component has been created and I updated the wiki page about starting/stopping Karaf. > Documentation - How to stop karaf without using KILL > > > Key: KARAF-246 > URL: https://issues.apache.org/jira/browse/KARAF-246 > Project: Karaf > Issue Type: Improvement > Components: documentation >Affects Versions: 2.1.0 >Reporter: Claus Ibsen >Priority: Trivial > > In the installation guide > http://karaf.apache.org/3-installation.html > In the bottom its discussed how to stop karaf. Its a bit abrupt to stop it > using a KILL. There is a stop script in the bin holder. > Please document how to use it. > There are some pieces here > http://karaf.apache.org/47-administration.html > Maybe refer to that page, and improve it with more details and examples. > I suppose if you have security enabled you would need to provide credentials > to be able to stop it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-246) Documentation - How to stop karaf without using KILL
[ https://issues.apache.org/jira/browse/KARAF-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-246: -- Assignee: Jean-Baptiste Onofré > Documentation - How to stop karaf without using KILL > > > Key: KARAF-246 > URL: https://issues.apache.org/jira/browse/KARAF-246 > Project: Karaf > Issue Type: Improvement > Components: documentation >Affects Versions: 2.1.0 >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Trivial > > In the installation guide > http://karaf.apache.org/3-installation.html > In the bottom its discussed how to stop karaf. Its a bit abrupt to stop it > using a KILL. There is a stop script in the bin holder. > Please document how to use it. > There are some pieces here > http://karaf.apache.org/47-administration.html > Maybe refer to that page, and improve it with more details and examples. > I suppose if you have security enabled you would need to provide credentials > to be able to stop it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
[ https://issues.apache.org/jira/browse/KARAF-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated KARAF-253: --- Attachment: KARAF-253_documentation.patch Ioannis, I also attached the documentation patch. Please review and commit it also. If you chose another port number than 4, please also update this provided patch with the port number you chose. Thanks, Christian > changing the default JMX service uri to be more enterprise frendly > -- > > Key: KARAF-253 > URL: https://issues.apache.org/jira/browse/KARAF-253 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Christian Müller >Assignee: Ioannis Canellos > Fix For: 2.1.1, 2.2.0 > > Attachments: KARAF-253_documentation.patch, > KARAF-253_fix_for_2.1.1.patch, KARAF-253_fix_for_2.2.0.patch > > > Please see Nabble for details: > http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html > Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-246) Documentation - How to stop karaf without using KILL
[ https://issues.apache.org/jira/browse/KARAF-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-246. Resolution: Fixed I checked the scalate manual provide start/stop information in the user guide. > Documentation - How to stop karaf without using KILL > > > Key: KARAF-246 > URL: https://issues.apache.org/jira/browse/KARAF-246 > Project: Karaf > Issue Type: Improvement > Components: documentation >Affects Versions: 2.1.0 >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Trivial > > In the installation guide > http://karaf.apache.org/3-installation.html > In the bottom its discussed how to stop karaf. Its a bit abrupt to stop it > using a KILL. There is a stop script in the bin holder. > Please document how to use it. > There are some pieces here > http://karaf.apache.org/47-administration.html > Maybe refer to that page, and improve it with more details and examples. > I suppose if you have security enabled you would need to provide credentials > to be able to stop it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-233) Add a log:clear command
[ https://issues.apache.org/jira/browse/KARAF-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-233. Resolution: Fixed Fix Version/s: 2.2.0 Revision 1026241. > Add a log:clear command > --- > > Key: KARAF-233 > URL: https://issues.apache.org/jira/browse/KARAF-233 > Project: Karaf > Issue Type: New Feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.0 > > > Using the command log:display quickly becomes unuseable when the log grows to > 1MB and beyond. It would be nice if the log could be cleared from the command > line using log:clear. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-245) Export SUN packages in config.properties like done in ServiceMix
[ https://issues.apache.org/jira/browse/KARAF-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923848#action_12923848 ] Jean-Baptiste Onofré commented on KARAF-245: Yes, it's in jre.properties. Agree that the Sun packages should be defined for JRE 1.5 too. I fix it right now :) > Export SUN packages in config.properties like done in ServiceMix > > > Key: KARAF-245 > URL: https://issues.apache.org/jira/browse/KARAF-245 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.0.0, 2.1.0 > Environment: davsclaus:/opt$ mvn -version > Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_20 > Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac" >Reporter: Claus Ibsen > > I am updating chapter 13 about OSGi and I hit a problem with camel-cxf > and Karaf 2.1 > He is what I do > davsclaus:/opt$ mvn -version > Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_20 > Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac" > davsclaus:/opt$ tar -xf ~/Downloads/apache-karaf-2.1.0.tar.gz > davsclaus:/opt/apache-karaf-2.1.0$ bin/karaf > ka...@root> features:addurl > mvn:org.apache.camel.karaf/apache-camel/2.5-SNAPSHOT/xml/features > ka...@root> features:install camel-cxf > Error executing command: Could not start bundle > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1 > in feature(s) : Unresolved constraint in bundle > org.apache.servicemix.bundles.saaj-impl [90]: Unable to resolve 90.0: > missing requirement [90.0] package; > (package=com.sun.org.apache.xerces.internal.dom) > And I get the above problem with the SUN package. > I have not changed any configuration settings on Karaf. > I just tried with equinox instead of felix as osgi container. Same problem > ka...@root> features:install camel > ka...@root> features: > features:addurl features:info > features:install features:list > features:listrepositoriesfeatures:listurl > features:listversionsfeatures:refreshurl > features:removerepositoryfeatures:removeurl features:uninstall > ka...@root> features:install camel-cxf > Refreshing bundles org.springframework.context (38), > org.springframework.context.support (39), > org.apache.servicemix.bundles.cglib (47), org.apache.camel.camel-core > (46), org.springframework.aop (34), > org.apache.servicemix.bundles.jaxb-impl (44) > Error executing command: Could not start bundle > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saaj-impl/1.3.2_1 > in feature(s) : The bundle > "org.apache.servicemix.bundles.saaj-impl_1.3.2.1 [90]" could not be > resolved. Reason: Missing Constraint: Import-Package: > com.sun.org.apache.xerces.internal.dom; version="0.0.0" > And the solution suggested by Willem Jiang > Hi Claus, > ServiceMix is using a different etc/config.properties from the karaf, and it > exports these sun packages > com.sun.org.apache.xalan.internal.xsltc.trax, \ > com.sun.org.apache.xerces.internal.dom, \ > com.sun.org.apache.xerces.internal.jaxp, \ > com.sun.org.apache.xerces.internal.xni, \ > I'm afraid you need to do the same thing in karaf etc/config.properties file > if you are try to using the saaj-impl from sun. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-256) Upgrade to PAX-WEB 0.8.0 (SNAPSHOT right now)
[ https://issues.apache.org/jira/browse/KARAF-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-256: -- Assignee: Jean-Baptiste Onofré > Upgrade to PAX-WEB 0.8.0 (SNAPSHOT right now) > - > > Key: KARAF-256 > URL: https://issues.apache.org/jira/browse/KARAF-256 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > > Upgrade to the latest 0.8.0 Version. > New Features of PAX-WEB 0.8.0: > - Usage of Jetty 7 > - Configuration of Jetty through external jetty.xml file > - configuration of webapplications is possible through web.xml (like security) > - pax-web-deployer (replacement for the karaf war deployer) > - and much more... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-256) Upgrade to PAX-WEB 0.8.0 (SNAPSHOT right now)
[ https://issues.apache.org/jira/browse/KARAF-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924011#action_12924011 ] Jean-Baptiste Onofré commented on KARAF-256: Achim, on which repository do you have deployed the PAX-WEB 0.8.0-SNAPSHOT ? Thanks JB > Upgrade to PAX-WEB 0.8.0 (SNAPSHOT right now) > - > > Key: KARAF-256 > URL: https://issues.apache.org/jira/browse/KARAF-256 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > > Upgrade to the latest 0.8.0 Version. > New Features of PAX-WEB 0.8.0: > - Usage of Jetty 7 > - Configuration of Jetty through external jetty.xml file > - configuration of webapplications is possible through web.xml (like security) > - pax-web-deployer (replacement for the karaf war deployer) > - and much more... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-18) features:list fails to show which bundles have been installed by featuresBoot if any exception is thrown during installation
[ https://issues.apache.org/jira/browse/KARAF-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924013#action_12924013 ] Jean-Baptiste Onofré commented on KARAF-18: --- This issue is still present. I made a test last week in ServiceMix and if a boot feature fails to start, feature:list command displays all features as 'uninstall'. > features:list fails to show which bundles have been installed by featuresBoot > if any exception is thrown during installation > > > Key: KARAF-18 > URL: https://issues.apache.org/jira/browse/KARAF-18 > Project: Karaf > Issue Type: Bug > Environment: Apache Servicemix 4.1 RC1 (from FUSE ESB download) >Reporter: Scott Parkerson > > When using FUSE ESB 4.1.0.2, I had pared down the featuresBoot list in > etc/org.apache.felix.karaf.features.cfg to the following: > activemq,activemq-broker,web,camel,camel-flatpack,camel-ftp,camel-http,camel-jdbc,camel-jms,camel-mail,camel-osgi,spring-orm,hibernate,jdbc-postgresql-driver,servlet > I tried this on Apache ServiceMix 4.1 RC1 downloaded from the FUSE ESB > download site, while the features appear to install, the following bundles > fail to start: > [ 70] [Installed ] [] [ 60] activemq-console > (5.3.0.psc-01-00RC1) > ... > [ 72] [Installed ] [] [ 60] Apache ServiceMix Features :: > ActiveMQ Commands (4.1.0.psc-01-00RC1) > (That's an issue for someone else...) > However, if I go to the features:list, nothing is marked as installed, even > though many of the features do install. > So, to reproduce: > 1. Download ServiceMix 4.1 RC1 > 2. Verify that it starts up with the default feature set and that > features:list shows installed features. > 3. Shutdown SMX > 4. Modify etc/org.apache.felix.karaf.features.cfg and make featuresBoot look > like this: > featuresBoot=activemq,activemq-broker,web,camel,camel-flatpack,camel-ftp,camel-http,camel-jdbc,camel-jms,camel-mail,camel-osgi. > 5. Delete the data directory (start clean) and then start SMX > 6. Note that the two ActiveMQ bundles failed to start and that the > features:list lists *nothing* as currently installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
[ https://issues.apache.org/jira/browse/KARAF-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924521#action_12924521 ] Christian Müller commented on KARAF-253: Hello Ioannis, thanks for taking time and picking up this patch. Christian > changing the default JMX service uri to be more enterprise frendly > -- > > Key: KARAF-253 > URL: https://issues.apache.org/jira/browse/KARAF-253 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Christian Müller >Assignee: Ioannis Canellos > Fix For: 2.1.1, 2.2.0 > > Attachments: KARAF-253_documentation.patch, > KARAF-253_fix_for_2.1.1.patch, KARAF-253_fix_for_2.2.0.patch > > > Please see Nabble for details: > http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html > Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-253) changing the default JMX service uri to be more enterprise frendly
[ https://issues.apache.org/jira/browse/KARAF-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926876#action_12926876 ] Christian Müller commented on KARAF-253: Should I do it? > changing the default JMX service uri to be more enterprise frendly > -- > > Key: KARAF-253 > URL: https://issues.apache.org/jira/browse/KARAF-253 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Christian Müller >Assignee: Ioannis Canellos > Fix For: 2.2.0 > > Attachments: KARAF-253_documentation.patch, > KARAF-253_fix_for_2.1.1.patch, KARAF-253_fix_for_2.2.0.patch > > > Please see Nabble for details: > http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-tp3229446p3229446.html > Will apply the patches for both versions later today... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-261) Cannot run command admin on cygwin.
[ https://issues.apache.org/jira/browse/KARAF-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927364#action_12927364 ] Jean-Baptiste Onofré commented on KARAF-261: Thanks Stéphane for the reporting. I make a try and keep you posted. > Cannot run command admin on cygwin. > --- > > Key: KARAF-261 > URL: https://issues.apache.org/jira/browse/KARAF-261 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.1.0 > Environment: cygwin >Reporter: Stephane Chomat > Original Estimate: 0.08h > Remaining Estimate: 0.08h > > Run bin/admin on cygwin and you are an exception. > --- > $ bin/admin > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/karaf/admin/main/Execute > Caused by: java.lang.ClassNotFoundException: > org.apache.karaf.admin.main.Execute > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > Could not find the main class: org.apache.karaf.admin.main.Execute. Program > will exit. > I think the problem is the script bin/admin. > In the run function, move these lines > if $cygwin; then > KARAF_HOME=`cygpath --path --windows "$KARAF_HOME"` > KARAF_BASE=`cygpath --path --windows "$KARAF_BASE"` > CLASSPATH=`cygpath --path --windows "$CLASSPATH"` > fi > after setting classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-263) Upgrade to Spring 3.0.4.RELEASE
Upgrade to Spring 3.0.4.RELEASE --- Key: KARAF-263 URL: https://issues.apache.org/jira/browse/KARAF-263 Project: Karaf Issue Type: Improvement Components: runtime Affects Versions: 2.1.0 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.1.1 Upgrade to Spring 3.0.4.RELEASE to be aligned with ServiceMix and Camel. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-264) Upgrade to Jetty 6.1.25
Upgrade to Jetty 6.1.25 --- Key: KARAF-264 URL: https://issues.apache.org/jira/browse/KARAF-264 Project: Karaf Issue Type: Improvement Components: runtime Affects Versions: 2.1.0, 2.2.0 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.1.1, 2.2.0 Upgrade to Jetty 6.1.25 which provide major bug fixes (especially around performances). ServiceMix provides Jetty bundle 6.1.25_1-SNAPSHOT (waiting for the bundle release). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-264) Upgrade to Jetty 6.1.25
[ https://issues.apache.org/jira/browse/KARAF-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927425#action_12927425 ] Jean-Baptiste Onofré commented on KARAF-264: For the 2.1.x branch: Revision 1030051. > Upgrade to Jetty 6.1.25 > --- > > Key: KARAF-264 > URL: https://issues.apache.org/jira/browse/KARAF-264 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.1, 2.2.0 > > > Upgrade to Jetty 6.1.25 which provide major bug fixes (especially around > performances). > ServiceMix provides Jetty bundle 6.1.25_1-SNAPSHOT (waiting for the bundle > release). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-263) Upgrade to Spring 3.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-263. Resolution: Fixed Revision 1030051. > Upgrade to Spring 3.0.4.RELEASE > --- > > Key: KARAF-263 > URL: https://issues.apache.org/jira/browse/KARAF-263 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.1.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.1 > > > Upgrade to Spring 3.0.4.RELEASE to be aligned with ServiceMix and Camel. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-264) Upgrade to Jetty 6.1.25
[ https://issues.apache.org/jira/browse/KARAF-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-264. Resolution: Fixed Karaf trunk uses Jetty 7.1. > Upgrade to Jetty 6.1.25 > --- > > Key: KARAF-264 > URL: https://issues.apache.org/jira/browse/KARAF-264 > Project: Karaf > Issue Type: Improvement > Components: runtime >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.1, 2.2.0 > > > Upgrade to Jetty 6.1.25 which provide major bug fixes (especially around > performances). > ServiceMix provides Jetty bundle 6.1.25_1-SNAPSHOT (waiting for the bundle > release). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-266) Upgrade Karaf encryption to use Jasypt 1.7
Upgrade Karaf encryption to use Jasypt 1.7 -- Key: KARAF-266 URL: https://issues.apache.org/jira/browse/KARAF-266 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Jasypt 1.7 is out with a set of improvements and bug fixes. I planned to create a bundle in ServiceMix for this Jasypt version: https://issues.apache.org/activemq/browse/SMX4-669 Once the bundle is out, I will update Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-267) Use ServiceMix ASM 3.1.0 bundle in place of the springsource one
Use ServiceMix ASM 3.1.0 bundle in place of the springsource one Key: KARAF-267 URL: https://issues.apache.org/jira/browse/KARAF-267 Project: Karaf Issue Type: Improvement Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré To be able to download the ASM bundle from the Apache central repo, I planned to create an ASM ServiceMix bundle: https://issues.apache.org/activemq/browse/SMX4-670 This bundle will be used in Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-266) Upgrade Karaf encryption to use Jasypt 1.7
[ https://issues.apache.org/jira/browse/KARAF-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-266. Resolution: Fixed Fix Version/s: 2.2.0 Revision 1032495. > Upgrade Karaf encryption to use Jasypt 1.7 > -- > > Key: KARAF-266 > URL: https://issues.apache.org/jira/browse/KARAF-266 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.0 > > > Jasypt 1.7 is out with a set of improvements and bug fixes. > I planned to create a bundle in ServiceMix for this Jasypt version: > https://issues.apache.org/activemq/browse/SMX4-669 > Once the bundle is out, I will update Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-267) Use ServiceMix ASM 3.1.0 bundle in place of the springsource one
[ https://issues.apache.org/jira/browse/KARAF-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-267. Resolution: Fixed Fix Version/s: 2.2.0 Revision 1032510. > Use ServiceMix ASM 3.1.0 bundle in place of the springsource one > > > Key: KARAF-267 > URL: https://issues.apache.org/jira/browse/KARAF-267 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.0 > > > To be able to download the ASM bundle from the Apache central repo, I planned > to create an ASM ServiceMix bundle: > https://issues.apache.org/activemq/browse/SMX4-670 > This bundle will be used in Karaf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-261) Cannot run command admin on cygwin.
[ https://issues.apache.org/jira/browse/KARAF-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-261: -- Assignee: Jean-Baptiste Onofré > Cannot run command admin on cygwin. > --- > > Key: KARAF-261 > URL: https://issues.apache.org/jira/browse/KARAF-261 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.1.0 > Environment: cygwin >Reporter: Stephane Chomat >Assignee: Jean-Baptiste Onofré > Original Estimate: 0.08h > Remaining Estimate: 0.08h > > Run bin/admin on cygwin and you are an exception. > --- > $ bin/admin > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/karaf/admin/main/Execute > Caused by: java.lang.ClassNotFoundException: > org.apache.karaf.admin.main.Execute > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > Could not find the main class: org.apache.karaf.admin.main.Execute. Program > will exit. > I think the problem is the script bin/admin. > In the run function, move these lines > if $cygwin; then > KARAF_HOME=`cygpath --path --windows "$KARAF_HOME"` > KARAF_BASE=`cygpath --path --windows "$KARAF_BASE"` > CLASSPATH=`cygpath --path --windows "$CLASSPATH"` > fi > after setting classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-261) Cannot run command admin on cygwin.
[ https://issues.apache.org/jira/browse/KARAF-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929530#action_12929530 ] Jean-Baptiste Onofré commented on KARAF-261: Fix performed on the trunk: revision 1032516. I'm making the merge on the 2.1.x branch. > Cannot run command admin on cygwin. > --- > > Key: KARAF-261 > URL: https://issues.apache.org/jira/browse/KARAF-261 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.1.0 > Environment: cygwin >Reporter: Stephane Chomat >Assignee: Jean-Baptiste Onofré > Original Estimate: 0.08h > Remaining Estimate: 0.08h > > Run bin/admin on cygwin and you are an exception. > --- > $ bin/admin > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/karaf/admin/main/Execute > Caused by: java.lang.ClassNotFoundException: > org.apache.karaf.admin.main.Execute > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > Could not find the main class: org.apache.karaf.admin.main.Execute. Program > will exit. > I think the problem is the script bin/admin. > In the run function, move these lines > if $cygwin; then > KARAF_HOME=`cygpath --path --windows "$KARAF_HOME"` > KARAF_BASE=`cygpath --path --windows "$KARAF_BASE"` > CLASSPATH=`cygpath --path --windows "$CLASSPATH"` > fi > after setting classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-261) Cannot run command admin on cygwin.
[ https://issues.apache.org/jira/browse/KARAF-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-261. Resolution: Fixed Fix Version/s: 2.2.0 2.1.1 Fix applied on 2.1.x branch: revision 1032524. > Cannot run command admin on cygwin. > --- > > Key: KARAF-261 > URL: https://issues.apache.org/jira/browse/KARAF-261 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.1.0 > Environment: cygwin >Reporter: Stephane Chomat >Assignee: Jean-Baptiste Onofré > Fix For: 2.1.1, 2.2.0 > > Original Estimate: 0.08h > Remaining Estimate: 0.08h > > Run bin/admin on cygwin and you are an exception. > --- > $ bin/admin > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/karaf/admin/main/Execute > Caused by: java.lang.ClassNotFoundException: > org.apache.karaf.admin.main.Execute > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > Could not find the main class: org.apache.karaf.admin.main.Execute. Program > will exit. > I think the problem is the script bin/admin. > In the run function, move these lines > if $cygwin; then > KARAF_HOME=`cygpath --path --windows "$KARAF_HOME"` > KARAF_BASE=`cygpath --path --windows "$KARAF_BASE"` > CLASSPATH=`cygpath --path --windows "$CLASSPATH"` > fi > after setting classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-274) Upgrade to JLine 2.5
[ https://issues.apache.org/jira/browse/KARAF-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-274. Resolution: Fixed Revision 1034812. > Upgrade to JLine 2.5 > > > Key: KARAF-274 > URL: https://issues.apache.org/jira/browse/KARAF-274 > Project: Karaf > Issue Type: Improvement > Components: runtime >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.0 > > > In order to fix a stty parsing issue on Linux, a new JLine 2.5 version has > been provided. > We have to upgrade to this release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-274) Upgrade to JLine 2.5
Upgrade to JLine 2.5 Key: KARAF-274 URL: https://issues.apache.org/jira/browse/KARAF-274 Project: Karaf Issue Type: Improvement Components: runtime Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.2.0 In order to fix a stty parsing issue on Linux, a new JLine 2.5 version has been provided. We have to upgrade to this release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-288) Shell history doesn't work anymore (at leas on windows)
[ https://issues.apache.org/jira/browse/KARAF-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933771#action_12933771 ] Jean-Baptiste Onofré commented on KARAF-288: FYI, I've just made a try on Linux and Solaris. It's working fine. So it seems that the issue is Windows related. > Shell history doesn't work anymore (at leas on windows) > --- > > Key: KARAF-288 > URL: https://issues.apache.org/jira/browse/KARAF-288 > Project: Karaf > Issue Type: Bug > Components: console >Affects Versions: 2.2.0 > Environment: Windows 7 >Reporter: Achim Nierbeck > > With the latest version from svn, the shell history (key-up) doesn't work > anymore, at leas on windows right now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-244) features-maven-plugin does not work with maven 3
[
https://issues.apache.org/jira/browse/KARAF-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-244:
--
Assignee: Jean-Baptiste Onofré
> features-maven-plugin does not work with maven 3
>
>
> Key: KARAF-244
> URL: https://issues.apache.org/jira/browse/KARAF-244
> Project: Karaf
> Issue Type: Bug
> Components: tooling
>Affects Versions: 2.1.0
>Reporter: Bengt Rodehav
>Assignee: Jean-Baptiste Onofré
>
> Now that maven 3 has been released, I think it is important to get the
> features-maven-plugin to work under maven 3. The problem is that you normally
> use "mvn:" url's in the features-maven-plugin, e g:
>
>
>
> org.apache.karaf.tooling
> features-maven-plugin
>
>
> add-features-to-repo
> generate-resources
>
> add-features-to-repo
>
>
>
>
> mvn:org.apache.karaf/apache-karaf/${karaf-version}/xml/features
>
>
> ssh
> management
> webconsole
>
>
> ${project.build.directory}/features-repo
>
>
>
>
> But the url handler for "mvn:" does not work under maven 3 due to changes in
> the classpath handling. An alternative must be developed. I've noticed on the
> ops4j mailing list that something called pax-url-aether is in the works.
> Maybe that's an option for features-maven-plugin?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (KARAF-5) [karaf] admin:create should support a -r, --rmi-registry-port option to allow the RMI registry port to be configured
[ https://issues.apache.org/jira/browse/KARAF-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5 started by Jean-Baptiste Onofré. > [karaf] admin:create should support a -r, --rmi-registry-port option to allow > the RMI registry port to be configured > - > > Key: KARAF-5 > URL: https://issues.apache.org/jira/browse/KARAF-5 > Project: Karaf > Issue Type: Improvement >Reporter: Eoghan Glynn >Assignee: Jean-Baptiste Onofré > > By default the JMX/RMI serviceURL is configured for child instances with the > same RMI registry port as the root instance. > As a result, the monitoring of the child can depend on the live-ness of the > root instance, depending on the startup sequence. > For example if the child is created via "admin:create foo" in the root's > shell, but then started via the $KARAF_HOME/instances/foo/bin/start script, > the child shares the single RMI registry hosted by the root instance. > If the root instance is then stopped, the child may no longer be monitored > over JMX. Even if the root is restarted, the child still cannot be monitored > as there is no auto-reregistration. > Instead it should be possible to create a child instance with an > instance-specific RMI registry port so that its not dependent on an RMI > registry shared with another instance, e.g. "admin:create --rmi-registry-port > 1199 foo" so that rmiRegistryPort=1199 > is configured in > $KARAF_HOME/instances/foo/etc/org.apache.felix.karaf.management.cfg -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
