[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Thu Feb 26 07:54:44 EST 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen resolved JBIDE-2972.
----------------------------------------

    Resolution: Rejected


as far as I understood the last mail about i18n we won't need nor want to do this.

reopen if i misunderstood.

> 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.GA
>
>
> 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

        



More information about the jbosstools-issues mailing list