This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 170457 - Wrong JDK sources used by debugger
Summary: Wrong JDK sources used by debugger
Status: CLOSED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-17 12:39 UTC by geofjamg
Modified: 2010-05-06 11:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description geofjamg 2009-08-17 12:39:24 UTC
2 JDK are defined in my Java Platform Manager : 1.6 which is the default one and 1.7 (from OpenJDK)
I created a java project where I changed the current java platform to 1.7.
When I debug this project et step into JDK classes, JDK 1.6 sources are displayed instead of JDK 1.7.
Comment 1 Martin Entlicher 2009-08-17 14:27:21 UTC
It works for me correctly. When I change project's platform, debugger opens the sources of the given platform. (In NB
6.7.1, but I believe that 6.7 also works this way).

What kind of projects do you have? I've tested J2SE projects created by NetBeans through:
New Project -> Java -> Java Application.
Comment 2 geofjamg 2009-08-17 18:45:54 UTC
I also have a J2SE project and I use the 6.7.1 NB version.
Comment 3 geofjamg 2009-08-17 20:38:28 UTC
I installed another JDK (1.5) and I have the same problem. I change project's platform to 1.5 and debugger still opens
the default JDK sources (which is 1.6 for me).
That's strange because navigation (Navigate -> Go to source) works fine.
Comment 4 geofjamg 2009-08-19 10:14:39 UTC
This bug is not present in the dev build (200908171401), but he is in the 6.7.1 (200907230233, up to date).
A correction should have already been done.
Comment 5 Vojtech Sigler 2009-09-18 09:11:20 UTC
Since this is already fixed in the dev build and it cannot be made into a patch (fix changeset unknown), marking as WONTFIX.
Comment 6 Marian Mirilovic 2010-05-06 11:51:36 UTC
closing incomplete issues