Low priority, but would be cool IMHO:

If a .properties file is a template, during create-from-template if there is already a file of the same name in the target folder, instead of failing or replacing the old file, just add all keys from
this template to the existing one (probably the old keys should take priority in case of conflict, i.e. only add new keys). Maybe this behavior could be an option for the file if it was a template, ra
ther than the default behavior.

Justification: for API Support at least, we encourage use of Bundle.properties files. So sample code makes references to NbBundle, which looks for this by default. But, it is not possible to include B
undle.properties templates along with each specific template, because then people could not create from template twice in the same package--their old Bundle.properties would be overridden. There is th
e workaround of including only .properties files named according to the template, but then NbBundle.getBundle (Class) will not work, and there will be too many bundle files (one per package is more re

asonable).