Clint - I've run into one (hopefully minor) hitch with the process. The
filtering works, but only after I've used Maven to deploy the project. When
I'm developing, however, I just run the project on the Jetty server that
comes with the Quickstart. Of course, that means that the ${} variables are
treated as literal values. Is there a way to filter the project locally
without having to run a Maven build every time I make a change?James - Spring and Hibernate are next on my things-to-learn list, after I get Maven (and perhaps Continuum) figured out. Thanks to both of you for the input! On Wed, May 20, 2009 at 10:48 AM, James Carman <jcar...@carmanconsulting.com > wrote: > Check out the way I did it in my wicket-advanced example application: > > http://svn.carmanconsulting.com/public/wicket-advanced/trunk > > I did a combination of maven profiles and Spring's > PropertyPlaceholderConfigurer. If you're not using Spring, it won't > help, but if you are, it might be interesting to you. > > On Wed, May 20, 2009 at 12:59 PM, Clint Popetz <cl...@42lines.net> wrote: > > I recommend using ${} variables in web.xml and resource filtering, as > > you mentioned, but the way to avoid changing them all the time in > > pom.xml is to have different maven profiles that set them differently > > in your pom. It is true that you'll have to do things like > > -PtomcatDeployment when running maven to activate them, but then all > > your random variables are controlled by a uniform set of profiles, and > > you aren't trying to remember which options to set for which target > > deployment. You can also set up the profiles to be active based on > > certain environments, or automate setting them in build scripts or in > > settings.xml. > > > > Maven profiles are da bomb, IMHO. Especially when building for lots > > of target environments > > (qa/mirroring/local-dev/load-testing/continuous-integration) and on > > different platforms. > > > > -Clint > > > > On Wed, May 20, 2009 at 11:40 AM, Dane Laverty <danelave...@gmail.com> > wrote: > >> I've got my project set up to deploy with Maven's Tomcat plugin now. My > next > >> step is getting the web.xml to use the correct Wicket configuration > >> (development/deployment) value. Is there a way to run two separate > web.xml > >> files for the application, and then somehow have Maven pick up the > correct > >> one when I run "mvn tomcat:deploy"? Or am I going about this the wrong > way > >> entirely? I've done some reading and it sounds like people are using > "web > >> resource filtering" to address the issue, however to me it seems that it > >> just moves the parameters from the web.xml to the pom.xml, and that I > would > >> have to manually change them in the pom.xml when I want to change from > >> deployment to development. > >> > > > > > > > > -- > > Clint Popetz > > http://42lines.net > > Scalable Web Application Development > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
