[jira] [Commented] (IVY-1489) Still seeing *.lck files if ivy is aborted abruptly

["jaikiran pai (JIRA)" <ji...@apache.org>]

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

jaikiran pai commented on IVY-1489:
-----------------------------------

[~medboz], [~elyograg],
Ivy 2.4 introduced {{artifact-lock-nio}} as noted in the doc here https://ant.apache.org/ivy/history/latest-milestone/settings/lock-strategies.html which is much more reliable. Can you give that a try and see if that works for you?

> Still seeing *.lck files if ivy is aborted abruptly
> ---------------------------------------------------
>
>                 Key: IVY-1489
>                 URL: https://issues.apache.org/jira/browse/IVY-1489
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>         Environment: Linux sauron 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.7.0_67"
> Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
>            Reporter: Shawn Heisey
>
> IVY-1388 is still happening after upgrading to 2.3.0.
> For me, this is seen when building the lucene-solr project.  Frequently after starting a build I will realize that I've typed the ant command line wrong, or that I haven't fixed a problem correctly, so I will use ctrl-c to abort the build, fix the problem, and start it back up.  Often the interruption will result in a .lck file being left behind and the build hanging at "resolve:" until the .lck file is deleted.



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