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 57138 - Initializing scaning classpath on building project
Summary: Initializing scaning classpath on building project
Status: CLOSED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-29 15:30 UTC by pzajac
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 pzajac 2005-03-29 15:30:00 UTC 
[200503281900]
Steps to reproduce:
1) Create javaproject with few classes. 
2) Add some jar libraries to project. 
3) Build the project.
4) Explore the folders with built classes in Filesystem view
5) Clean and build the project - shows Initializing scaning classpath on every time
Comment 1 Martin Matula 2005-03-30 11:42:02 UTC 
This is as designed - if you are browsing through the produced jar file, we have
to update metadata for it when it changes.
Comment 2 pzajac 2005-03-30 11:55:00 UTC 
The scanning classpath dialog is also shown during building when the the built
classes are explored in filesystem view and Project view is active. IHMO it is
quite disturbing for developers. There exist some usecases why I want to look to
 built classes. For example I copy resource files from src folder in my custom
ant task. And I want to check if the files are correctly copied.
Comment 3 Jan Becicka 2005-09-02 15:08:00 UTC 
It is as designed. These classes are not scanned on startup, but on demand. We
want to work it this way.
Comment 4 pzajac 2005-09-05 08:57:53 UTC 
v
Comment 5 Quality Engineering 2007-09-20 10:52:52 UTC 
Reorganization of java component