Setting the JVM property is great because you can do it on your deployment
server, so the same WAR runs in debug mode on all but the deployment machines.
If you want Maven to fix the setting on a build, you can create a properties
file:
> wicket.configuration = ${deploy.type}
Then create one or more profiles in your pom, one of them set as a default
profile. In them, have Maven do a substitution on deploy.type for either
'development' or 'deployment'.
Profiles are great for automated builds since the profile can be specified on
the command line in the CI system.
Brian
On Jul 19, 2010, at 1:14 PM, Major Péter wrote:
> Hi,
>
> you could configure the wicket.configuration with JVM properties too, so
> you can have always enabled the production mode in web.xml, and override
> it with your dev server JVM property. See the JavaDoc for
> Application#getConfigurationType.
>
> Regards,
> Peter
>
> 2010-07-19 19:10 keltezéssel, Gustavo Henrique írta:
>> Hi!
>> I'm using wicket in development mode but I need to change to deployment mode
>> when maven is called. How I configure maven to change that mode when it is
>> to generate war file?
>>
>> thanks!
>
> ---------------------------------------------------------------------
> 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
