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 40949 - [buildsys] Library marked by error annotation
Summary: [buildsys] Library marked by error annotation
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Tomas Zezula
Keywords: RANDOM
Depends on:
Blocks: 41537
  Show dependency tree
Reported: 2004-03-12 10:35 UTC by Milan Kubec
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2004-03-12 10:35:46 UTC
[Own stavbicka build, checkout of stavbicka and
trunk modules today morning, JDK 1.4.2_03]
I opened My App demo project and file and line:


was marked by error annotation with message:

Cannot access
Bad class file: null
Unable to access file: No such file or directory
Please remove or make sure it appears in the
correct subdirectory of the classpath.

My Lib project is opened too. Project can be
successfully built and also run.
Comment 1 Milan Kubec 2004-03-12 15:24:45 UTC
Doesn't happen when running IDE again with clean userdir.
Comment 2 David Konecny 2004-03-15 09:32:03 UTC
Milan, are you able to reproduce it somehow?
Comment 3 Milan Kubec 2004-03-15 10:09:52 UTC
Not really, happened just once.
Comment 4 Milan Kubec 2004-03-25 16:20:21 UTC
Happened to me again. The error message for affected import is now:
package org.mylibrary doesn't exist
Happened after creating project and then library, setting classpath of
project to depend on library after while of writing code I closed
library and used pop-up menu of the project to "Open required
projects". Then I started to write code again and the library gets
marked by error annotation. Project can be re/built and run
succesfully. This time I was running IDE on JDK 1.5.0 b42.
Comment 5 Jesse Glick 2004-05-11 00:47:41 UTC
Is this still true?
Comment 6 Milan Kubec 2004-05-11 08:14:03 UTC
I will take a look at it.
Comment 7 Tomas Zezula 2004-05-25 14:06:17 UTC
Can not reproduce, probably already fixed.
It may be also caused by the lib build product, which may not be up to
Comment 8 Milan Kubec 2004-07-12 12:47:33 UTC
Probably fixed.