Rapthor wrote: > > > Donald McLean wrote: >> >> Really? That sounds like a case of "The cure is worse than the disease." >> >> I can't imagine a single case where something like that would be a >> better solution than the three or four techniques for providing static >> attributes that I'm already familiar with. >> >> However, of course, YMMV. >> > > Hmm you mean I should leave the properties file out and create a static > class instead? That sounds useful ... On the first attempt I wanted to use > JAVAs Properties-class and so I used properties-files as base. > > Did I get you right? > >
Now I remember: I wanted to be able to change configuration values at runtime. I would just have to provide a mechanism to reload the Properties instance with the file. But the mechanism to create a static class does not confirm with that idea. -- View this message in context: http://www.nabble.com/ANT-task-to-process-properties-files-into-static-class-tf2909466.html#a8131373 Sent from the Ant - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
