Fred Bricon
Fred Bricon
Thx for the pom. IM(F)O annotation processors are plugin dependencies, not project dependencies, hence my setup. But that would not change anything here. I don't believe I need to setup...
If the project is a regular java project (see below) , then annotation processing is properly configured. ``` 4.0.0 foo.bar test 0.0.1-SNAPSHOT org.apache.maven.plugins maven-compiler-plugin 2.5.1 1.6 1.6 com.googlecode.androidannotations androidannotations 2.5.1...
Using m2e 1.1 (http://download.eclipse.org/technology/m2e/milestones/1.1/) on Juno (should work on Indigo too), the test project from master is configured with JDT APT. I had to change the androidannotations dependencies to 2.5.1...
For the querydsl annotation processor, the problem comes from a limitation in Eclipse APT : as I explained in https://github.com/jbosstools/m2e-apt/issues/14#issuecomment-6327841 APs can only be detected if they're defined in `META-INF/services/javax.annotation.processing.Processor`...
They should actually split their querydsl-apt into 3 jars, one for each AP they provide. That way they could add one service provider per jar, without risking all APs to...
interesting. Thanks for the heads up
Indeed Eclipse JDT APT does not support loading APs from open Eclipse projects, there's nothing I can do to change that. Your best bet is to open the project containing...
Can you reproduce the issue in a clean workspace, only importing the offending project, or the whole clustering module?
Here's what I get when importing m2e-apt's test projects _as Maven projects_ from https://github.com/jbosstools/m2e-apt/tree/master/org.jboss.tools.maven.apt.tests/projects  http://content.screencast.com/users/fbricon/folders/Jing/media/7867f7a3-d4b7-4a20-98f6-3c214dbddfb7/00000018.png The discovery mechanism is not relying on the comment section in your pluginExecution...
So far I've been unable to reproduce the problem on win7 64 (eclipse running with JDK 1.7.0_10, project built with JDK 1.6.0_37), using JBDS 6.0.0 (based off eclipse 4.2.1). I'll...