EJ, what you are seeing, AFAICT, is the by-design
behavior of the ln executable. We can debate whether
allowing this is a bug in Ant, since the documentation
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 - 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" is an actual directory, the symlink gets
> created as a
> subdirectory of
> /Users/username/someotherdir/test-link.
>
> So you wind up with something like:
> /Users/username/someotherdir/test-link/test-link
>
> I also noticed that if run twice, with overwrite
> false, I wind up with
> another subdirectory as explained above. We have
> some branches that
> don't have every directory branched (from parent to
> child) and people
> are using symlinks. Is there another way to do
> this?
>
> I looked around a bit in search of bugs against the
> symlink target, but
> I couldn't find anything that looked like what I'm
> up against.
>
> Any comments/help would be great.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
