• Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 4.1.0.Alpha1
    • Fix Version/s: 4.15.x
    • Component/s: maven
    • Labels:


      The PR includes the following enhancements:

      • AS 7.2/EAP 6.1 are now recognized correctly
      • the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
      • the fix for the ConcurrentModificationException exception
      • included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
      • JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
      • JBoss Java Project Source Container

      Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.

      You have to have some deployment on the servers in order the WeldBootstrap class to be created.
      You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
      The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  fbricon Fred Bricon
                  snjeza Snjezana Peco
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created: