Since I proposed the idea, I'd figured I better figure out how to do
it. Here is some sample code I threw together. It turns our that you can't
use the <exec> task, instead we have to use the <java> task.
thanks, aaron
<project name="hackyBuild" default="hackyInstaller" basedir=".">
<target name="hackyInstaller" description="HackyInstaller">
<java jar="hackyInstaller.jar" fork="true">
<arg line="-SetHostAndKey http://hackystat.ics.hawaii.edu foo"/>
</java>
</target>
</project>
C:\java\temp>ant
Buildfile: build.xml
hackyInstaller:
[java] Rhino classes (js.jar) not found - Javascript disabled
[java] Hackystat key is invalid.
BUILD SUCCESSFUL
Total time: 2 seconds
C:\java\temp>
At 07:38 AM 8/4/2005, you wrote:
--On Wednesday, August 3, 2005 8:01 PM -1000 Aaron Kagawa
<[EMAIL PROTECTED]> wrote:
Of course, there probably is an Ant task that can run command line
executions from a jar file. If so, then we wouldn't need to implement an
entirely new view component.
A couple of things:
* Cedric is right; we can't get rid of 'ant updateAntLib' entirely, since
we need things like jblanket for our build process which are unrelated to
Hackystat. But we can get rid of the sensor jar files from hackyBuild.
* Ant has an <exec> task which would allow us to invoke hackyInstaller.jar
via its command line interface. In some ways, I actually prefer this to
building an Ant task, because if we build an Ant task, then we have to get
the jar file into ant/lib, which means 'ant updateAntLib', and we're back
where we started!
Let's start by hacking up an exec task and see what happens. If it seems
that a custom Ant task will buy us something significant, I'm open.
Cheers,
Philip
