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 working on a CVS controlled project. Using NetBeans I copied the ApplicationResources.properties file which is under CVS control. Then I pasted it as a copy and renamed it to ApplicationResources_de.properties to add a new language to the webapp. At this point the new file vanishes, because NetBeans handles the properties files as one file for easier editing. This is generally very nice, but even in the filesystem tab ApplicationResources_de.properties can not be found, so it can not be added to the CVS project!
And have you tryied using Versiong Explorer ? This is kinda view of individual File(Object)s and in simple Explorer (doesn't matter if it is in Project's TAB or not) there are displayed whole DataObjects which is handled by IDE's internal logic and thus Properties files are treated as one DO... I suggest cloese this bug as IVALID or WONTFIX.... Any objections?
Exactly Daniel. Recommended workflow is to use "Versioning Explorer" for this purpose, Boris. I also propose to resolve this as won't fix. Martin ?
Well, we need to check the behavior when you run Add on the whole DataObject. The behavior of the command-line integration is that only the local files are added and other files in the DataObject are ignored. This behavior is important for J2EE modules in S1S. So javacvs should behave the same way I think. It should not be that hard to implement.
I think I simply overlooked, that the Properties file can be expanded! Then I get two new nodes: one for the default language and one for de (german). These nodes have both a CVS context menu, so I assume that it's possible to add the new file by using NetBeans. I did it already using cvs add in the shell.
Wow, I don't believe my eyes! I'm not sure this is supposed to work, it was not there before. Some actions (e.g. rename) do not work on the locales nodes. I'm going to fill an issue and ask for explanation of what is this supposed to do.
Issue #31061 submitted to properties module.
The secondary locales can be added through the Versioning Explorer as Dan pointed out. Also there was implemented feature #31056, that makes the addition of secondary files very easy (for the command-line CVS integration currently, it will be extended for JavaCVS in 4.0). Also you can take the advantage of special behavior of Properties nodes, that allow you to add individual locales from the sub-nodes. This resolving as a duplicate of issue #31061, since after issue #31061 is fixed this should work. *** This issue has been marked as a duplicate of 31061 ***
Okay, verifying as duplicate issue and hoping that properties guys will resolve it soon.