[forge-dev] I18N Plugin
jperkins at redhat.com
Tue Apr 17 15:23:46 EDT 2012
Just as a side observation, if Forge doesn't have to support Java 5,
then using the Properties.load(Reader) is a better option. With an
InputStreamReader you can instantiate it with a character set encoding,
e.g. UTF-8. This allows property files that don't use unicode to be
On 04/17/2012 11:34 AM, George Gastaldi wrote:
> Ok, in order to allow better flexibility, I created a
> PropertiesFileResource (http://pastebin.com/cumGm9Bp) and an
> EntryResource (http://pastebin.com/PDARhPEJ).
> Now I need to change
> to return this object when a .properties file is called.
> Question is: What´s the better way of doing this ? I don´t think
> changing directly in this method will suffice.
> When inside a properties file, running "ls" should display the
> properties in a key = value format
> George Gastaldi
> 2012/4/17 Lincoln Baxter, III<lincolnbaxter at gmail.com>:
>> This sounds like something that would go well in the "dev-plugins" module.
>> Good idea! I've also been wanting a plugin to create a new ServiceLoader
>> service registration in META-INF/services, based on an interface and class
>> On Mon, Apr 16, 2012 at 11:55 PM, George Gastaldi<gegastaldi at gmail.com>
>>> Hey all,
>>> Just created a new issue (https://issues.jboss.org/browse/FORGE-541)
>>> regarding i18n support on Forge enabled projects.
>>> I was thinking if it should it be part of Forge core. WDYT ?
>>> Feel free to add any new comment on this issue. I plan to start
>>> working on it still this week.
>>> George Gastaldi
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>> Lincoln Baxter, III
>> "Simpler is better."
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
> forge-dev mailing list
> forge-dev at lists.jboss.org
James R. Perkins
JBoss by Red Hat
More information about the forge-dev