[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370082#comment-17370082
 ] 

Michael Osipov commented on MNG-5838:
-

Maven Resolver 1.6.2 will be available with Maven 3.8.2 so this has been 
addressed in 3.8.x too.

> 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
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.8.2, 4.0.0, 4.0.0-alpha-1
>
>
> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205530#comment-17205530
 ] 

Michael Osipov commented on MNG-5838:
-

This one is coming with Maven Resolver 1.6.1, finally.

> 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
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.7.0-candidate
>
>
> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178956#comment-17178956
 ] 

Michael Osipov commented on MNG-5838:
-

This can/will be solved with MRESOLVER-132. In short, I see that locking as 
wrong.

> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Sylwester Lachiewicz (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741670#comment-16741670
 ] 

Sylwester Lachiewicz commented on MNG-5838:
---

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: Dylan 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:
> 
> Scroll down halfway for the second file.
> Is there an option to disable file locking?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Dylan Hutchison (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321896#comment-15321896
 ] 

Dylan Hutchison commented on MNG-5838:
--

[~michael-o], I just checked this on version 3.3.9 and the problem is still 
here. 

Currently we are working around this issue by version-locking our cluster to 
Maven 3.2.3. Let me know if I can help further. 

> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313023#comment-15313023
 ] 

Michael Osipov commented on MNG-5838:
-

I agree!

> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313021#comment-15313021
 ] 

Karl Heinz Marbaise commented on MNG-5838:
--

But we are waiting to integrate the Aether code...so we might keep it open and 
may be move it later to the Aether component ?

> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312997#comment-15312997
 ] 

Michael Osipov commented on MNG-5838:
-

[~dhutchis], does this still happens with master? [~khmarbaise], I am inclined 
to close this one becuse this is a Aether issue and not a Maven one. The only 
place where {{lock()}} is called is Maven Compat.

> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Dylan Hutchison (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051233#comment-15051233
 ] 

Dylan Hutchison commented on MNG-5838:
--

Yes, it is a low level error-- the 
[java.nio.channels.FileChannel.lock|https://docs.oracle.com/javase/7/docs/api/java/nio/channels/FileChannel.html#lock(long,%20long,%20boolean)]
 method is not implemented on file systems that do not support file locking, 
like Lustre.  Is there some way to make Maven not use file locking?  

You can see the lock method being called 
[here|http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.aether/aether-ant-tasks/1.0.0.v20140518/org/eclipse/aether/internal/impl/TrackingFileManager.java#203].

What I don't know is why this build works (albeit with warnings) on Maven 3.2.3 
but fails on 3.3.3.

> 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:
> 
> 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)

[jira] [Commented] (MNG-5838) Maven on No-File-Lock Systems

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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:
> 
> 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)