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 9167 - deleting a class in the explorer window should delete the corresponding class file...
Summary: deleting a class in the explorer window should delete the corresponding class...
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P4 normal (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-01-19 21:11 UTC by athompson
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

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 athompson 2001-01-19 21:11:33 UTC 
...as well as the java file.  it does not if you use the cross-directory
compiler. at the least it should prompt you to delete it.
Comment 1 Jesse Glick 2001-01-22 16:56:59 UTC 
Not possible to fix. If cross-directory compilation were implemented differently
(using MultiFileSystem, technically) then it would work automatically, but as is
this is not possible--the .java file does not "know" anything about its .class,
it is the compiler which does the magic.
Comment 2 athompson 2001-01-22 18:19:59 UTC 
in the development version, there is native support for the cross-directory
compiler.  since the class path is stored in the 'target' property (in project
settings-->compiler types), and the package information can be obtained from the
java file to be deleted, this information can be used to determine where the
class file resides.  it is indeed not a very elegant solution, but one that will
work until a better fix can be devised.
Comment 3 Jan Chalupa 2001-03-12 10:46:19 UTC 
Version: 'Dev' -> 3.2
Comment 4 Svata Dedic 2001-04-06 18:49:49 UTC 
Because of other changes, the java source object is (or should be) now aware 
of all its .class files, regardless of where they are. Should work in the 
latest 3.2 builds, reopen if it does not.
Comment 5 Jan Becicka 2001-04-09 16:47:54 UTC 
[release32-23] Verified
Comment 6 athompson 2001-04-13 23:51:25 UTC 
please see bug 11422
Comment 7 Jan Chalupa 2001-05-05 23:24:16 UTC 
Target milestone -> 3.2
Comment 8 Quality Engineering 2003-07-01 13:18:42 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 9 Quality Engineering 2007-09-20 10:27:34 UTC 
Reorganization of java component