You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2015/09/06 14:21:45 UTC

[jira] [Commented] (IVY-1498) Mixed use of symlinks leads to cache corruption

    [ https://issues.apache.org/jira/browse/IVY-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732361#comment-14732361 ] 

Nicolas Lalevée commented on IVY-1498:
--------------------------------------

The fixes you pointed is not available anymore. Do you still have it somewhere ?

Even if Ivy doesn't require Java 7, and if the only way to properly fix it is too use that API, we could image that we could do some conditional code which test for the availability of that API, and use it only if available; and we would recommend to use Java 7 if people want to use symlinks with Ivy.

> Mixed use of symlinks leads to cache corruption
> -----------------------------------------------
>
>                 Key: IVY-1498
>                 URL: https://issues.apache.org/jira/browse/IVY-1498
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>            Reporter: Stephen Haberman
>            Priority: Blocker
>
> If a user switches between "use symlinks" or not (or, say, has ant/ivy configured with symlinks but Eclipse/IvyDE without symlinks), the ivycache can be corrupted.
> Specifically, if a symlink was setup in symlink mode:
> lib/foo.jar --> ivycache/com/foo/foo-1.2.jar
> And then later we retrieve into lib without symlink mode, Ivy retrieve will write, say, foo-1.3.jar's bytes into the lib/foo.jar location...which will then overwrite the foo-1.2.jar bytes in the ivycache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)