[
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741670#comment-16741670
]
Michael Osipov edited comment on MNG-5838 at 8/17/20, 12:38 PM:
----------------------------------------------------------------
We have calls to {{lock()}} also in {{maven-resolver-impl}} in
{{org.eclipse.aether.internal.impl.TrackingFileManager#lock()}}.
was (Author: slachiewicz):
We have calls to lock() also in maven_-resolver-_impl in
_org.eclipse.aether.internal.impl.TrackingFileManager#lock_
> Maven on No-File-Lock Systems
> -----------------------------
>
> Key: MNG-5838
> URL: https://issues.apache.org/jira/browse/MNG-5838
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.3, 3.3.9
> Reporter: Shana Hutchison
> Priority: Major
>
> I work on a Lustre file system that does not support file locking. Maven
> emits tons of warnings when it cannot lock a file due to IOExceptions. In my
> case this is not a problem because I only run one maven process at a time and
> the .m2 directory inside my home directory is not shared, so there is no need
> to lock files.
> Maven built correctly despite the warnings when using Maven 3.2.3. Then, when
> I upgraded to Maven 3.3.3, Maven failed on most goals, even clean. I'd like
> to at least compile my code with mvn on this system with no file locking,
> even if it can't run project tests.
> I uploaded log files for running with 3.2.3 and 3.3.3 here:
> <https://gist.github.com/a0099ea87e5ac663b2ac>
> Scroll down halfway for the second file.
> Is there an option to disable file locking?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
