I had that originally. But from a support standpoint I moved that info
to a Java class. I prefer to have that info built into the application
and not dangling around in some properties file.
I've taken more or less the opposite approach. Initially I had
configuration data in a traditional UNIX configuration file that tha
application could find by searching the local directory, /usr/local/etc
and /etc in that order. Then I realised that, although this was convenient
to manage during development, it had installation drawbacks, particularly
for client programs which are run on many PCs across a network. I also
twigged that my file format was also readable as a properties file because
it only contained comments and keyword=value lines.
Rather than building configuration data content into a class, I just
included the configuration file in the application's JAR file, which
effectively builds it into the application. For added convenience I wrote
a simple script that can extract the config file, change it and replace it
in the jar. Doing that is much more convenient for site specific
configuration than using a compiler.