Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6347

JBoss Tools expects the Eclipse JDT Core jar from the Seam distribution to be in core.jar, but they are now in ecj.jar

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.1 ER1, EAP_EWP 5.1.1 ER3
    • Seam
    • None

    • eap 5.1.1 ER3, JBDS 4.0.0.GA

    • Hide

      1. in JBDS 4.0.0: File->New->Seam Web Project
      2. create a WAR project called NewWebProject using Seam runtime from EAP 5.1.1 ER1
      3. notice there is no core.jar, nor ecj.jar in the lib/ folder
      4. New -> Seam Action
      5. on the NewWebProject-test project, run as -> TestNG project
      6. Notice the exception

      Could not instantiate Seam component: org.jboss.seam.security.ruleBasedPermissionResolver
      ...
      Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath

      Show
      1. in JBDS 4.0.0: File->New->Seam Web Project 2. create a WAR project called NewWebProject using Seam runtime from EAP 5.1.1 ER1 3. notice there is no core.jar, nor ecj.jar in the lib/ folder 4. New -> Seam Action 5. on the NewWebProject-test project, run as -> TestNG project 6. Notice the exception Could not instantiate Seam component: org.jboss.seam.security.ruleBasedPermissionResolver ... Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
    • Release Notes
    • Workaround Exists
    • Hide

      Copy ecj.jar from seam/lib/ directory to your JBDS project NewWebProject/WebContent/WEB-INF/lib/:
      cp seam/lib/ecj.jar NewWebProject/WebContent/WEB-INF/lib/ecj.jar

      Show
      Copy ecj.jar from seam/lib/ directory to your JBDS project NewWebProject/WebContent/WEB-INF/lib/: cp seam/lib/ecj.jar NewWebProject/WebContent/WEB-INF/lib/ecj.jar
    • Hide
      Seam projects created using JBDS earlier than version 4.1.1 failed the test phase with the message:

      <screen>
      Could not instantiate Seam component: org.jboss.seam.security.ruleBasedPermissionResolver
      ...
      Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
      </screen>

      This error occurred because, since an upgrade of Drools to 5.1, functions required by JBDS which would previously been found in <filename>lib/core.jar</filename> are now contained in lib/ecj.jar. To workaround this problem, take one of the following options, with option 1 being the recommended option:

      <orderedlist>
        <listitem>
          <para>Upgrade JBDS to 4.1.1;</para>
        <listitem>
        <listitem>
          <para>Copying lib/ecj.jar to the project.</para>
        <listitem>
      </orderedlist>
      Show
      Seam projects created using JBDS earlier than version 4.1.1 failed the test phase with the message: <screen> Could not instantiate Seam component: org.jboss.seam.security.ruleBasedPermissionResolver ... Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath </screen> This error occurred because, since an upgrade of Drools to 5.1, functions required by JBDS which would previously been found in <filename>lib/core.jar</filename> are now contained in lib/ecj.jar. To workaround this problem, take one of the following options, with option 1 being the recommended option: <orderedlist>   <listitem>     <para>Upgrade JBDS to 4.1.1;</para>   <listitem>   <listitem>     <para>Copying lib/ecj.jar to the project.</para>   <listitem> </orderedlist>
    • Documented as Known Issue
    • NEW

    Description

      JBoss Tools expects the Eclipse JDT Core jar to be located in seam/lib/core.jar.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-6361 seam-gen NoClassDefFoundError: org/eclipse/jdt/core/ToolFactory

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1818 Seam in EAP 5.1.1 upgraded Drools libraries - update your Project wizards

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-6611 Seam-gen generated .classpath file for Eclipse contains missing libraries

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              mnovotny@redhat.com Marek Novotny
              maschmid@redhat.com Marek Schmidt
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: