I'll also add that foreach takes a list of things seperated by commas
( or any delimmiter)
Sent from my iPhone
On Jul 21, 2008, at 6:45 AM, André Pilz <[EMAIL PROTECTED]> wrote:
Hello,
in old days I wrote a target which checks for the file, and then
call this target with antcall for singl
On Mon, Jul 21, 2008 at 10:14 AM, Lars Ræder Clausen <[EMAIL PROTECTED]> wrote:
> Problem is, the required files come from
> several different directories, some from within the build space, some
> from without. It was easy to make a ClassPath with them, but that's
> not a usable argument for in
On Mon, Jul 21, 2008 at 4:01 PM, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 21, 2008 at 6:23 AM, Lars Ræder Clausen <[EMAIL PROTECTED]> wrote:
>> What obvious task/combination of conditions am I missing?
>
> I'd use Ant-Contrib's with a nested , but in your
> case Ant's own and t
On Mon, Jul 21, 2008 at 6:23 AM, Lars Ræder Clausen <[EMAIL PROTECTED]> wrote:
> What obvious task/combination of conditions am I missing?
I'd use Ant-Contrib's with a nested , but in your
case Ant's own and the usual target gymnastic (see other
poster's code) would do too. --DD
---
Hello,
in old days I wrote a target which checks for the file, and then call
this target with antcall for single or ant-contrib:foreach for lists of
files. Example with the normal path (customize to your needs):
filepath="${path}"/>
I use Ant to compile a Java module that depends on a number of jar
files that cannot be built from within the same build file. I have
them all listed in a class path, but I'd like to have a precondition
that fails if any of the jars listed do not exists -- makes the error
much easier to understand