Karaf
  1. Karaf
  2. KARAF-169

Do not use the ClassPath manifest header for the karaf client jar

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.1.0
    • Component/s: karaf-core
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Guillaume Nodet added a comment -

        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

        Show
        Guillaume Nodet added a comment - 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

          People

          • Assignee:
            Guillaume Nodet
            Reporter:
            Guillaume Nodet
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development