Sorry KC, I missed that. You are definintely going to need to continue copying to a staging location.
Personally, I never filter things inside the web application, keeping configuration outside of the webapp (eg, in a tomcat context file). - Brett On 1/23/06, KC Baltz <[EMAIL PROTECTED]> wrote: > Vincent, Brett, > > Your responses don't seem to address the issue of the filtered web.xml file. > The solutions you linked to look good, but I don't see how they address that > specific problem. > > Stephen's suggestions seem workable, but they also appear to depend on > plugins or IDE features that don't currently exist. > > Let me know if I'm going against the grain trying to have a file filtered > inplace. I think I have things working using some Ant tasks within M2 to do > the copy/filter/rename, so I'm going to go with that until I hear something > better. > > K.C. > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, January 23, 2006 11:12 AM > To: 'Maven Users List' > Subject: RE: [m2] Best practice for in-place webapp development? > > > ... and > http://blogs.codehaus.org/people/vmassol/archives/001307_cargo_v07_and_maven > 2_plugin_v01.html. > > -Vincent > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: lundi 23 janvier 2006 19:27 > > To: Maven Users List > > Subject: Re: [m2] Best practice for in-place webapp development? > > > > http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html > > http://blogs.codehaus.org/people/brett/archives/001306_developing_with_jet > > ty_where_have_you_been_all_my_life.html > > > > > > On 1/23/06, KC Baltz <[EMAIL PROTECTED]> wrote: > > > I'd like to convert our project to use M2 for web app development and > > I've run into a bit of a snag. Right now, we use Eclipse with the Sysdeo > > plugin so we can run our webapp in Tomcat, directly from Eclipse without > > any sort of deployment/copying steps. The files we edit are the ones > > Tomcat is using. This is great because we can edit JSPs and see the > > changes take place immediately. I don't want to give up this behavior. > > > > > > Here's the problem: We have some values in web.xml that we want to be > > configured at build time via filtering. We're currently using an Ant > > task to copy, filter, and rename web.xml.template to web.xml. In Maven, > > the best practice seems to be to not have a rename step, but I can't see > > how to make this work with an in-place deployment. I need to have an > > unfiltered version of web.xml for CVS, and a filtered version for running > > in Tomcat. > > > > > > Obviously, I could point Tomcat at the /target/MyProject directory and > > run it from there, but then any changes I made to JSPs would need to be > > copied back to the /src tree to commit them to CVS. > > > > > > Is anyone doing something like this? Can you suggest a fix? > > > > > > K.C. > > > > > > > > > > --------------------------------------------------------------------- > > 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]
