Igor, Thanks for the suggestion. Definitely looks like a good way to go.
Tauren On Sun, Aug 23, 2009 at 5:02 PM, Igor Vaynberg <[email protected]>wrote: > we used to do something like this before we switched to jndi > > <value>classpath*:/application.properties</value> <-- prod values > <value>conf/application.${user.name}.properties</value> > > that way each dev can create a conf/application.<their user > name>.properties and override production settings with their own. > > for different envs you simply override the value of user.name with by > defining it with -Duser.name > > -igor > > On Fri, Aug 21, 2009 at 4:27 PM, Tauren Mills<[email protected]> wrote: > > I just wanted to follow up on this. As an interim solution until I > > have time to really do this right (using Hudson, etc.), I've done what > > is suggested here: > > http://www.developer.com/java/ent/article.php/3811931 > > > > In my spring config PropertyPlaceholderConfigurer, I use this: > > <value>classpath*:/application.${env}.properties</value> > > > > This means that steps 1 and 2 have been resolved without the effort > > required to switch to using JNDI, maven profiles, or other build > > tools. All I do is specify -Denv=prod on my production server and > > -Denv=dev -Dwicket.configuration=development on my development system. > > I can add additional staging, QA, and other servers with this > > scenario, and it doesn't require a separate WAR for each one. > > > > Tauren > > > > > > On Mon, Aug 17, 2009 at 11:07 AM, Tauren Mills<[email protected]> > wrote: > >> Janos and Jeremy, > >> > >> Thank you both for your feedback! > >> > >> After considering your answers, I think that using Maven profiles is > >> most in line with my needs. And the suggestion to use the command > >> line -Dwicket.configuration=deployment parameter will certainly help. > >> I've never used Hudson before, but I'm looking into it now. It sounds > >> like it could help simplify things significantly. > >> > >> Thanks again, > >> Tauren > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
