Community
Participate
Working Groups
For example for a maven generated eclipse project, where you have classes and test-classes output directories each by its own, any tiny change (even when it's done to a class that is not an aspect nor advised) triggers a full rebuild with the following log: 8:09:26 PM Build kind = AUTOBUILD 8:09:26 PM Project=cereza, kind of build requested=Incremental AspectJ compilation 8:09:26 PM build: Examined delta - source file changes in required project cereza 8:09:26 PM Preparing for build: not going to be incremental because path change detected (one of classpath/aspectpath/inpath/injars) 8:09:26 PM Falling back to batch compilation 8:09:26 PM Preparing for build: not going to be incremental because no successful previous full build ... If you change every project source folder to have the same output dir (for example the default one), the problem disappears.
This sounds familiar, I think this may have been fixed already. Please could you try with the latest development build to verify whether this is the case? Either: 1.4.2.200703020612 for Eclipse 3.2.2 or 1.5.0.200703300605 for Eclipse 3.3M6 Note that if you are on Eclipse 3.2 or 3.2.1 and wish to upgrade to the above version of AJDT 1.4.2, you need to first upgrade to Eclipse 3.2.2.
I've upgraded to eclipse 3.2.2 + ajdt 1.4.2 and now I get incremental builds as expected. So the bug report just applies to 1.4.1. Thank you Matt.
Ok, marking as fixed in 1.4.2
