Thanks Simon! I can work with that...
On May 7, 2012, at 5:41 PM, Simon Murcott wrote:
> I ended up writing a custom ant task to do this. Unfortunately in both *nix
> and windows you can't always rely on environment variables. On *nix you need
> to read the output of /bin/hostname or on win
I ended up writing a custom ant task to do this. Unfortunately in both *nix and
windows you can't always rely on environment variables. On *nix you need to
read the output of /bin/hostname or on windows read the output of
WScript.Network.ComputerName
Regards, Simon
On 8/05/2012, at 8:28 AM, E
Thanks Nathan, very helpful. This is at the top of my build file:
When running with -v, I get this:
[property] Loading Environment env.
Property "env.COMPUTERNAME" has not been set
And then the code below tries to import a property file that doesn't exist:
Add -v in your call (or -debug):
ant [-v|-d] -f build.xml
-Original Message-
From: Eric Fetzer [mailto:elstonk...@yahoo.com]
Sent: Monday, May 07, 2012 2:12 PM
To: Ant Users
Subject: Build directly on machine vs. SSH to machine and start build
This is very strange to me. Here a
This is very strange to me. Here are the 2 scenarios.
Scenario 1:
1) Log on to buildMachine as user builduser
2) >bash
3) >cd /my/builddir
3) >/opt/apache-ant-1.7.1/bin/ant -f build.xml -Dfull.buildnumber=3.0.2.8
4) Build succeeds without issue
Scenario 2:
1) From a different machine:
Indeed; all produced jars for the last few Ant releases are available
in Maven Central. You'll certainly need ant.jar, possible
ant-launcher.jar, and depending on which optional tasks you might want
to use, any number of additional jars and their dependencies.
HTH,
Matt
On Fri, May 4, 2012 at 4:
