[
https://issues.apache.org/jira/browse/IVY-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158968#comment-14158968
]
Shawn Heisey commented on IVY-1489:
-----------------------------------
A related problem, probably needs its own issue: The .lck files appear to be
created with a last modified timestamp equivalent to the unix epoch,
1970-01-01T00:00:00Z. Unless there's a particularly good reason for that, it
seems more useful for troubleshooting purposes to have them use the current
date.
> 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)
