You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2010/08/26 15:23:53 UTC
[jira] Resolved: (KARAF-169) Do not use the ClassPath manifest
header for the karaf client jar
[ https://issues.apache.org/jira/browse/KARAF-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved KARAF-169.
-----------------------------------
Assignee: Guillaume Nodet
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/karaf/trunk ...
M assembly/src/main/descriptors/unix-bin.xml
M assembly/src/main/descriptors/windows-bin.xml
A assembly/src/main/filtered-resources/bin/client
A assembly/src/main/filtered-resources/bin/client.bat
M client/pom.xml
Committed r989671
> Do not use the ClassPath manifest header for the karaf client jar
> -----------------------------------------------------------------
>
> Key: KARAF-169
> URL: https://issues.apache.org/jira/browse/KARAF-169
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.0.0
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 2.2.0
>
>
> The original problem is that commands don't work anymore in Equinox.
> The reason is that gogo classes are now included in the karaf.shell.console artifact which is put in the main classloader because it is referenced from the karaf-client manifest. This problem only appear on Equinox though.
> Anyway, using a script to launch the client might be a better idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.