This is all very well, but we have some developers who'd ideally like to not have to run maven at all whilst doing webapp development, but still leverage it for building all our reports and doing build checks before code checkin.
ie we don't want to be copying files about, is this possible, so far I've told them no. The information contained in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If You are not the intended recipient of this e-mail, the use of this information or any disclosure, copying or distribution is Prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. The views expressed in this e-mail may not necessarily be the views of The PCMS Group plc and should not be taken as authority to carry out any instruction contained. > -----Original Message----- > From: Siegfried G�schl [mailto:[EMAIL PROTECTED] > Sent: 01 August 2003 10:53 > To: Maven Users List > Subject: RE: "In-Place" Web Development > > > Hi Brett, > > I came along this issue two weeks ago using Eclipse, Tomcat, Struts > and the Tomcat Plugin for Eclipse. > > What I'm doing: > > +) I left MAVEN alone and tweaked the Eclipse confiugration to > generate the class file into src/webapp/WEB-INF/classes. > > +) added a postGoal to war:webapp calling a locally defined goal > local:webapp > > <goal name ="local:webapp"> > > <echo>Copy libs to ${maven.war.src}/WEB-INF/lib</echo> > <copy todir="${maven.war.src}/WEB-INF/lib" overwrite="true"> > <fileset dir="${maven.build.dir}/${pom.artifactId}/WEB-INF/lib"> > <include name="**/*.*"/> > </fileset> > </copy> > > <echo>Copy class files to ${maven.war.src}/WEB-INF/classes</echo> > <copy todir="${maven.war.src}/WEB-INF/classes" overwrite="true"> > <fileset dir="${maven.build.dir}/${pom.artifactId}/WEBINF/classes"> > <include name="**/*.*"/> > </fileset> > </copy> > > </goal> > > What it does is to copy the libs and generated classes from target > into src/webapp/WEB-INF. And this is the place where the "in-place" > development is done - the main inconvenience is changing the > referenced JARs. > > > Cheers, > > Siegfried Goeschl > > > > On 1 Aug 2003 at 15:59, Brett Porter wrote: > > > This isn't really in place though.. Although it is quick enough for > > me. > > > > If you want it in place, what I've done in the past is have > the target > > dir set to the current directory so that WEB-INF/lib and classes get > > populated by maven (everything else src=dest so its no > problem), then > > symlink or configure whatever tomcat instance you are > running to that > > directory, compile into WEB-INF/classes, tweak your JSPs, etc > > > > - Brett > > > > > -----Original Message----- > > > From: Ben Walding [mailto:[EMAIL PROTECTED] > > > Sent: Friday, 1 August 2003 3:45 PM > > > To: Maven Users List > > > Subject: Re: "In-Place" Web Development > > > > > > > > > Take a look at > > > http://wiki.codehaus.org/maven/CreatingWebApplications > > > > > > Dave Ford wrote: > > > > > > >How do people do "in-place" web development with Maven? > I have been > > > > developing web apps "in-place" now for quite some time > > > (pre-maven). By > > > >in-place, I mean the following: > > > > > > > > > --------------------------------------------------------------------- > 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]
