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

[ https://issues.jboss.org/browse/JBIDE-12087?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-12087: --------------------------------------- {quote} Referencing the JDK in the factory path is irrelevant to that bug. {quote} I have said this bug is caused by adding jars from the classpath to .factorypath. This way the project's classpath is included in the OSGi classpath so that the problem happens in many places. The problem with jboss-as7 is only one of them. {quote} As for all the jars being put to the factory path, I haven't found a better way : CLI builds use all the APs found in the project classpath, and we have no way to know what jars are irrelevant to annotation processing. If you have any suggestions to improve the current implementation, I'm all ears. {quote} You can't use the same technique in the Eclipse environment as in CLI. CLI has only one classloader when compiling a project. Eclipse's plugins have their own classloaders. Adding all project's jars to .factorypath will cause different issues because annotation processing happens in the context of the Java builder. The Eclipse apt is a Java compiler participant. Beside, in most of the cases the user won't use all the annotations processors defined on the classpath. Annotation processing decreases performance of the Java builder. Annotation processors are being added only if they are necessary. I suppose that is the main reason why it isn't added to Eclipse automatically. Why would somebody, for instance, add apt from tools.jar if he doesn't use JDK's jaxrs services. In my opinion, it would be the best to enable APT when existing .factorypath in the project's root because we can't know when APT is required and what jars need to be added to .factorypath. This idea coming from WELD-835. Since .factorypath is already defined, you don't have to regenerate it. Re the workaround I propose m2e-apt to be disabled by default. Otherwise, there will be different issues in Eclipse/JBT/JBDS because of incorrectly defined .factorypath. JBoss AS 7 is just an example Craig found. -- 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