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.
Existing problems: - no standard way of including a replaceable token inside a quoted string (it will be ignored by MapFormat)--this makes it impossible to provide things like icon resource paths based on package - DATE, TIME, etc. are included by Java loader and maybe other loader separately; there is no master list of these - user-specified strings like USER are set separately in every loader, so this info must be retyped in every Settings for different modules - missing conventions for common user-specifiable things like copyright, version, etc. - not documented how to add multi-line strings (loaded via java.util.Properties) See Solution tab for suggested fixes. [phamernik] deferred for f4j 1.0 CE final.
Priority is changed to P4 (normal).
I think this is dupe of something newer, pls. check.
Component: core->java.
Passing to Svata...
Actually I think this is an openide issue - there is no workable API for consolidating replacement tokens across modules.
Jesse's right, the basic support for fixed (or standard, like DATE) replacement strings should be done in OpenAPIs, or at least documented (if the macros are declarared in XML layer).
passing back to Petr, Petr please reassign it that's not right.
*** Issue 17075 has been marked as a duplicate of this issue. ***
Changed owner David S. -> David K.
It would be nice to add some scripting support at the same time. That way the template could be a bit like a JSP. could go the whole hog and let the template be a JSP and then you have the JSP2.0 and JSTL + custom tags etc for free, but I gusee that some people will not like that! I am sure thatthere is some compromise, but having the templates scriptable would tend to ensure thatthe content is in the template, and much of the behavior, so the majority of the programming could be UI only, and the behavior would be more declarative. perhaps this could also control the conditional creation of files, within a group
We do not need old open issues nobody is going to fix.
Is nobody going to fix this? IMHO this is still as relevant as it was when opened.
If you know about someone, please reassign the issue to him.
It's still a valid requirement even if we don't have anyone to work on it right now. We still need to work on it someday.