Davis Ford wrote:
Thanks Brian,
I will check into dependency-maven-plugin. In the meantime, I had
solved it. This seems to be anti-Maven, b/c it uses an environment
variable, but it seems to work. I added these two goals to maven.xml
<goal name="check-props">
<j:if test="${context.getVariable('geoserver.home') == null}">
<j:if test="${context.getVariable('env.GEOSERVER_HOME') ==
null}">
<fail>Please set either env-var GEOSERVER_HOME
or Maven var
geoserver.home</fail>
</j:if>
<echo>Setting geoserver.home to
${env.GEOSERVER_HOME}</echo>
<j:set var="geoserver.home"
value="${env.GEOSERVER_HOME}"/>
</j:if>
</goal>
<goal name="geoserver" prereqs="jar, check-props" description="Copy
the Diamond Jar to GeoServer">
<echo>GeoServer Home is = ${geoserver.home}</echo>
<ant:copy file="${maven.build.dir}/${maven.final.name}.jar"
todir="${geoserver.home}\server\geoserver\WEB-INF\lib"/>
</goal>
You could also place the GEOSERVER_HOME variable in the
project.properties file so you don't have to use context.getVariable().
This way, you just have to tell your developers to change the setting in
their copy of the project.properties file.
- Henry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
