Bug 363512 - [console] [source lookup] Java stack trace console links to class files
Summary: [console] [source lookup] Java stack trace console links to class files
Status: CLOSED DUPLICATE of bug 348507
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7.1   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 13:12 EST by elatllat CLA
Modified: 2011-11-14 06:10 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description elatllat CLA 2011-11-10 13:12:00 EST 
Build Identifier: M20110909-1335

this did not happen in previous versions.
the search is not honoring the "order and export" list.
so if you add a class folder to the libraries with some classes overlapping the java files in the project the Java stack trace console links to the .class instead of the .java

Reproducible: Always

Steps to Reproduce:
1.make a project with some java files in it
2.add a class folder to the libraries with one class that overlaps a java
3.paste in a stack trace with that class and it will link to the wrong file
Comment 1 Markus Keller CLA 2011-11-11 11:09:18 EST 
It depends on the ordering of the build path. If the class folder is in front of the source folder, then the .class file is the right one.
Comment 2 elatllat CLA 2011-11-11 11:19:38 EST 
(In reply to comment #1)
> It depends on the ordering of the build path. If the class folder is in front
> of the source folder, then the .class file is the right one.

Hi Markus,
thanks for the comment
As I said it is not honoring the "order and export" list.
The class folder is after the source folder.
(it obviously would not have worked in previous versions if this were not the case)
Comment 3 Markus Keller CLA 2011-11-14 06:10:22 EST 
This should be fixed in 3.8 builds, see bug 348507.

*** This bug has been marked as a duplicate of bug 348507 ***