Again, I appreciate the creative solutions, David. But I'm afraid the
redundancy is impractical. Having to specify every set of filepaths
twice in separate areas is far too brittle to be acceptable to our team.
I count 36 explicitly named single files in our current build.xml
script, not includin
> Again, we need to detect any specified file(s) which are not present when
> the tarball is being created.
In that case, simply use to check for those files before
running your tarball.
Or, even better, combine the task with the condition:
Thanks for the suggestions, David. In all of our cases we are using
to bundle many files. There are dozens of s specifying a
single file each, and those need to fail if the file doesn't exist.
Additional s use wildcards, and ideally those would also fail
if they didn't resolve to any actual file
If you're just tarring up a single file, then you can use available to
see if that file actually exists:
If you have more than one file and you want to make sure you have at
least one file to tar up, you can save your tarfileset as a
patternset, then use resourceCount against th
I'd like my task to fail if the files I specify don't exist. I
currently make use of the prefix, username, group and (sometimes) mode
attributes of , so I can't lose that functionality.
>From the Ant Manual, it looks like the new Resource Collection support
can handle this. But as a mere Ant us
Hello,
There are some interseting arguments to exec like spawn (standard is false) etc.
I never tried this, so someone else might know exactly.
But I think it is worth a try to use the exec task for a test and see what
happens.
I think it is possible to keep the settings of a Batchfile you run.
Thanks for the suggestion, but here is my problem:
1. These batch files are used at runtime from an end user after installing the
product with an installer.
2. Therefore, these batch files cannot be converted to ANT as that would
duplicate the logic and could get out of sync
3. I am trying to re
Hello,
I would translate the "bat" files to ANT-Tasks.
This is a lot of work, but than your Antfile can decide what bat-jobs you run
and when.
Another way is to run the bat-files itself inside Ant using the exec-task,
which is a bit tricky to handle.
To be honest: I dont like Batchfiles, so I
