ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Resolved: (IVY-1165) During retreieve: Creation of symlinks problematic in Windows with Cygwin 1.7
Date Wed, 03 Feb 2010 21:07:28 GMT


Maarten Coene resolved IVY-1165.

    Resolution: Fixed

I've tried another approach and committed it to svn trunk, could you please give it a try?
The reason is that I want to avoid changing the existing FileUtils.copy-code because it could
give unexpected side-effects, so it seemed better to me if that code could be left untouched...


> During retreieve: Creation of symlinks problematic in Windows with Cygwin 1.7
> -----------------------------------------------------------------------------
>                 Key: IVY-1165
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.1.0-RC2
>         Environment: Windows 7 64 bit
> Cygwin 1.7
> Cygwin's bin directory on PATH
>            Reporter: John Brandy
>            Assignee: Maarten Coene
>             Fix For: trunk
> On Windows with the Cygwin 1.7 bin directory on the PATH, Ivy will create a ~1kb "symlink"
file instead of copying the jar to the ivylib directory. This causes the retrieve process
to fail.
> As described in [IVY-353|], the creation
of symlinks with cygwin was problematic  for Windows systems. The fix as I understand it was
to attempt to create a symlink, if that failed (the expected file did not exist) then copy
the jar. That worked with the default configuration of Cygwin 1.5 which attempted to create
Windows link (file.lnk) files. However as of 1.7 cygwin does not default to that behavior
anymore and now Ivy fails in this case. 
> For either version, if cygwin's environment option "winsymlinks" is turned to off --
which 1.7 defaults to -- then Ivy won't successfully retrieve due to thinking that the creation
of a symlink was successful.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message