Hi all, I noticed a somehow bizarre behavior with eclipse 3.3.0 and ajdt 1.5.0. I reported this as a critical bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=201999 although from my point of view it's really a blocker. I managed to reproduce the problem in a small project:
- create a project - convert it to aspectj - add a new class - introduce an error in this class and save - clean the project output (from project/clean) - full build triggered - do a dummy change to the class that keeps the error - *full* build triggered - etc etc - then correct the error - full build triggered - do a dummy change to the class that doesn't introduce new errors - *incremental* build triggered - etc etc That is: there is a need to produce a class in the output folder correlating to every source file in order to get incremental builds. I suppose that otherwise aspectj can't find a previous successful full build. But this is too unrealistic an assumption, as most medium to big sized project present some compilation errors during development hours and probably at the end of the day too. Sometimes I do a svn checkout that introduces errors from inconsistencies between my colleagues work, maybe some outdated unit tests or something like that. I think it's nonsense to get these tests compiling at any cost just to force aspectj do incremental builds. Do you know of any sensible workaround? I'm seriously thinking about removing the aspectj capabilities from the project and use loadtime weaving plus annotated syntax on a plain java project. Thank you in advance. Regards, Carlos
_______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
