[
https://issues.apache.org/jira/browse/IVY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756811#comment-16756811
]
Simon Wade commented on IVY-1602:
-
This was using the head of the master branch
[
https://issues.apache.org/jira/browse/IVY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756811#comment-16756811
]
Simon Wade edited comment on IVY-1602 at 1/31/19 3:07 AM:
--
This was using the head
[
https://issues.apache.org/jira/browse/IVY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756790#comment-16756790
]
jaikiran pai commented on IVY-1602:
---
Hello Simon,
Which version of Ivy is this?
> Cache corrupted when
[
https://issues.apache.org/jira/browse/IVY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai reassigned IVY-1602:
-
Assignee: jaikiran pai
> Cache corrupted when retrieves switch from directory symlink to copy
>
Simon Wade created IVY-1602:
---
Summary: Cache corrupted when retrieves switch from directory
symlink to copy
Key: IVY-1602
URL: https://issues.apache.org/jira/browse/IVY-1602
Project: Ivy
Issue
[
https://issues.apache.org/jira/browse/IVY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756685#comment-16756685
]
Simon Wade commented on IVY-1602:
-
I've attached a build.xml that can be used to reproduce the issue; you
[
https://issues.apache.org/jira/browse/IVY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Wade updated IVY-1602:
Attachment: IVY-1602.zip
> Cache corrupted when retrieves switch from directory symlink to copy
>
[
https://issues.apache.org/jira/browse/IVY-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755409#comment-16755409
]
Kenneth Preudhomme edited comment on IVY-1505 at 1/30/19 2:26 PM:
--
I'd
https://bz.apache.org/bugzilla/show_bug.cgi?id=62952
--- Comment #8 from Stefan Huehner ---
(In reply to Jaikiran Pai from comment #7)
> > Any chance to get a 1.10.6 out in short?
>
> I'll start a discussion on the dev list. I don't think we are waiting for
> any specific work to make it into