Community
Participate
Working Groups
Build ID: 20090619-0625 Steps To Reproduce: 1. Create AspectJ project with aspect: declare error : call(* *.*(..)): "test message"; 2. Create Java project with one class and one method. Add dependency to it to AspectJ Inpath of first project -> Problem view updates, with one error on correct resource. You can double-click and navigate to correct resource. 3. Add yet another Java project. Add it to Build path of AspectJ project -> Problem view still has one item, but you can not navigate to resouce and path column is empty. More information: Reproduces on AJDT 2.0.0 and 2.0.1.e35x-20090727-2200 In scenario above org.eclipse.ajdt.internal.ui.ajde.UIMessageHandler.locationToResource returns null, but ISourceLocation isl parameter seems to be correctly initialized. I think that this this call is not working: if (ir == null) { // try any project ir = AJDTUtils.findResource(loc); So locationToResource returns null and this seem to cause the problem
Thanks for the report and the suggested location where things are going wrong. I will have a look at this in the next few days. I am actually surprised that navigation is working at all between projects for declare warning/error.
Created attachment 143328 [details] Bug fix This patch fixes the problem, org.eclipse.ajdt.internal.ui.ajde.UIMessageHandler.tryToFindResource method was not returning not null value.
Thanks for the patch. I'll have a look at it later this week.
Patch has been applied and your test case is working. I am now using it as a regression test. Will be available in the next dev build of the 3.5 stream. However, that may not come out for another few days.
