run Jetty from outside the target so that you have to use -PcleanJetty to clean up, generally persisting the server and configuration that you used across clean builds

git-svn-id: https://svn.apache.org/repos/asf/archiva/branches/MRM-1025@721951 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Porter 2008-12-01 02:52:56 +00:00
parent 6a109eb2e9
commit 1e4179f5f2
1 changed files with 34 additions and 4 deletions

View File

@ -353,11 +353,11 @@
<systemProperties>
<systemProperty>
<name>plexus.home</name>
<value>${project.build.directory}/appserver-base</value>
<value>${basedir}/appserver-base</value>
</systemProperty>
<systemProperty>
<name>appserver.base</name>
<value>${project.build.directory}/appserver-base</value>
<value>${basedir}/appserver-base</value>
</systemProperty>
<systemProperty>
<name>appserver.home</name>
@ -365,7 +365,7 @@
</systemProperty>
<systemProperty>
<name>derby.system.home</name>
<value>${project.build.directory}/appserver-base/logs</value>
<value>${basedir}/appserver-base/logs</value>
</systemProperty>
</systemProperties>
</configuration>
@ -444,7 +444,7 @@
</goals>
<configuration>
<tasks>
<copy todir="${project.build.directory}/appserver-base">
<copy todir="${basedir}/appserver-base">
<fileset dir="src/appserver-base" />
</copy>
</tasks>
@ -497,5 +497,35 @@
</plugins>
</build>
</profile>
<profile>
<id>cleanJetty</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<executions>
<execution>
<id>cleanJetty</id>
<phase>clean</phase>
<configuration>
<filesets>
<fileset>
<directory>${basedir}/appserver-base</directory>
<includes>
<include>**/**</include>
</includes>
</fileset>
</filesets>
</configuration>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>