[ BUILD # : 200409100847 ]
[ JDK VERSION : J2SE 1.5.0 ]
This is what happen when you...
1) Rename a class. Build folder ends up with two
classes, that one with the new name and the old
2) Move a class. Build folder gets the new copy,
but never deletes the old one.
3) Delete a class. It's never deleted in build
Current workaround is to Clean & Build, but for
large projects with large dependencies takes long
There are some scenarios where not cleaning Java
classes has great repercussion. Factories whose
implementations are expected in some folder and
plugins, which use to be located in a particular
folder. In both cases, NB will make available
classes that weren't supposed to be there.
Changing category to java/project - that's probably closest.
Sorry, this is what Clean & Build is for. If you don't want to rebuild
subprojects, you can disable that in project properties.
Yes Jesse, but this behavior is counterintuitive. Mostly because other
actions, like creating and modifying, behave as expected, that is,
keeping build folder synchronized.
About cleaning or not required projects, is not a forever yes-or-not
decision. I found much more accurate to propagate the action across
required projects, but performing a clean because the above mentioned,
may lead to cleaning more that often.
Or you want me to keep in mind whether a have deleted/moved/renamed a
file in order to execute Clean & Build next time I want to Build, want
old tagret milestone, please re-evaluate
As for me, it works quite well in NB4.1. Maybe is a little ugly letting the *.*~
files undeleted in web|src folder. Also, when moving a JSP a got my_jsp.jsp~
duplicated (origin and destination)