Community
Participate
Working Groups
The version of AJDT installed through Eclipse Software Update via http://download.eclipse.org/tools/ajdt/34/update is not working for my project. Whenever I try to build the project, the build just stalls with the message "Invoking AspectJ Builder". The CPU utilization of the Eclipse process is close to 0%, if it does matter. The last version of AJDT that worked for me is 1.6.0.200807041530. After that, any version of AJDT I tried to install exhibited the same "hang" behavior.
Can you please attach a test case or a project that exhibits the behavior you are describing? I will look into it.
Still a problem?
We have found the workaround for this issue. Problem was that we have Perforce plug-in installed and 'class' files are generated in the subfolder 'classes' of the project folder. Perforce plug-in tried to check-out all 'class' files whenever AJDT was called, even though these are not in the Perforce repository. It lead to the very long waiting times. The workaround is adding the pattern '*/classes/*' into 'Ignored resources' tab of Perforce preferences.
Would it have made any difference if files in the classes folder were marked as "derived"? Currently, AspectJ does not do this, but there is a bug 258325 on AspectJ for this to happen.
If marking resources as 'derived' would allow Perforce plug-in recognize them as 'non-addable' to the Perforce repository, then yes, it should help.
It's a conjecture, really. Could you try it out by marking one of the 'classes' folders as derived and see if perforce still tries to add it? Then we can be certain that the proposed fix will work.
Yes, it did work. I marked 'classes' folder as 'Derived' in 'Project Explorer'. After that, I was be able to build the project. The problem starts again when I use 'Clean Project' command. The 'classes' folder gets deleted by Eclipse. The newly created 'classes' folder is not marked as 'Derived'. Even though I can build the project the first time after 'clean', invoking the 'clean' command again does hang Eclipse as before.
Good, then we can be sure that this bug depends on bug 258325. Thanks for looking into this.
The fix is in head and available from this update site: http://download.eclipse.org/tools/ajdt/34/dev/noweaving Will move it over to the jdt weaving branch soon. I believe that this will solve your problem because now all build artifacts are marked as derived (but not the output folder itself). This is mimicking the behavior of JDT. Would you please try it out and let me know if it is working for you?
*** Bug 261009 has been marked as a duplicate of this bug. ***
This fix has been committed to head and addresses the bug.
