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.
In order to get back the 3.x behaviour where compiled classes were placed in the source code directory, I changed "build.classes.dir" and "build.dir" to the source directory. Executing "Clean and Build (Shift-F11)" resulted in all files in the source code directory being lost. Perhaps the build process should only delete files that can be compiled by it.
Duplicate of something? Not sure.
This is not supported case. The build directory has to differ to the source root. In the NetBeans 4.1 there are more source roots in the single compilation unit, so build dir == src.dir does not work at all.
Changing to Enhancement, because I think that it could happend to somebody who is used to compile to source dir. There might be some test that would disable clean actions if those two properties point to the same folder or something like that.
If you have to work together with Eclipse users via CVS/SVN you either have to compile to the source dir or have to copy all media files referenced in your classes from the source dir to the build dir every time you check out. At least I found no other solution. So compiling to source dir should be an option.
Eclipse cannot do compilation to build directory? OK, it is possible to do it in NetBeans (needs to rewrite the clean target), but it will look strange.
Maybe Eclipse can compile to build dirs, but the developers I know (and work with) compile to the source dir. I prefer seperate build dirs, too, but don't want to hassle around with copying files forth and back when working with Eclipse users. Imho the Clean target should never delete files which are not built by Netbeans. Limiting it to class (and other?) files would be safer. Perhaps it should only include class files with corresponding source files. This would prevent one from deleting third-party classes in the build dir which won't be built by Netbeans. I'm wondering why I'm the only one affected by this behaviour.
Most of users are using separated src and build dir. The most Ant script's clean target simply deletes the build folder. Deleting only class files which were compiled from the java files will need a custom ant task. It is problematic for users which require headless build (eg. automatic builds)