Community
Participate
Working Groups
I20030916 Scenario: I added a breakpoint (==> marker) to A.java in project A. When running my program it stopped but then asked me which file to open since there was another B/A.java in my workspace. Why showing that dialog if it is clear that only A/A.java has a breakpoint marker while B/A.java hasn't? Couldn't we make source look up for breakpoints in *.java files smarter? I understand that this (i.e. breakpoint) is a special case but it would be nice this case would be better supported.
Just a question - are both A.java's on your buildpath? What type of launch config/source locator was involved (i.e. was it a runtime workbench, a custom source lookup path, etc)?
>are both A.java's on your buildpath? yes What type of launch config/source locator was involved (i.e. was it a runtime workbench, a custom source lookup path, etc)? default runtime-workbench
Ah- I guess since each plug-in has their own classloader, this will still work. I.e. plug-in ONE will find it's A, and plug-in TWO will find it's A.
Deferred
This is actually a PDE issue (and might be a dup of an existing bug). I think PDE was investigating source lookup based on runtime bundle information which would solve the problem.
moving to PDE for comment.
we're using bug 65164 to track ideas/progress on a revolutionary source lookup for PDE. *** This bug has been marked as a duplicate of 65164 ***
