[MNG-5838] Maven on No-File-Lock Systems

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.3, 3.3.9
• Fix Version/s: 3.8.2, 4.0.0-alpha-2, 4.0.0
• Assignee: Michael Osipov
• Reporter: Shana Hutchison
• Created: 04/Jun/15 18:28
• Updated: 20/Oct/22 08:11
• Resolved: 09/Oct/20 18:27

Description

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?

Issue Links

• is fixed by: MRESOLVER-132 Remove synchronization in TrackingFileManager
• requires: MNG-6996 Upgrade Maven Resolver to 1.6.1