[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849482#comment-17849482
]
Joe Witt commented on MNG-7868:
---
Thanks for the bump on the thread with that info. Moving
[nifi|https://issues.apache.org/jira/browse/NIFI-13300] to 3.9.7. initial
findings are encouraging. Will reply with any trouble.
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> 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)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849476#comment-17849476
]
Tamas Cservenak commented on MNG-7868:
--
All affected users: please upgrade to 3.9.7 and report back. The MRESOLVER-522
should fix the problem of "hot artifacts".
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> 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)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Maven 3.9.7 release notes [maven-site]
cstamas merged PR #521: URL: https://github.com/apache/maven-site/pull/521 -- 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
[jira] [Created] (MSITE-1009) Upgrade plugins and components (in ITs)
Michael Osipov created MSITE-1009: - Summary: Upgrade plugins and components (in ITs) Key: MSITE-1009 URL: https://issues.apache.org/jira/browse/MSITE-1009 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0, 4.0.0-M15 * Upgrade to Maven Doxia 2.0.0-M12 * Upgrade to Maven Doxia Sitetools 4.0.0-M19 * Upgrade to Maven Surefire Plugin 3.2.5 * Upgrade to Maven Plugin Tools 3.13.0 * Upgrade to Maven Reporting Impl 4.0.0-M15 * Upgrade to Maven Fluido Skin 2.0.0-M9 * Upgrade to Maven Reporting API 4.0.0-M12 * Upgrade to Maven Reporting Exec 2.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1404) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSHARED-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1404. --- Resolution: Fixed Fixed with [be97a272f3d605658df797fa59776f802c1ca527|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=be97a272f3d605658df797fa59776f802c1ca527]. > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1404 > URL: https://issues.apache.org/jira/browse/MSHARED-1404 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M14 > > > * Upgrade to Maven Site Plugin 4.0.0-M14 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Doxia 2.0.0-M12 > * Upgrade to Maven Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting Impl 4.0.0-M15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1404) Upgrade plugins and components (in ITs)
Michael Osipov created MSHARED-1404: --- Summary: Upgrade plugins and components (in ITs) Key: MSHARED-1404 URL: https://issues.apache.org/jira/browse/MSHARED-1404 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-exec Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-exec-2.0.0, maven-reporting-exec-2.0.0-M14 * Upgrade to Maven Site Plugin 4.0.0-M14 * Upgrade to Maven Reporting API 4.0.0-M12 * Upgrade to Maven Doxia 2.0.0-M12 * Upgrade to Maven Doxia Sitetools 2.0.0-M19 * Upgrade to Maven Reporting Impl 4.0.0-M15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-1811) Add resources to JPMS test module
[
https://issues.apache.org/jira/browse/SUREFIRE-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel_K updated SUREFIRE-1811:
--
Component/s: Maven Surefire Plugin
> Add resources to JPMS test module
> -
>
> Key: SUREFIRE-1811
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1811
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: Pavel_K
>Priority: Major
>
> I am testing version 3.0.0-M5 with two module-info in one project - one main
> and one for test. My test project is here
> https://github.com/PashaTurok/hibernate-h2-test4 . The problem is with
> resources. For example, I have src/main/resources/META-INF/persistence.xml
> file that is not copied to test module. Because of this it is not possible to
> find resource in test module and it is necessary to use something like this
> https://github.com/PashaTurok/hibernate-h2-test4/blob/292e2e683ad72487cbf8d2e5a35dde0d9255001a/src/test/java/com/foo/hibernate/h2/test4/TestIT.java#L72
> .
> In target/test-classes/META-INF/jpms.args I see:
> {code:java}
> --patch-module
> my.project=/home//hibernate-h2-test4/src/main/java,
> /home/.../hibernate-h2-test4/target/generated-sources/annotations
> {code}
> As I understand test module will NOT contain resources from the module under
> test? I mean that test module will NOT contain
> /home//hibernate-h2-test4/src/main/resources?
> That's why I suggest to include src/main/resources in test module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-1811) Add resources to JPMS test module
[
https://issues.apache.org/jira/browse/SUREFIRE-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849446#comment-17849446
]
Pavel_K commented on SUREFIRE-1811:
---
The problem still exists. For example, situation - one jpms module
{code:java}
module my.module {...}
{code}
with javafx css files and one test module with the same name
{code:java}
open module my.module {...}
{code}
in the same project. I can't execute tests because resources are absent. [~sor]
, could you say if you found a solution?
> Add resources to JPMS test module
> -
>
> Key: SUREFIRE-1811
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1811
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Failsafe Plugin
>Affects Versions: 3.0.0-M5
>Reporter: Pavel_K
>Priority: Major
>
> I am testing version 3.0.0-M5 with two module-info in one project - one main
> and one for test. My test project is here
> https://github.com/PashaTurok/hibernate-h2-test4 . The problem is with
> resources. For example, I have src/main/resources/META-INF/persistence.xml
> file that is not copied to test module. Because of this it is not possible to
> find resource in test module and it is necessary to use something like this
> https://github.com/PashaTurok/hibernate-h2-test4/blob/292e2e683ad72487cbf8d2e5a35dde0d9255001a/src/test/java/com/foo/hibernate/h2/test4/TestIT.java#L72
> .
> In target/test-classes/META-INF/jpms.args I see:
> {code:java}
> --patch-module
> my.project=/home//hibernate-h2-test4/src/main/java,
> /home/.../hibernate-h2-test4/target/generated-sources/annotations
> {code}
> As I understand test module will NOT contain resources from the module under
> test? I mean that test module will NOT contain
> /home//hibernate-h2-test4/src/main/resources?
> That's why I suggest to include src/main/resources in test module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.apache.maven.reporting:maven-reporting-api from 4.0.0-M11 to 4.0.0-M12 [maven-reporting-impl]
dependabot[bot] closed pull request #44: Bump org.apache.maven.reporting:maven-reporting-api from 4.0.0-M11 to 4.0.0-M12 URL: https://github.com/apache/maven-reporting-impl/pull/44 -- 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
Re: [PR] Bump doxiaVersion from 2.0.0-M10 to 2.0.0-M12 [maven-reporting-impl]
dependabot[bot] commented on PR #43: URL: https://github.com/apache/maven-reporting-impl/pull/43#issuecomment-2131156590 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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
Re: [PR] Bump org.apache.maven.reporting:maven-reporting-api from 4.0.0-M11 to 4.0.0-M12 [maven-reporting-impl]
dependabot[bot] commented on PR #44: URL: https://github.com/apache/maven-reporting-impl/pull/44#issuecomment-2131156596 Looks like org.apache.maven.reporting:maven-reporting-api is up-to-date now, so this is no longer needed. -- 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
Re: [PR] Bump doxiaVersion from 2.0.0-M10 to 2.0.0-M12 [maven-reporting-impl]
dependabot[bot] closed pull request #43: Bump doxiaVersion from 2.0.0-M10 to 2.0.0-M12 URL: https://github.com/apache/maven-reporting-impl/pull/43 -- 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
[jira] [Closed] (MSHARED-1402) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSHARED-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1402. --- Resolution: Fixed Fixed with [610c5230c447102f9899a7ae35d30541c3b1df6c|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=610c5230c447102f9899a7ae35d30541c3b1df6c]. > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1402 > URL: https://issues.apache.org/jira/browse/MSHARED-1402 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M15 > > > * Upgrade to Maven Doxia 2.0.0-M12 > * Upgrade to Maven Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Site Plugin 4.0.0-M15 > * Upgrade to Maven Plugin Tools 3.13.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-340) Rearrange title order in Velocity context
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-340:
--
Issue Type: Improvement (was: Dependency upgrade)
> Rearrange title order in Velocity context
> -
>
> Key: DOXIASITETOOLS-340
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-340
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 2.0.0-M18
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M19
>
>
> Currently, the title is set as follows:
> {projectName}} -- {{documentTitle}}
> This causes problems when you have multiple browsers tabs open, all you see
> is the project name not the document title, making is hard to identify. The
> common, today's approach is to go from specific to general: {{documentTitle}}
> -- {projectName}}. We should do the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1403) Configure log file as as File (not only file name relative to base directory)
[ https://issues.apache.org/jira/browse/MSHARED-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSHARED-1403. - Resolution: Fixed > Configure log file as as File (not only file name relative to base directory) > - > > Key: MSHARED-1403 > URL: https://issues.apache.org/jira/browse/MSHARED-1403 > Project: Maven Shared Components > Issue Type: Task > Components: maven-verifier >Affects Versions: maven-verifier-2.0.0-M1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1403) Configure log file as as File (not only file name relative to base directory)
[ https://issues.apache.org/jira/browse/MSHARED-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849444#comment-17849444 ] ASF GitHub Bot commented on MSHARED-1403: - olamy merged PR #89: URL: https://github.com/apache/maven-verifier/pull/89 > Configure log file as as File (not only file name relative to base directory) > - > > Key: MSHARED-1403 > URL: https://issues.apache.org/jira/browse/MSHARED-1403 > Project: Maven Shared Components > Issue Type: Task > Components: maven-verifier >Affects Versions: maven-verifier-2.0.0-M1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSHARED-1403] Configure log file as as File (not only file name relative to base directory) [maven-verifier]
olamy merged PR #89: URL: https://github.com/apache/maven-verifier/pull/89 -- 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
[jira] [Commented] (MPMD-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849442#comment-17849442 ] Michael Osipov commented on MPMD-391: - [~delany], there is a issue for this open for years. > Log what developers care about and not what they don't > -- > > Key: MPMD-391 > URL: https://issues.apache.org/jira/browse/MPMD-391 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Here's output from a recent PMD plugin run that failed: > [INFO] >>> maven-pmd-plugin:3.21.2:check (default-cli) > :pmd @ commons-io >>> > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:pmd (pmd) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > [INFO] > [INFO] <<< maven-pmd-plugin:3.21.2:check (default-cli) < :pmd @ commons-io <<< > [INFO] > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:check (default-cli) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 05:22 min > [INFO] Finished at: 2024-01-14T14:11:30Z > [INFO] > > Error: Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.21.2:check (default-cli) on > project commons-io: You have 1 PMD violation. For more details see: > /home/runner/work/commons-io/commons-io/target/pmd.xml -> [Help 1] > Error: > Error: To see the full stack trace of the errors, re-run Maven with the -e > switch. > Error: Re-run Maven using the -X switch to enable full debug logging. > Error: > Error: For more information about the errors and possible solutions, please > read the following articles: > Error: [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > Error: Process completed with exit code 1. > Things I don't care about that are printed: > * PMD version > * Doxia skin > * Blank lines > * Total time > * Timestamp when it finished > * Generic information about Mojo failures > * Exit code from Mojo > The one thing I care about: > * The actual error that caused the failure > Everything in the first list can be hidden in some random log file no one > will ever look at. Everything in the second list should be front and center. > Instead Maven gets this exactly backwards, -- This message was sent by Atlassian Jira (v8.20.10#820010)
