[ https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995678#comment-14995678 ]
Karl Heinz Marbaise commented on MNG-5838: ------------------------------------------ If you take a deeper look into the output you can see things like this: {noformat} java.io.IOException: Function not implemented at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:91) at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1022) {noformat} which means this on very low level in Java Code and here in the Java classes itself...You might check the OpenJDK JVM documentations if you find something... > 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)