jglick opened a new issue, #836:
URL: https://github.com/apache/maven-mvnd/issues/836
I just upgraded mvnd to 1.0-m6-m39 via Snap from 0.9.0 (using Java 11) and
ran a build of my reactor with 27 modules as usual (max parallelism 11). It
spat out some errors such as
```
Could not acquire write lock for
'~/.m2/repository/.locks/com.github.spotbugs~spotbugs-annotations~4.7.3.lock'
Could not acquire write lock for
'~/.m2/repository/.locks/commons-collections~commons-collections~3.2.2.lock'
```
and the build failed partway through
```
Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
(enforce-bytecode-version) on project …: Execution enforce-bytecode-version of
goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce failed: Could
not acquire write lock for
'~/.m2/repository/.locks/groupId~artifactId~1.234.lock' -> [Help 1]
Failed to execute goal some:plugin:1.2:some-mojo (default-some-mojo) on
project …: Execution default-some-mojo of goal some:plugin:1.2:some-mojo
failed: Could not acquire write lock for
'~/.m2/repository/.locks/groupId2~artifactId2~5.678.lock' -> [Help 1]
Could not acquire write lock for
'~/.m2/repository/.locks/groupId3~artifactId3~9.012.lock'
```
When I ran the build again, it passes, so I presume this was some sort of
race condition, possibly involving artifact downloads (I had pulled in various
POM updates since the last local build of the project).
No further details were provided, and I was not using `-e` so there was no
stack trace giving context. I checked `~/.m2/mvnd/registry/1.0-m6/daemon-*.log`
which did not really add any more information:
```
Dispatch message: ExecutionFailure{projectId='…', halted=true,
exception='java.lang.IllegalStateException: Could not acquire write lock for
'~/.m2/repository/.locks/com.github.spotbugs~spotbugs-annotations~4.7.3.lock''}
```
If nothing else, the `Throwable.toString` of the cause ought to be included
in the top-level error message I think.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
