Yup..
James Carman wrote:
Well, the test and prod profiles do have that property set to
deployment. The default properties just sets it to development.
On Fri, May 30, 2008 at 2:38 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Great:) Looks like we do a lot of stuff
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
it seems it's just not enough adding the stuff to the profiles, do you
use the maven properties plugin aswell? or?
James Carman wrote:
Well, the test and prod profiles do have that property set to
deployment. The default properties just sets it to development.
On Fri, May 30, 2008 at 2:38
On Mon, Jun 2, 2008 at 7:55 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
it seems it's just not enough adding the stuff to the profiles, do you use
the maven properties plugin aswell? or?
Just adding the properties/profiles won't quite get it done. You need
to turn on
: Monday, June 02, 2008 4:36 AM
To: users@wicket.apache.org
Subject: Re: maven deployment..?
Brill Pappin wrote:
Because deployment happens to a staging or production server, I simply
set the jvm startup params with -Dwicket.configuration=deployment.
It's also a possibility, i'll
Why do you need the filtering?
- Brill
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of James Carman
Sent: Monday, June 02, 2008 8:14 AM
To: users@wicket.apache.org
Subject: Re: maven deployment..?
On Mon, Jun 2, 2008 at 7:55 AM, Nino Saturnino
AM
To: users@wicket.apache.org
Subject: Re: maven deployment..?
On Mon, Jun 2, 2008 at 7:55 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
it seems it's just not enough adding the stuff to the profiles, do you
use the maven properties plugin aswell? or?
Just adding
Ahh, I see... I don't use spring so I don't have to replace anything :)
-Brill
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of James Carman
Sent: Monday, June 02, 2008 9:01 AM
To: users@wicket.apache.org
Subject: Re: maven deployment..?
The filtering
[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
Well, the test and prod profiles do have that property set to
deployment. The default properties just sets it to development.
On Fri, May 30, 2008 at 2:38 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Great:) Looks like we do a lot of stuff the same way:)
So you just need
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
You don't need different web.xml files. You can use maven's filtering
capability to filter your web.xml file (actually I filter my spring
config files since I set up my application in a spring context). Take
a look at my wicket-advanced example code for inspiration:
12 matches
Mail list logo
