Yes - sigh - I've added all this functionality and a series of
dependencies to test for a symlink and then create them as needed.
I honestly think that branching every folder each time and asking
people to ignore via client spec is a better solution.
may
not always be the case.
On Feb 23, 2005, at 10:47 AM, Matt Benson wrote:
--- Edward Ciramella <[EMAIL PROTECTED]> wrote:
With overwrite set to true and failonerror set to
false, I still get
the link in the sub directory and the second time
it's run, I get the
build failed message.
With overwrite set to true and failonerror set to false, I still get
the link in the sub directory and the second time it's run, I get the
build failed message.
Here is the exact line from the build file:
On Feb 22, 2005, at 4:55 PM, Matt Benson wrote:
--- Edward Ciramella <[EMAIL P
of the symlink task makes no mention of this alternate
interpretation of the link entity specified as a
parameter to ln, but in the meantime your best course
will probably be to use indiscriminately the overwrite
attribute.
HTH,
Matt
--- Edward Ciramella <[EMAIL PROTECTED]> wrote:
Hello ant world -
Hello ant world - I'm attempting to create a symlink regardless if a
directory exists where the symlink is or if the symlink already exists.
What I'm seeing is kind of interesting.
Say I'm creating a symlink from /Users/username/test-link to
/Users/username/someotherdir/test-link
If the "to"
