Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-459

Incompatible/Duplicate excalibur-cli-1.0.jar library in classpath

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: 2.3.0
    • Component/s: None
    • Labels:
      None

      Description

      We have to different excalibur-1.0.jar files in our classpath: phoenix-bin/lib/excalibur-1.0.jar and phoenix-bin/bin/lib/excalibur-1.0.jar
      The correct one seems to be the /bin/lib version.

        Activity

        Hide
        brainlounge Bernd Fondermann added a comment -

        that's right, phoenix-bin/bin/lib/excalibur-cli-1.0.jar is the right one to not let the stacktrace in question appear - but it does not get loaded, even if /lib/excalibur-cli-1.0.jar is removed. only moving jar from bin/lib/ to lib/ fixes the problem.

        so the question comes up, if the bin/lib jars are needed at all!?

        BTW, the stacktrace in question is:

        Running Phoenix:
        There was an uncaught exception:
        ---------------------------------------------------------
        — Message —
        org.apache.avalon.excalibur.cli.CLOption.getDescriptor()Lorg/apache/avalon/excalibur/cli/CLOptionDescriptor;
        — Stack Trace —
        java.lang.NoSuchMethodError: org.apache.avalon.excalibur.cli.CLOption.getDescriptor()Lorg/apache/avalon/excalibur/cli/CLOptionDescriptor;
        at org.apache.avalon.phoenix.frontends.CLISetup.parseCommandLineOptions(CLISetup.java:202)
        at org.apache.avalon.phoenix.frontends.CLIMain.main(CLIMain.java:122)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.avalon.phoenix.launcher.Main.startup(Main.java:128)
        at org.apache.avalon.phoenix.launcher.Main.main(Main.java:83)

        Show
        brainlounge Bernd Fondermann added a comment - that's right, phoenix-bin/bin/lib/excalibur-cli-1.0.jar is the right one to not let the stacktrace in question appear - but it does not get loaded, even if /lib/excalibur-cli-1.0.jar is removed. only moving jar from bin/lib/ to lib/ fixes the problem. so the question comes up, if the bin/lib jars are needed at all!? BTW, the stacktrace in question is: Running Phoenix: There was an uncaught exception: --------------------------------------------------------- — Message — org.apache.avalon.excalibur.cli.CLOption.getDescriptor()Lorg/apache/avalon/excalibur/cli/CLOptionDescriptor; — Stack Trace — java.lang.NoSuchMethodError: org.apache.avalon.excalibur.cli.CLOption.getDescriptor()Lorg/apache/avalon/excalibur/cli/CLOptionDescriptor; at org.apache.avalon.phoenix.frontends.CLISetup.parseCommandLineOptions(CLISetup.java:202) at org.apache.avalon.phoenix.frontends.CLIMain.main(CLIMain.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.avalon.phoenix.launcher.Main.startup(Main.java:128) at org.apache.avalon.phoenix.launcher.Main.main(Main.java:83)
        Hide
        danny@apache.org Danny Angus added a comment -

        Closing issue fixed in released version.

        Show
        danny@apache.org Danny Angus added a comment - Closing issue fixed in released version.

          People

          • Assignee:
            bago Stefano Bagnara
            Reporter:
            bago Stefano Bagnara
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development