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.
Development build of NetBeans 3.3 #200109030100 on Windows 2000 with JDK 1.3.1 Description: ============ It is interesting but due to some reason there is backup file created immediate- ly when generating it from template under CVS filesystem mounted using Built-in Client. These files are then stated in filesystem as [Local]. Steps to reproduce: =================== 1. Mount CVS filesystem using Built-in Client. 2. Create new bean using "New|Beans|Bean" popup menu somewhere underneath. 3. Verify externally that in fact two files were created physically.
Reassigning to java (dunno if that's the best place though). When doing backups, I don't create a backup for files that don't exist, once the fileObject exists and it's outputstream is requested (to be saved) I create a backup. I found out that for creating new from template, the original template is stored first and then replaced with the right stuff.. the template thingie is then saved as backup.. This is what the files differ at: "package Templates.Classes;" <snip the rest>
Sorry, will not solve for 3.3: The template is instantiated (copied) on the disk first, then it is changed, reformatted, class is renamed and class members defined in the N.F.T. wizard are inserted. I plan to change this weird templatizing in 3.4/4.0
This is "as designed" for 3.3. Changing to a RFE. The solution depends on moving away from DataObject-bound services, so I will be linking more blockers for this to be implemented in the future.
The backup files are no longer created.