[
https://issues.apache.org/jira/browse/LUCENE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-6743.
---------------------------------
Resolution: Fixed
This issue is complete. I use the following in ~/build.properties for a nice
hassle free, no .ivy2 folder delete time, existence:
ivy.bootstrap.version=2.4.0
ivy_checksum_sha1=5abe4c24bbe992a9ac07ca563d5bd3e8d569e9ed
ivy.lock-strategy=artifact-lock-nio
I first removed ivy 2.3.0 from ~/.ant/lib and then used the ant ivy bootstrap
target to pull in 2.4.0. One time upgrade operation.
The hard part with making this the default is that many devs and users will
still have ivy 2.3.0 on the classpath and if we specify the artifact-lock-nio
in the config, that won't work AFAIK. We would need to do it somehow
conditionally I think. This provides an easy path for anyone else hitting these
issues now though.
> Allow Ivy lockStrategy to be overridden by system property.
> -----------------------------------------------------------
>
> Key: LUCENE-6743
> URL: https://issues.apache.org/jira/browse/LUCENE-6743
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: Trunk, 5.4
>
> Attachments: LUCENE-6743.patch
>
>
> The current hard code lock strategy is imperfect and can fail under parallel
> load. With Ivy 2.4 there is a better option in artifact-lock-nio. We should
> allow the lock strategy to be overrideen like the resolutionCacheDir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
