Community
Participate
Working Groups
Eclipse 3.0 separates the notion of a task from a problem. The AJDT builder classifies TODO tasks as problems.
Created attachment 9431 [details] Changes Log, based on AJDT 1.1.7 CompilerMonitor now checks if warning message begins with TODO. If yes, the marker created is of type TASK. Otherwise it creates, as before the patch, a PROBLEM marker. Version: AJDT 1.1.7, Eclipse 3.0 M8
This sounds like a good step, although from the description it won't work with user-defined task tags (e.g., RBTODO: or FIX:). It also would get confused by declare warning/error messages that start with TODO (which isn't terribly important).
You are right Ron. But without a AJ compiler change we don't have much info to differentiate between warnings coming back from the compiler and TODOs. The lancaster codebase, which doesn't use AJDE, won't have this problem. The best we *could* do right now is query the platform to determine the set of user defined task prefixes and any warnings coming out of the compiler that start with those prefixes are converted to TASKs.
Upon investigation Luzius's patch already looks for user defined tags, so the only remaining problem is declare warning or declare error statements that start with the same string as the name of a task tag. The org.aspectj.bridge.IMessages passed to the CompilerMonitor from the AspectJ compiler have the kind WARNING for both warnings and tasks. For tasks they should probably have the kind INFO. This therefore looks like an AspectJ bug so I am transferring the bug report.
I've checked in the AspectJ side of this just now - so messages of kind TASKTAG will come out of AspectJ now when compiling. I have a patch from Sian to do the AJDT thing which I'll apply next time I build ajde.
this is fixed on the aj side...will be in M3.
This bug was fixed in June!
