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 159634 - Project classpaths not differentiated by directory
Summary: Project classpaths not differentiated by directory
Status: RESOLVED WONTFIX
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: rmichalsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 19:53 UTC by _ tboudreau
Modified: 2009-11-02 11:01 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 _ tboudreau 2009-03-04 19:53:18 UTC
I have two copies of the same non-nbsrc NetBeans module open.  One is a checkout from an SVN server of its current
contents.  The other is a copy with modifications which I recovered after a disk crash.

In the old copy exists
public abstract class JCProject { ... }

In the new copy exists
public class JCProject { ... }

When I invoke a constructor in the copy with modifications
new JCProject();

I get the hint Implement all Abstract Methods - the hint is getting its metadata from the wrong copy of the project.

This also affects debug info, and I've been having problems with exceptions thrown from lines that, when I search for
them, are javadoc comments.  Something about the way NB project class metadata is stored does not include tracking the
path of the project.
Comment 1 Jesse Glick 2009-03-04 19:57:49 UTC
Tim, use the NetBeans Project Metadata Inspector (dev AU) to get proper diagnostics.
Comment 2 rmichalsky 2009-03-05 09:43:20 UTC
Could you also try if the order of opening the projects affects the behavior?
Comment 3 rmichalsky 2009-04-09 15:19:51 UTC
A rare scenario.
Comment 4 Quality Engineering 2009-11-02 11:01:53 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX