Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12087

JDS5 beta 3 crashes when importing JBoss AS 7.1.1.Final Maven project

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 3.3.0.CR1
    • None
    • maven
    • None
    • Hide

      git clone git://github.com/jbossas/jboss-as.git jboss-as
      cd jboss-as
      git checkout 7.1.1.Final
      ./build.sh
      mvn dependency:sources
      mvn dependency:resolve -Dclassifier=javadoc

      then launch jbdevstudio with a new blank workspace then:

      File->Import
      Maven -> Existing Maven Projects

      Browse for your jboss-as dir with a checked out copy of 7.1.1.Final in it. Wait while JBDS5 analyses each POM. Proceed to import all modules.

      You will be prompted with the warning:

      "No marketplace entries found to handle javacc-maven-plugin:2.5:jjtree-javacc in Eclipse. Please see Help for more information."

      regarding cmp/pom.xml. The action proposed is "Resolve Later". Click "Finish"; you don't care if the project doesn't build right now, you just want to import it.

      The import will begin and the modules will show up in the workspace's projects list, but the UI will be non-responsive except for the moving progress bouncer at the bottom-right and a percentage completion marker labeled "Importing maven projects...". This will reach somewhere between 93% and 98% before ceasing to advance.

      At this point behavior varies.

      Sometimes a dialog will appear entitled "Problem Occurred" with the text:

      "'Importing maven projects' has encounted a problem."
      "An internal error occurred during "Importing Maven Projects""
      "[<< Details] [OK]"
      "An internal error occurred during "Importing maven projects". java.lang.NullPointerException"

      The first few times I saw this dialog I wasn't able to get the detail part because it wasn't responding to mouse input.

      Sometimes, after some minutes or hours the frame of a dialog may appear overlaid over jbdevstudio with no content in it. Sometimes this dialog gets content (though still no title bar) reading:

      "An internal error occurred while showing an internal error."
      "You are recommended to exit the workbench"
      "Subsequent errors may happen and may terminate the workbench without warning."
      "See the .log file for more details."
      "Do you want to exit the workbench?"
      "[Yes] [No]"

      At least on my Gnome 3 Shell system the dialog is not responsive to mouse input. In my most recent trial with an import of only a subset of AS7 I was able to dismiss it with the escape key; on previous occasions it's been totally nonresponsive or blank.

      Show
      git clone git://github.com/jbossas/jboss-as.git jboss-as cd jboss-as git checkout 7.1.1.Final ./build.sh mvn dependency:sources mvn dependency:resolve -Dclassifier=javadoc then launch jbdevstudio with a new blank workspace then: File->Import Maven -> Existing Maven Projects Browse for your jboss-as dir with a checked out copy of 7.1.1.Final in it. Wait while JBDS5 analyses each POM. Proceed to import all modules. You will be prompted with the warning: "No marketplace entries found to handle javacc-maven-plugin:2.5:jjtree-javacc in Eclipse. Please see Help for more information." regarding cmp/pom.xml. The action proposed is "Resolve Later". Click "Finish"; you don't care if the project doesn't build right now, you just want to import it. The import will begin and the modules will show up in the workspace's projects list, but the UI will be non-responsive except for the moving progress bouncer at the bottom-right and a percentage completion marker labeled "Importing maven projects...". This will reach somewhere between 93% and 98% before ceasing to advance. At this point behavior varies. Sometimes a dialog will appear entitled "Problem Occurred" with the text: "'Importing maven projects' has encounted a problem." "An internal error occurred during "Importing Maven Projects"" " [<< Details] [OK] " "An internal error occurred during "Importing maven projects". java.lang.NullPointerException" The first few times I saw this dialog I wasn't able to get the detail part because it wasn't responding to mouse input. Sometimes, after some minutes or hours the frame of a dialog may appear overlaid over jbdevstudio with no content in it. Sometimes this dialog gets content (though still no title bar) reading: "An internal error occurred while showing an internal error." "You are recommended to exit the workbench" "Subsequent errors may happen and may terminate the workbench without warning." "See the .log file for more details." "Do you want to exit the workbench?" " [Yes] [No] " At least on my Gnome 3 Shell system the dialog is not responsive to mouse input. In my most recent trial with an import of only a subset of AS7 I was able to dismiss it with the escape key; on previous occasions it's been totally nonresponsive or blank.
    • Workaround Exists
    • Hide

      As a workaround, before importing the JBoss AS projects, m2e-apt needs to be disabled in the workspace preferences.

      • Window > Preferences > Maven > Annotation Processing
      • select "Do not automatically configure/execute Annotation Processing from pom.xml"
      Show
      As a workaround, before importing the JBoss AS projects, m2e-apt needs to be disabled in the workspace preferences. Window > Preferences > Maven > Annotation Processing select "Do not automatically configure/execute Annotation Processing from pom.xml"

      When attempting to import JBoss AS 7.1.1.Final, checked out from git, as a Maven project into JBoss Developer Studio 5.0 beta 3 on an x64 Fedora machine with JDK7, JBoss Developer Studio becomes unresponsive partway through the import. It sometimes then fails with an error message, and sometimes just ends up stuck in what appears to be some kind of infinite loop until killed.

      I haven't installed any add-ons or extras, it's stock JBoss Developer Studio 5.0 Beta 3.

      I've tried increasing the memory parameters from the already generous initial allocations to:

      -Xms512m
      -Xmx1592m

      with no improvement. I have 8GB to play with so I'll be throwing a ridiculous amount of RAM at and trying again, but this should not be necessary in any case, not just to import a maven project, even a big one.

      All I'm trying to do is import AS7 so I can add the AS7 project to the source search path when debugging a test case that's triggering a bug in AS7, so I don't have to manually add each and every source jar from as7 to my source search path. This seemed like the easy way to do it.

        1. import-error-log.log.gz
          145 kB

              fbricon@redhat.com Fred Bricon
              ringerc_jira Craig Ringer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: