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]
