[jbosstools-issues] [JBoss JIRA] (JBIDE-12087) JDS5 beta 3 crashes when importing JBoss AS 7.1.1.Final Maven project

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698592#comment-12698592 ] 

Snjezana Peco commented on JBIDE-12087:
---------------------------------------

The described issue happens on both Windows and Linux when m2e-apt is present. Can't be reproduced in Eclipse/WTP/m2e.
The NPE is just one of the issues in m2e-apt.

There are also the following issues:

- when using JDK as a JRE container, m2e-apt will enable apt for every maven java project. It will find META-INF/services/com.sun.mirror.apt.AnnotationProcessorFactory in the JDK's tools.jar and enable apt. All the jboss-as7 projects imported using JBDS 5.0.0.CR1 will have apt enabled and .factorypath added.
The "javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__SAXParserFactory not found exception" exception is caused by this issue.
- another issue is related to performance. m2e-apt searches all jars in the project's classpath in order to find META-INF/services/com.sun.mirror.apt.AnnotationProcessorFactory or
META-INF/services/javax.annotation.processing.Processor (see the ProjectUtils.containsAptProcessors() method). This is called once or twice for every maven change listener which significantly affects performance. I think m2e-apt would need to use a classloader (that doesn't lock jars as in https://issues.jboss.org/browse/JBIDE-1012). We would also need to have a possibility to disable m2e-apt. 

m2e-apt can be removed from JBDS only by editing the bundles.info file.
                
> JDS5 beta 3 crashes when importing JBoss AS 7.1.1.Final Maven project
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-12087
>                 URL: https://issues.jboss.org/browse/JBIDE-12087
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>         Environment: $ uname -a
> Linux ichindar.localdomain 3.3.7-1.fc17.x86_64 #1 SMP Mon May 21 22:32:19 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> $ lsb_release -a
> LSB Version:	:core-4.0-amd64:core-4.0-noarch
> Distributor ID:	Fedora
> Description:	Fedora release 17 (Beefy Miracle)
> Release:	17
> Codename:	BeefyMiracle
> $ java -version
> java version "1.7.0_b147-icedtea"
> OpenJDK Runtime Environment (fedora-2.1.fc17.6-x86_64)
> OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
>            Reporter: Craig Ringer
>            Assignee: Fred Bricon
>             Fix For: 3.3.0.CR1
>
>         Attachments: import-error-log.log.gz
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira