Thank Wim. It's currently done both ways, so hopefully we can hash this out and reach a decision to be consistent.
I personally feel that the maintenance nightmare can be solved by tooling/utilities, but the dependency issue by having a single file that every other file is dependent on goes against a couple of fundamental design principles. With that said, there does not seem to be too much concurrent development in the project; I am willing to go either way. I will wait for some more responses before proceeding. Steven Spungin ----- Original Message ----- From: "Wim Jongman" <[email protected]> To: "E4 Project developer mailing list" <[email protected]> Sent: Thursday, August 7, 2014 6:32:55 PM Subject: Re: [e4-dev] e4 tools cleanup I'm not fond of having translation files in each package.The advantage does not outweigh the maintenance nightmare it causes. Cheers, Wim On Thu, Aug 7, 2014 at 10:48 PM, Steven Spungin < [email protected] > wrote: I am planning doing a sweep through e4 tools and adding all nls strings to property files this weekend, unless anybody has objections to many files being changed at this time. I was going to do this several months ago, but the tooling(externalize string wizard) was giving me issues when trying to put the strings into a different package using the new eclipse approach. So instead, I wrote a patch that would allow us to do so. https://git.eclipse.org/r/#/c/26196/ . Bug 434261 - [nls tooling] Allow selection of property file not in source folder. Without this patch, either each string needs to be entered into the java and properties file manually, or the translation files need to be in the same package as the source. This would result in many pairs of translation files. Does anybody object to a pair of translation files in each package? Having multiple files does have the advantage of minimizing merge conflicts. Steven Spungin _______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev _______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
