[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-2972:
--------------------------------------
It's still relevant, but I have a workaround. This file contains the wildcards I have
defined to pick up .properties files:
http://anonsvn.jboss.org/repos/jbosstools/trunk/i18n/prop2potincludes.txt (reproduced
here):
*/plugins/*/plugin.properties
*/plugins/*/src/**/*.properties
*/plugins/*/jbosscore/**/*.properties
*/plugins/*/jbossui/**/*.properties
*/plugins/*/resources/**/*.properties
*/plugins/*/template-src/**/*.properties
Naturally, I would prefer the list was shorter, and not so ad hoc. (But plugin.properties
is fine, by the way.) I'm just concerned about the hodge-podge of
*Messages.properties files, under src/, jbosscore/, resources/, etc.
Also, I haven't got any feedback from the translators yet, but I suspect some of the
included properties files may contain not translatable text but configuration values. So
it would still be better if we could keep them in separate directories so that I can
easily exclude config files.
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL:
https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.CR2
See
http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira