[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to handle properties file

From: Michael Koch
Subject: Re: How to handle properties file
Date: Fri, 20 May 2005 06:40:31 +0200
User-agent: mutt-ng 1.5.9-r292i (Debian)

On Thu, May 19, 2005 at 11:24:16PM +0200, Nicolas Geoffray wrote:
> On Thu, 2005-05-19 at 21:54 +0200, Sascha Brawer wrote:
> > Hi Nicolas,
> > 
> >
> > 
> > I think the default config file should not be shipped as part of 
> >, but instead installed as a separate file. Sorry, I don't have 
> > the time right now to fix it myself...
> > 
> OK. Thank you Sascha for the answer.
> So, properties files inside a jar (or zip) archive are always handled by
> the application (or the gnu classpath files)? Nothing should be done at
> the opening of the jar file? If I'm asking, it's because i'm afraid as a
> vm implementor to make some code that will read a jar file (like
> and do things like looking for *.properties files from it.

Now I understand your original request. Sorry for my stupidity.
No, not all *.properties files have to be outside of
E.g. we use property files to define locale data. These need to be still
inside Others should be outside to be editable by the
administrator of the GNU classpath installation. Can you please file a
bug report for this?

Escape the Java Trap with GNU Classpath!

Join the community at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]