[GitHub] [maven-mvnd] hohwille commented on issue #836: `Could not acquire write lock for…` errors

2023-09-05 Thread via GitHub 


hohwille commented on issue #836:
URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1706508653

   I was now able to reproduce the lock errors also with pure maven and without 
mvnd.
   Therefore I created 
[MNG-7868](https://issues.apache.org/jira/browse/MNG-7868).
   IMHO this issue here is kind of invalid as it is a bug in maven itself and 
not in mvnd.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-mvnd] hohwille commented on issue #836: `Could not acquire write lock for…` errors

2023-09-01 Thread via GitHub 


hohwille commented on issue #836:
URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702409617

   ```
   $ mvnd -v
   Apache Maven Daemon (mvnd) 1.0-m7 windows-amd64 native client 
(b2ef5d81997adbcdb72dc8c5603722538fa641fe)
   Terminal: org.jline.terminal.impl.jansi.win.JansiWinSysTerminal
   Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
   Maven home: D:\projects\salog\software\mvnd\mvn
   Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: 
D:\projects\salog\software\java
   Default locale: en_US, platform encoding: UTF-8
   OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
   ```
   
   But I also get this:
   ```
   Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire 
write lock for 
'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
 in 30 SECONDS
   at 
org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
 (NamedLockFactoryAdapter.java:202)
   at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve 
(DefaultArtifactResolver.java:271)
   at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts 
(DefaultArtifactResolver.java:259)
   at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies 
(DefaultRepositorySystem.java:352)
   ```
   
   Windows Filesystem and file-locking is a disaster. However, with regular 
`mvn` the error does not occur even not when I run parallel builds (e.g. `-T 
2C`). Please also note that also with `mvnd` the error goes away if I do not 
specify concurrent build (no `-T` option).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org