Because deployment happens to a staging or production server, I simply set the jvm startup params with -Dwicket.configuration=deployment.
I also have a small block in my Application instance that turns params on and off depending on the mode as well, so for instance I can have tags stripped etc. in production. So, I simply deploy the war as needed and the correct env is set up. I like this way of doing it because I hate having a *different* deployable depending on how some filter modified my metadata. - Brill -----Original Message----- From: Nino Saturnino Martinez Vazquez Wael [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2008 10:43 AM To: users@wicket.apache.org Subject: maven deployment..? Hi I use cargo, to deploy to tomcat and I would really like to automatically deploy wicket in deploy and not development. So what do you guys do..? Have different profiles that include different web.xml or? -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 --------------------------------------------------------------------- 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]