[
https://issues.apache.org/jira/browse/MNG-7748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704781#comment-17704781
]
Dan Mclaughlin commented on MNG-7748:
-------------------------------------
I moved the property to our .mvn/maven.config, and 120 seems to have solved it.
The builds are almost complete, and they would have failed by now. I look
forward to testing 3.9.2, so we can remove that property. I prefer to tweak the
defaults only if necessary, so our builds will work without too many
maven-specific customizations.
> Several plug-ins fail during parallel build on Maven 3.9.x
> ----------------------------------------------------------
>
> Key: MNG-7748
> URL: https://issues.apache.org/jira/browse/MNG-7748
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.9.0, 3.9.1
> Environment: The error happens on every platform we build on: Linux,
> OSX, and Windows. We are using JDK 19.
> Reporter: Dan Mclaughlin
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> We have a multi-module build that we have been doing parallel builds on for
> years using the -T1C build parameter. As soon as we moved to Maven 3.9.0
> (and we've tried 3.9.1) we keep getting several plugins that fail at random
> with a "Could not acquire write lock for" error message. If we simply move
> back to Maven 3.8.x then things work fine. We can also set -T1 so the build
> only uses one thread and then things work.
> {noformat}
> *11:02:23* [ERROR] Failed to execute goal
> org.owasp:dependency-check-maven:8.1.2:check (default) on project
> cris-common-utils: Execution default of goal
> org.owasp:dependency-check-maven:8.1.2:check failed: Could not acquire write
> lock for 'artifact:org.apache.logging.log4j:log4j-api:2.20.0' -> [Help 1]
> *11:02:23* [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
> (enforce-bytecode-version) on project cris-jakarta-transform: Execution
> enforce-bytecode-version of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could
> not acquire write lock for 'artifact:org.slf4j:slf4j-api:2.0.6' -> [Help 1]
> *11:02:23* [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
> (enforce-bytecode-version) on project cris-authservice: Execution
> enforce-bytecode-version of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could
> not acquire write lock for 'artifact:org.slf4j:slf4j-api:2.0.6' -> [Help 1]
> *11:02:23* [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
> (enforce-bytecode-version) on project cris-swing-components: Execution
> enforce-bytecode-version of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could
> not acquire write lock for 'artifact:org.slf4j:slf4j-api:2.0.6' -> [Help 1]
> *11:02:23* [ERROR] Could not acquire write lock for
> 'artifact:org.apache.logging.log4j:log4j-api:2.20.0'
> *11:02:23* [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
> (enforce-bytecode-version) on project cris-internalservices: Execution
> enforce-bytecode-version of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could
> not acquire write lock for 'artifact:org.slf4j:slf4j-api:2.0.6' -> [Help 1]
> *11:02:23* [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
> (enforce-bytecode-version) on project cris-common-xmldata: Execution
> enforce-bytecode-version of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could
> not acquire write lock for 'artifact:org.slf4j:slf4j-api:2.0.6' -> [Help 1]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
