Nope. These are all fine. The model checker is being too aggressive in what it flags. Thanks for bringing it to our attention. I'll tweak the model checker to be a bit more conservative.
On Sat, Feb 7, 2009 at 4:05 PM, Johan Fabry <[email protected]> wrote: > Hi Andrew, all, > > good news and maybe bad news... > Good news: the new version of AJDT seems to have solved my NPE problems on > on AJCodeElement.getNameRange. Next week I'll do some more tests to make > *really* sure. > > Maybe bad news: the event trace view has some things to say on the spacewar > example, many times "Java Element is wrong type (advice relationships should > not contain any types or compilation units)". See file in attachment. > > > > > > On 04 Feb 2009, at 18:10, Andrew Eisenberg wrote: > >> There have been a few posts to these mailing lists about problems with >> the crosscutting model (eg- navigation and the crosscutting view). >> Most situations seem to be fine, but there may still be some corner >> cases where gutter markers are not being properly placed. >> >> I just added a simple sanity check on the model that runs after the >> build (actually, it only runs if the AJDT Event Trace View is open, >> otherwise it doesn't waste time running). I hope that this will help >> diagnose any issues found. >> >> So, if you are noticing any oddness with your crosscutting model, >> please update to the latest dev version of AJDT, restart, open up the >> AJDT Event Trace View, and do a full build. >> >> Please report any results back to this list. >> >> thank you, >> --andrew >> _______________________________________________ >> aspectj-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/aspectj-users > > -- > Johan Fabry > [email protected] - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
