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.
[release32 mar 31] After making a module JAR from template (e.g.), moving to a new folder in Explorer (Cut & Paste), and then compiling it: the actual *.jar is created in the old folder. IMHO the .jar location should be updated automatically when the .jarContents is moved, otherwise the user has to do it.
The location of the jar file is a property of the jar content file. While by default they are the same except for the extension, this is not necessarily true. The proper rule is probably: if a jarcontents is moved then if the jar file's name differed only by extension then change it else leave it alone end if end if
I agree, that sounds like the proper rule. Most users will just make a JAR from template and may never notice/care that they can set the location, so the normal behavior should assume they want to keep the two together.
If the jar cntents file and jar file are brothers (same folder, same name, both use default extensions), they will now stay brothers through move, copy, and rename.
Target milestone -> 3.2
Verified
Resolved for 3.4 or earlier, no new info since then -> closing.