Re: [Clirr-devel] Message framework

[<lak...@t-...>]

Simon Kitching wrote:

>[...]
>  
>
>>    * Using english language properties files without language extension
>>      (i.e. x.properties instead of x_en.properties) does bring some
>>      nasty surprises, see
>>      https://sourceforge.net/tracker/index.php?func=detail&aid=594469&group_id=29721&atid=397078
>>      <>I have a solution that will work without copying the properties
>>      file during the build (like we do in checkstyle). You just need to
>>      use a valid class name as the ressource name, e.g.
>>      EventMessages_en.properties, I can do the rest.
>>      <><> 
>>    
>>
> <>
> I understand the problem described by your email (and yes that is
> nasty!). I don't understand your comment above, though.
>
> Isn't the correct solution just to copy event_messages.properties to
> event_messages_en.properties as part of the build?


> <>With that:
> * if the user asks for "en" then "en" is found.
> * if the user asks for an unsupported locale then they get the
> properties for the machine's default locale (if it exists)
> * if there are no properties for the machine's default locale,
> then they get the base version (which is also english).
>


Basically yes, that's what we do in checkstyle, and it works. My point 
probably is that Maven is great for doing standard things, but it's a 
bit tricky to convince it to do additional things (at least for me), and 
I have a better solution that doesn't require build time tricks or 
duplicate data in the jar file.

>So what do you mean by "You just need to use a valid class name as the
>resource name"? Maybe it is just easier if you commit the fix then I can
>see what you meant :-)
>
>  
>
:-)

OK, I'll fix it, but probably not tonight. European Football 
Championship Semifials on TV - sorry, I just have to set priorities ;-).

Cheers,
Lars