Dylan Hutchison created MNG-5838:
------------------------------------
Summary: 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
Reporter: Dylan Hutchison
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
(v6.3.4#6332)
