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.
NB4.0 doesn't permits user to create a enum via the wizard.
Yes, we should add such template.
Dusane, please provide an enum template + *description*. proposed template: /* * __NAME__.java * * Created on __DATE__, __TIME__ */ package Templates.Classes; /** * * @author __USER__ */ public enum Class { }
We should add templates for enum and annotation type. Honzo, could you do it?
Sure, I could. Dusan, will you supply the stuff requsted by Jan B.?
Just a stupid question ? Why is target now 4.1 ? Is it really not possible for 4.0 ? It's only a template file to create. (and proposed template is proposed in the issue) No code to modify. No wizard to create. Or am I wrong ?
see http://www.netbeans.org/community/releases/40/high-resistance.html. It is impossible to add new features to 4.0 now.
That issue was created the 5 Septembre 2004. The template was given the 6 Septembre 2004. And now, 2 months later, you say that it can be delivered with NB4.0 because we are in High Resistance Mode ? Come on. I really hope you are kidding. Is creation of a template file really considered as a feature ? It's only a) adding a plain text file in the good repository (org.netbeans.modules.java.resources.templates.Enum.template and b) add an entry in the .properties file to have help (org.netbeans.modules.java.Bundles.properties) No lines of code is modified. When we are un HRM, I can understand that no creation/modification of .java files has to be done. Only Bug Fixing. But, is creation of a template file would be considered as Java code enhancement ? I think that creation of template files would be considered as creation of Help pages. And creation of HTML Help pages are accepted even in High Resistance Mode. Just my feeling. Maybe I am totally wrong.
Vincent, I am sorry for this. This issue was assigned to a UI engineer and got lost in the tons of defects we had to fix. As you can imagine, defects have higher priority then issues marked as feature requests (especially after the feature freeze). I am currently in process of going through all the enhancement and feature requests and choosing the ones we are going to address for 4.1. That's how I bounced to this one. You are right that it should be quite easy to fix this. It is a pity this was not escalated sooner. But currently the process is that we can only fix P2 and P1 defects. In addition, only defects escalated before Nov. 10 are considered. Issues escallated after yesterday will be addressed only if they are real showstoppers, since the code freeze starts basically tomorrow evening. Anyway, I will check whether there is any chance we will be able to put this into 4.0 despite the above.
It's a pity, but it's really too late. :-(
I am going to add the templates for enum and annotation type to the main trunk. Jano could you update J2SE Project Type UI Spec with order of templates and with description how to notify user that current JDK platform is not jdk 1.5?
I added templates + logic that notifies a user about wrong source level (possibly platform) of the target project. Hopefully Jano will update the spec soon. /cvs/java/project/src/org/netbeans/modules/java/project/Bundle.properties new revision: 1.26; previous revision: 1.25 /cvs/java/project/src/org/netbeans/modules/java/project/JavaTargetChooserPanel.java new revision: 1.22; previous revision: 1.21 /cvs/java/project/src/org/netbeans/modules/java/project/layer.xml new revision: 1.18; previous revision: 1.17 /cvs/java/project/src/org/netbeans/modules/java/project/resources/AnnotationType.html initial revision: 1.1 /cvs/java/project/src/org/netbeans/modules/java/project/resources/AnnotationType.template initial revision: 1.1 /cvs/java/project/src/org/netbeans/modules/java/project/resources/Enum.html initial revision: 1.1 /cvs/java/project/src/org/netbeans/modules/java/project/resources/Enum.template initial revision: 1.1
Reorganization of java component