> The ${label} parameter becomes set to "Release_2007_12_01_001" when
> the build script is executed. Even better, it cannot be reset via a
> task. That means you could have a default value defined in
> your build file, and then have the command line value over ride it.
He meant task instead of
Not sure if this is what you're looking for, but you can pass in
properties by using the -D flag:
ant -Dlabel=Release_2007_12_01_001 -f mybuild target
The ${label} parameter becomes set to "Release_2007_12_01_001" when
the build script is executed. Even better, it cannot be reset via a
task. Tha
Need to call an ANT target from a UNIX shell script and pass the parameter to
it - like a Build TAG name: so from within the shell script, I'd like to
issue something like this: ant -f mybuild.xml Release_2007_12_01_001 - how
could I pass a parm as input parm to a script so ANT could do some va
> 1). Use a task to set a property depending upon the value
> of ${java.version}. I don't think there's an 'atleast' condition, so
> you'll have to make do with "contains". Once you manage to set this
> condition, use a task if this condition isn't set.
Jan
-
This is a Windows issue since Windows cannot reference file paths
longer than 260 characters. If this works under JDK 1.5, it is because
JDK 1.5 is using a somewhat different way to handle file names (using
the NTFS library calls instead of the Windows library calls). I can
see a few ways of handli
Hi Chuck,
Use an "apply" task with "parallel" and "relative" set to "true" and set
a value for "dir". Like this:
relative="true">
Daniel
Chuck Holzwarth wrote:
If you have checked the destination directory out from subversion, you should
be able to create a target where you use t
I have resolved this. Please check the enviroment settings of your machine
nad make sure if the JDK version matchs tools.jar.
To a norther word, sometimes you can leave %CLASSPATH% empty and point it in
a bat file.
Jacky-9 wrote:
>
> Hi guys,
>
> I encounter this error when trying to build my
