Re: maven deployment..?
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 the same way:) So you just need to add this to your profile?: properties wicket.configurationdeployment/wicket.configuration /properties James Carman wrote: 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: http://svn.carmanconsulting.com/public/wicket-advanced/trunk On Fri, May 30, 2008 at 10:43 AM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: 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] -- -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] -- -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]
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 certainly ease of maven config a bit. 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. I've done this too once, however I like to test it with same properties as 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] -- -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]
Re: maven deployment..?
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 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 to add this to your profile?: properties wicket.configurationdeployment/wicket.configuration /properties James Carman wrote: 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: http://svn.carmanconsulting.com/public/wicket-advanced/trunk On Fri, May 30, 2008 at 10:43 AM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: 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] -- -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] -- -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]
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 the properties/profiles won't quite get it done. You need to turn on resource filtering in maven: resources resource directorysrc/main/resources/directory includes include**/*.xml/include include**/*.properties/include /includes filteringtrue/filtering /resource /resources - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven deployment..?
Not a problem, you can turn that switch on at any time on the maven command line, or in a profile (which also would likely require a command line switch). If you're a true test user, you can likely turn that on for only your unit tests and/or set up an execution for surefire so the test are run in another phase (disclaimer: I've never tried to set up executions for surefire, I assume it can be done). Example: # mvn -P WICKETTEST test # mvn -Dwicket.configuration=deployment test - Brill -Original Message- From: Nino Saturnino Martinez Vazquez Wael [mailto:[EMAIL PROTECTED] Sent: 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 certainly ease of maven config a bit. 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. I've done this too once, however I like to test it with same properties as 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] -- -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]
RE: maven deployment..?
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 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 resource filtering in maven: resources resource directorysrc/main/resources/directory includes include**/*.xml/include include**/*.properties/include /includes filteringtrue/filtering /resource /resources - 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]
Re: maven deployment..?
The filtering replaces the maven properties in your templates. Take a look at: http://svn.carmanconsulting.com/public/wicket-advanced/trunk/src/main/resources/META-INF/beans.xml That's my spring configuration file. All of the database settings, the Wicket configurationType, etc. are all replaced by maven properties when they are copied. On Mon, Jun 2, 2008 at 8:56 AM, Brill Pappin [EMAIL PROTECTED] wrote: 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 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 resource filtering in maven: resources resource directorysrc/main/resources/directory includes include**/*.xml/include include**/*.properties/include /includes filteringtrue/filtering /resource /resources - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven deployment..?
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 replaces the maven properties in your templates. Take a look at: http://svn.carmanconsulting.com/public/wicket-advanced/trunk/src/main/resour ces/META-INF/beans.xml That's my spring configuration file. All of the database settings, the Wicket configurationType, etc. are all replaced by maven properties when they are copied. On Mon, Jun 2, 2008 at 8:56 AM, Brill Pappin [EMAIL PROTECTED] wrote: 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 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 resource filtering in maven: resources resource directorysrc/main/resources/directory includes include**/*.xml/include include**/*.properties/include /includes filteringtrue/filtering /resource /resources - 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] - 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]
RE: maven deployment..?
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]
Re: maven deployment..?
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 to add this to your profile?: properties wicket.configurationdeployment/wicket.configuration /properties James Carman wrote: 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: http://svn.carmanconsulting.com/public/wicket-advanced/trunk On Fri, May 30, 2008 at 10:43 AM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: 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] -- -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]
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]
Re: maven deployment..?
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: http://svn.carmanconsulting.com/public/wicket-advanced/trunk On Fri, May 30, 2008 at 10:43 AM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: 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]
