This is particularly handy for taking the nightly builds (as well as reporting output from Together and Maven) and deploying them to our development web server via a cron job, or as the result of a CVS or Cruise Control action.
You can find out more about how to configure it (for *nix, anyway) at http://www.asitis.org/archives/000063.html (turned up from a quick Google search, and appears to be "all there")
We've even got our Maven repository (http) being kept in CVS, so that whenever a change is made to that repository, a new rsynch is done to the web server (they can only write files or create directories that aren't already there). This means that our (distributed) development team has control over the remote repository using their CVS access, without having to worry about any kind of special or additional access to our web server boxes. It also stops them from bugging me in order to put up new jars all the time. ;)
$0.02
...jeff
At 05:54 -0700 9/15/03, Hagelski wrote:
I was having similar problems with that, so I resorted to some interaction with the system:
<goal name="web1-deploy"> <j:set var="project.contextroot" value="/"/> <attainGoal name="web1-init"/> <attainGoal name="war"/>
<exec dir="${maven.build.dir}" executable="scp"> <arg line="${maven.war.final.name}"/> <arg line=" [EMAIL PROTECTED]:/usr/java/jboss/server/default/deploy/${maven.war.fi nal.name}"/> </exec> </goal>
when the exec occurs, I get prompted for my password.
the ssh-agent idea looks good too, think I'll check that out myself.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
