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.
I'm using NetBeans IDE 5.0 (Build 200601251500) on Windows XP v5.1 on x86. The Template Manager has some shortcomings when Duplicating, Renaming or Adding templates. First, when using the Template Manager to Duplicate an existing template (e.g., the "Java Classes/Java Class" template), it doesn't allow me to enter a description for the duplicate template. Most of the templates that ship with NetBeans have a meaningful description for each template. The description shows up in the "New File" dialog at step 1 "Choose File Type". The Template Manager should allow me to set a meaningful description for my template -- similar to the templates that ship with NetBeans. Second, after the Duplicate function has been used, the template's filename is used as the template name in the dialog (e.g., for the "Java Class" template -- whose underlying filename is Class.java -- the duplicated template is called "Class_1.java"). This name cannot be renamed with a descriptive name that includes spaces (e.g., I want to call it "Java Class with Logging". Instead, the name must be the filename with no spaces (e.g., I have to call it something like "JavaClassWithLogging.java"). The Template Manager should allow me to set a meaningful name for the template -- separate from the filename -- similar to the other templates that ship with NetBeans. Third, the same issues happen when Adding a new template. The dialog does not let me set the description for the template and it won't allow me to set the name to something descriptive with spaces and without basing it on the filename and the file suffix. The Template Manager should allow me to enter a meaningful name and description of the template separate from its filename -- similar to the other templates that ship with NetBeans. Another related DEFECT issue (67545) has already been reported about the bug that the class name within the new template no longer matches the underlying filename, thus generating an error when trying to use the template. It doesn't look like anything is happening with that related issue.
Renaming and duplicating templates should work much better after core-main/rev/a678bf1ffb1b - check NetBeans 7.0 Milestone1 which is coming before end of this year.
Troubles while adding new templates were fixed in core-main/rev/e0dacb6e3de2