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 128536 - NB55 compat: wrong Java Editor Code Hints
Summary: NB55 compat: wrong Java Editor Code Hints
Status: RESOLVED DUPLICATE of bug 105927
Alias: None
Product: java
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-27 10:22 UTC by ayermolayev
Modified: 2008-02-27 12:25 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 ayermolayev 2008-02-27 10:22:20 UTC
Java Editor displays wrong and misleading Code Hints, falsely reporting missing packages, symbols, variables etc.
The same project opened in NB55 does not display any wrong hints.

Missing package is reported every time, when it comes from a jar X, that is referenced in the "Class-Path" attribute 
of another jar Y. The jar Y is included in the library which is added to the project.
According to the Jar-File mainfest spec for the "Class-Path" attribute 
(http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Main%20Attributes) "The application or extension class loader 
uses the value of this attribute to construct its internal search path"

Obviously, the Editor just ignores the "Class-Path" attribute provided in the jar Y
Comment 1 ayermolayev 2008-02-27 10:36:18 UTC
Consequencely, Files and Packages windows display wrong information about the current compilation status of the 
corresponding folders and packages, falsely indicating that not all files/packages are compiled (while they actually 
are compiled).
Comment 2 Jan Lahoda 2008-02-27 12:25:27 UTC
Nothing wrong with the editor - the editor uses a classpath that is provided by the project type. Please see issue
#105927 for more details. BTW: when reassigning bugs, always use "Reassign issue to owner of selected subcomponent". Thanks.

*** This issue has been marked as a duplicate of 105927 ***