Adding that clean configuration works perfectly for what I want to
do. The mvn compile war:inplace is a nice hint as well, though I did
notice that it doesn't run my filters on resources going into the
classes dir, as it does when you just do a mvn clean package. But
that's not too big a deal - the clean config is what I was looking for.
Thanks!
J
On 2-Mar-07, at 2:10 PM, [EMAIL PROTECTED] wrote:
I'm wondering if a whole 'nother approach would work for you. It
really
depends on your workflow, but I submit it for your consideration.
Doing 'mvn compile war:inplace' will cause maven to copy the .class
files
to web-inf/classes and the pom dependencies to web-inf/lib so that
you can
do your gui testing in place. I'd also suggest setting up your source
control to ignore these folders. I've done it with subversion, but
don't
recall the syntax.
To go a step further, add those directories to the 'clean' plugin
in your
pom like this:
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<configuration>
<filesets>
<fileset>
<directory>${basedir}/src/main/webapp/WEB-INF/lib</directory>
</fileset>
<fileset>
<directory>${basedir}/src/main/webapp/WEB-INF/classes</directory>
</fileset>
</filesets>
</configuration>
</plugin>
Now you can do 'mvn clean package' to get a pristine war.
Does that meet your overall goal?
-Greg Vaughn
"Julian
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
