[PR] Bump org.cyclonedx:cyclonedx-maven-plugin from 2.7.11 to 2.8.0 [maven-parent]
dependabot[bot] opened a new pull request, #167: URL: https://github.com/apache/maven-parent/pull/167 Bumps [org.cyclonedx:cyclonedx-maven-plugin](https://github.com/CycloneDX/cyclonedx-maven-plugin) from 2.7.11 to 2.8.0. Release notes Sourced from https://github.com/CycloneDX/cyclonedx-maven-plugin/releases;>org.cyclonedx:cyclonedx-maven-plugin's releases. 2.8.0 Update CycloneDX Description Text (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/461;>#461) https://github.com/msymons;>@msymons New features and improvements convert external reference type by value instead of CONSTANT_NAME (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/480;>#480) https://github.com/hboutemy;>@hboutemy distribution-intake external reference is more accurate (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/477;>#477) https://github.com/hboutemy;>@hboutemy add 'build' lifecycle when CDX 1.5 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/462;>#462) https://github.com/hboutemy;>@hboutemy document SBOM external references (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/459;>#459) https://github.com/hboutemy;>@hboutemy improve site generation (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/458;>#458) https://github.com/hboutemy;>@hboutemy upgrade to CycloneDX 1.5 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/457;>#457) https://github.com/hboutemy;>@hboutemy Bug Fixes check if configured schemaVersion is supported (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/479;>#479) https://github.com/hboutemy;>@hboutemy Dependency updates Bump org.apache.maven.plugins:maven-compiler-plugin from 3.12.1 to 3.13.0 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/478;>#478) https://github.com/dependabot;>@dependabot Bump actions/checkout from 4.1.1 to 4.1.2 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/474;>#474) https://github.com/dependabot;>@dependabot Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0 in /src/it/makeAggregateBom/util (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/468;>#468) https://github.com/dependabot;>@dependabot Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/465;>#465) https://github.com/dependabot;>@dependabot Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/464;>#464) https://github.com/dependabot;>@dependabot Bump commons-codec:commons-codec from 1.16.0 to 1.16.1 (https://redirect.github.com/CycloneDX/cyclonedx-maven-plugin/pull/466;>#466) https://github.com/dependabot;>@dependabot Commits https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/90e38178a7480b10b0f225cf6c2bc2f26b5a6eab;>90e3817 [maven-release-plugin] prepare release cyclonedx-maven-plugin-2.8.0 https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/eed838e3a76712054ff8eeeb0af04c64a7d0bd26;>eed838e convert external reference type by value instead of default CONSTANT_NAME https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/3fd83bf3fef57fb5569cff378637b903ca39bf45;>3fd83bf Bump org.apache.maven.plugins:maven-compiler-plugin https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/343c62dfe4a8bd983c1c77e06d37b8f285f09dbb;>343c62d check if configured schemaVersion is supported https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/d0015429ef13f79503bb6d17e3b66f59a1b408a2;>d001542 distribution-intake external reference is more accurate https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/fa5541d39a58d6f09ec3b7a9a2ad1b8d7682bb18;>fa5541d Bump actions/checkout from 4.1.1 to 4.1.2 https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/a43cd056f3d6f319ff6e3de83cb62ebd9b2e29ec;>a43cd05 Bump org.apache.commons:commons-compress https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/31ff1f46643f888f91a27f02d9e82828f9b5590d;>31ff1f4 Bump org.junit:junit-bom from 5.10.1 to 5.10.2 https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/ce8a6e70afbf2c7307f9a4a449ce8f4c80e03dc2;>ce8a6e7 Bump release-drafter/release-drafter from 5 to 6 https://github.com/CycloneDX/cyclonedx-maven-plugin/commit/16dcb5b62fefe642cd29360141c512fd1ddcf2c0;>16dcb5b Bump commons-codec:commons-codec from 1.16.0 to 1.16.1 Additional commits viewable in https://github.com/CycloneDX/cyclonedx-maven-plugin/compare/cyclonedx-maven-plugin-2.7.11...cyclonedx-maven-plugin-2.8.0;>compare view [![Dependabot compatibility
[PR] Bump org.ow2.asm:asm from 9.6 to 9.7 [maven-dependency-analyzer]
dependabot[bot] opened a new pull request, #112: URL: https://github.com/apache/maven-dependency-analyzer/pull/112 Bumps org.ow2.asm:asm from 9.6 to 9.7. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[PR] Bump asmVersion from 9.6 to 9.7 [maven-shade-plugin]
dependabot[bot] opened a new pull request, #218: URL: https://github.com/apache/maven-shade-plugin/pull/218 Bumps `asmVersion` from 9.6 to 9.7. Updates `org.ow2.asm:asm` from 9.6 to 9.7 Updates `org.ow2.asm:asm-commons` from 9.6 to 9.7 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[PR] Bump org.mockito:mockito-junit-jupiter from 4.11.0 to 5.11.0 [maven-jar-plugin]
dependabot[bot] opened a new pull request, #76: URL: https://github.com/apache/maven-jar-plugin/pull/76 Bumps [org.mockito:mockito-junit-jupiter](https://github.com/mockito/mockito) from 4.11.0 to 5.11.0. Release notes Sourced from https://github.com/mockito/mockito/releases;>org.mockito:mockito-junit-jupiter's releases. v5.11.0 Changelog generated by https://github.com/shipkit/shipkit-changelog;>Shipkit Changelog Gradle Plugin 5.11.0 2024-03-01 - https://github.com/mockito/mockito/compare/v5.10.0...v5.11.0;>17 commit(s) by Aouichaoui Youssef, Franz Wong, Pranoti Durugkar, Róbert Papp, dependabot[bot] Fixes https://redirect.github.com/mockito/mockito/issues/3281;>#3281 : Add native method to exception message of MissingMethodI… [(https://redirect.github.com/mockito/mockito/issues/3283;>#3283)](https://redirect.github.com/mockito/mockito/pull/3283;>mockito/mockito#3283) MissingMethodInvocationException is thrown when mocking native method in 5.x [(https://redirect.github.com/mockito/mockito/issues/3281;>#3281)](https://redirect.github.com/mockito/mockito/issues/3281;>mockito/mockito#3281) Bump com.google.googlejavaformat:google-java-format from 1.19.2 to 1.20.0 [(https://redirect.github.com/mockito/mockito/issues/3277;>#3277)](https://redirect.github.com/mockito/mockito/pull/3277;>mockito/mockito#3277) Bump versions.bytebuddy from 1.14.11 to 1.14.12 [(https://redirect.github.com/mockito/mockito/issues/3272;>#3272)](https://redirect.github.com/mockito/mockito/pull/3272;>mockito/mockito#3272) Bump gradle/wrapper-validation-action from 2.1.0 to 2.1.1 [(https://redirect.github.com/mockito/mockito/issues/3268;>#3268)](https://redirect.github.com/mockito/mockito/pull/3268;>mockito/mockito#3268) Bump org.shipkit:shipkit-auto-version from 2.0.3 to 2.0.4 [(https://redirect.github.com/mockito/mockito/issues/3267;>#3267)](https://redirect.github.com/mockito/mockito/pull/3267;>mockito/mockito#3267) Bump gradle/wrapper-validation-action from 2.0.1 to 2.1.0 [(https://redirect.github.com/mockito/mockito/issues/3266;>#3266)](https://redirect.github.com/mockito/mockito/pull/3266;>mockito/mockito#3266) Bump org.junit.platform:junit-platform-launcher from 1.10.1 to 1.10.2 [(https://redirect.github.com/mockito/mockito/issues/3265;>#3265)](https://redirect.github.com/mockito/mockito/pull/3265;>mockito/mockito#3265) Bump gradle/wrapper-validation-action from 2.0.0 to 2.0.1 [(https://redirect.github.com/mockito/mockito/issues/3264;>#3264)](https://redirect.github.com/mockito/mockito/pull/3264;>mockito/mockito#3264) Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 [(https://redirect.github.com/mockito/mockito/issues/3261;>#3261)](https://redirect.github.com/mockito/mockito/pull/3261;>mockito/mockito#3261) Bump versions.junitJupiter from 5.10.1 to 5.10.2 [(https://redirect.github.com/mockito/mockito/issues/3260;>#3260)](https://redirect.github.com/mockito/mockito/pull/3260;>mockito/mockito#3260) Bump gradle/wrapper-validation-action from 1.1.0 to 2.0.0 [(https://redirect.github.com/mockito/mockito/issues/3258;>#3258)](https://redirect.github.com/mockito/mockito/pull/3258;>mockito/mockito#3258) Fixes https://redirect.github.com/mockito/mockito/issues/3229;>#3229: Resolve test generic arguments [(https://redirect.github.com/mockito/mockito/issues/3257;>#3257)](https://redirect.github.com/mockito/mockito/pull/3257;>mockito/mockito#3257) Bump org.shipkit:shipkit-auto-version from 2.0.2 to 2.0.3 [(https://redirect.github.com/mockito/mockito/issues/3256;>#3256)](https://redirect.github.com/mockito/mockito/pull/3256;>mockito/mockito#3256) Use kvm on ubuntu instead of macos to run Android tests [(https://redirect.github.com/mockito/mockito/issues/3252;>#3252)](https://redirect.github.com/mockito/mockito/pull/3252;>mockito/mockito#3252) Fixes https://redirect.github.com/mockito/mockito/issues/3240;>#3240 : Renamed mockito bom artifact [(https://redirect.github.com/mockito/mockito/issues/3251;>#3251)](https://redirect.github.com/mockito/mockito/pull/3251;>mockito/mockito#3251) Remove shipkit workaround for generateChangelog [(https://redirect.github.com/mockito/mockito/issues/3250;>#3250)](https://redirect.github.com/mockito/mockito/pull/3250;>mockito/mockito#3250) Bump com.gradle.enterprise from 3.16.1 to 3.16.2 [(https://redirect.github.com/mockito/mockito/issues/3249;>#3249)](https://redirect.github.com/mockito/mockito/pull/3249;>mockito/mockito#3249) Mockito bom missing artifact in maven central for java21 [(https://redirect.github.com/mockito/mockito/issues/3240;>#3240)](https://redirect.github.com/mockito/mockito/issues/3240;>mockito/mockito#3240) @Captor test parameters don't work with primitive type arguments [(https://redirect.github.com/mockito/mockito/issues/3229;>#3229)](https://redirect.github.com/mockito/mockito/issues/3229;>mockito/mockito#3229) Gradle 8.2: work around fix for release publishing
[PR] Bump org.mockito:mockito-core from 4.11.0 to 5.11.0 [maven-jar-plugin]
dependabot[bot] opened a new pull request, #75: URL: https://github.com/apache/maven-jar-plugin/pull/75 Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 4.11.0 to 5.11.0. Release notes Sourced from https://github.com/mockito/mockito/releases;>org.mockito:mockito-core's releases. v5.11.0 Changelog generated by https://github.com/shipkit/shipkit-changelog;>Shipkit Changelog Gradle Plugin 5.11.0 2024-03-01 - https://github.com/mockito/mockito/compare/v5.10.0...v5.11.0;>17 commit(s) by Aouichaoui Youssef, Franz Wong, Pranoti Durugkar, Róbert Papp, dependabot[bot] Fixes https://redirect.github.com/mockito/mockito/issues/3281;>#3281 : Add native method to exception message of MissingMethodI… [(https://redirect.github.com/mockito/mockito/issues/3283;>#3283)](https://redirect.github.com/mockito/mockito/pull/3283;>mockito/mockito#3283) MissingMethodInvocationException is thrown when mocking native method in 5.x [(https://redirect.github.com/mockito/mockito/issues/3281;>#3281)](https://redirect.github.com/mockito/mockito/issues/3281;>mockito/mockito#3281) Bump com.google.googlejavaformat:google-java-format from 1.19.2 to 1.20.0 [(https://redirect.github.com/mockito/mockito/issues/3277;>#3277)](https://redirect.github.com/mockito/mockito/pull/3277;>mockito/mockito#3277) Bump versions.bytebuddy from 1.14.11 to 1.14.12 [(https://redirect.github.com/mockito/mockito/issues/3272;>#3272)](https://redirect.github.com/mockito/mockito/pull/3272;>mockito/mockito#3272) Bump gradle/wrapper-validation-action from 2.1.0 to 2.1.1 [(https://redirect.github.com/mockito/mockito/issues/3268;>#3268)](https://redirect.github.com/mockito/mockito/pull/3268;>mockito/mockito#3268) Bump org.shipkit:shipkit-auto-version from 2.0.3 to 2.0.4 [(https://redirect.github.com/mockito/mockito/issues/3267;>#3267)](https://redirect.github.com/mockito/mockito/pull/3267;>mockito/mockito#3267) Bump gradle/wrapper-validation-action from 2.0.1 to 2.1.0 [(https://redirect.github.com/mockito/mockito/issues/3266;>#3266)](https://redirect.github.com/mockito/mockito/pull/3266;>mockito/mockito#3266) Bump org.junit.platform:junit-platform-launcher from 1.10.1 to 1.10.2 [(https://redirect.github.com/mockito/mockito/issues/3265;>#3265)](https://redirect.github.com/mockito/mockito/pull/3265;>mockito/mockito#3265) Bump gradle/wrapper-validation-action from 2.0.0 to 2.0.1 [(https://redirect.github.com/mockito/mockito/issues/3264;>#3264)](https://redirect.github.com/mockito/mockito/pull/3264;>mockito/mockito#3264) Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 [(https://redirect.github.com/mockito/mockito/issues/3261;>#3261)](https://redirect.github.com/mockito/mockito/pull/3261;>mockito/mockito#3261) Bump versions.junitJupiter from 5.10.1 to 5.10.2 [(https://redirect.github.com/mockito/mockito/issues/3260;>#3260)](https://redirect.github.com/mockito/mockito/pull/3260;>mockito/mockito#3260) Bump gradle/wrapper-validation-action from 1.1.0 to 2.0.0 [(https://redirect.github.com/mockito/mockito/issues/3258;>#3258)](https://redirect.github.com/mockito/mockito/pull/3258;>mockito/mockito#3258) Fixes https://redirect.github.com/mockito/mockito/issues/3229;>#3229: Resolve test generic arguments [(https://redirect.github.com/mockito/mockito/issues/3257;>#3257)](https://redirect.github.com/mockito/mockito/pull/3257;>mockito/mockito#3257) Bump org.shipkit:shipkit-auto-version from 2.0.2 to 2.0.3 [(https://redirect.github.com/mockito/mockito/issues/3256;>#3256)](https://redirect.github.com/mockito/mockito/pull/3256;>mockito/mockito#3256) Use kvm on ubuntu instead of macos to run Android tests [(https://redirect.github.com/mockito/mockito/issues/3252;>#3252)](https://redirect.github.com/mockito/mockito/pull/3252;>mockito/mockito#3252) Fixes https://redirect.github.com/mockito/mockito/issues/3240;>#3240 : Renamed mockito bom artifact [(https://redirect.github.com/mockito/mockito/issues/3251;>#3251)](https://redirect.github.com/mockito/mockito/pull/3251;>mockito/mockito#3251) Remove shipkit workaround for generateChangelog [(https://redirect.github.com/mockito/mockito/issues/3250;>#3250)](https://redirect.github.com/mockito/mockito/pull/3250;>mockito/mockito#3250) Bump com.gradle.enterprise from 3.16.1 to 3.16.2 [(https://redirect.github.com/mockito/mockito/issues/3249;>#3249)](https://redirect.github.com/mockito/mockito/pull/3249;>mockito/mockito#3249) Mockito bom missing artifact in maven central for java21 [(https://redirect.github.com/mockito/mockito/issues/3240;>#3240)](https://redirect.github.com/mockito/mockito/issues/3240;>mockito/mockito#3240) @Captor test parameters don't work with primitive type arguments [(https://redirect.github.com/mockito/mockito/issues/3229;>#3229)](https://redirect.github.com/mockito/mockito/issues/3229;>mockito/mockito#3229) Gradle 8.2: work around fix for release publishing
[PR] Bump org.junit:junit-bom from 5.10.1 to 5.10.2 [maven-jar-plugin]
dependabot[bot] opened a new pull request, #74: URL: https://github.com/apache/maven-jar-plugin/pull/74 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.1 to 5.10.2. Release notes Sourced from https://github.com/junit-team/junit5/releases;>org.junit:junit-bom's releases. JUnit 5.10.2 = Platform 1.10.2 + Jupiter 5.10.2 + Vintage 5.10.2 See http://junit.org/junit5/docs/5.10.2/release-notes/;>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.1...r5.10.2;>https://github.com/junit-team/junit5/compare/r5.10.1...r5.10.2 Commits https://github.com/junit-team/junit5/commit/4c0dddad1b96d4a20e92a2cd583954643ac56ac0;>4c0ddda Release 5.10.2 https://github.com/junit-team/junit5/commit/463a14773d884f2bf31f073a87bef9d0938872db;>463a147 Finalize release notes for 5.10.2 https://github.com/junit-team/junit5/commit/43c105a246c0130d08145335cb9986236e2a8465;>43c105a Revert Apply method predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/63d464d1e10a62743fe4024436ef1e006a89df72;>63d464d Revert Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/85ec2fccb32a51fbe6ff966e25726c94a67dd418;>85ec2fc Revert Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/6209006a7693dbf6f680a5ac4541aba86c9da899;>6209006 Update release notes https://github.com/junit-team/junit5/commit/5ee499f0e0029dbd1120ecf889bd214e2082c589;>5ee499f Fix CI build https://github.com/junit-team/junit5/commit/d919ba71ea4c3b1e60f2d21473ba31ff0f6857ab;>d919ba7 Namespace user-specific build parameters https://github.com/junit-team/junit5/commit/e26cd83ed307ef100399ced9985f04612931984b;>e26cd83 Prepare release notes for 5.10.2 https://github.com/junit-team/junit5/commit/ec8d4282c60f480d3de264330b37e75b1b8d05d9;>ec8d428 Include LauncherInterceptor in launcher module declaration Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.1...r5.10.2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-1367) Improvement in unit tests
[ https://issues.apache.org/jira/browse/MSHARED-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1367. Resolution: Fixed > Improvement in unit tests > - > > Key: MSHARED-1367 > URL: https://issues.apache.org/jira/browse/MSHARED-1367 > Project: Maven Shared Components > Issue Type: Task > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1367) Improvement in unit tests
[ https://issues.apache.org/jira/browse/MSHARED-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830299#comment-17830299 ] ASF GitHub Bot commented on MSHARED-1367: - slawekjaranowski merged PR #56: URL: https://github.com/apache/maven-archiver/pull/56 > Improvement in unit tests > - > > Key: MSHARED-1367 > URL: https://issues.apache.org/jira/browse/MSHARED-1367 > Project: Maven Shared Components > Issue Type: Task > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSHARED-1367] Improvement in unit tests [maven-archiver]
slawekjaranowski merged PR #56: URL: https://github.com/apache/maven-archiver/pull/56 -- 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] (MSHARED-1367) Improvement in unit tests
[ https://issues.apache.org/jira/browse/MSHARED-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830298#comment-17830298 ] ASF GitHub Bot commented on MSHARED-1367: - slawekjaranowski opened a new pull request, #56: URL: https://github.com/apache/maven-archiver/pull/56 - use Mockito instead of own mock classes > Improvement in unit tests > - > > Key: MSHARED-1367 > URL: https://issues.apache.org/jira/browse/MSHARED-1367 > Project: Maven Shared Components > Issue Type: Task > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1367) Improvement in unit tests
Slawomir Jaranowski created MSHARED-1367: Summary: Improvement in unit tests Key: MSHARED-1367 URL: https://issues.apache.org/jira/browse/MSHARED-1367 Project: Maven Shared Components Issue Type: Task Components: maven-archiver Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-archiver-next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-8085. -- Resolution: Fixed > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7, 4.0.0-alpha-14 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ > and https://maven.apache.org/ref/4-LATEST/ vs previous > https://maven.apache.org/ref/4.0.0-alpha-13/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] configure javadoc groups [maven]
hboutemy merged PR #1454: URL: https://github.com/apache/maven/pull/1454 -- 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] (MPLUGIN-508) Upgrade to Maven 4.0.0-alpha-12
[ https://issues.apache.org/jira/browse/MPLUGIN-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830292#comment-17830292 ] ASF GitHub Bot commented on MPLUGIN-508: gnodet commented on PR #242: URL: https://github.com/apache/maven-plugin-tools/pull/242#issuecomment-2016909806 > I extracted from this huge PR updates that were not really related to Maven 4 alpha but cleanup that caused it hard to get the intent of the PR you'll need to rebase to get a more focused PR, that we'll be able to describe: from what I see, the upgrade adds some very new approach like DI that would be useful to describe > > I'd like to do a release next week: we'll need to define if we can get this update in or not The support for 4.x plugins cannot really be finalised before the API is, given this target is moving. However, we need to keep up to date so that we can work on plugins more easily. I think the plugin could be trimmed down (just the actual plugin, we don't need other modules) and moved to maven-core to support v4 plugins... > Upgrade to Maven 4.0.0-alpha-12 > --- > > Key: MPLUGIN-508 > URL: https://issues.apache.org/jira/browse/MPLUGIN-508 > Project: Maven Plugin Tools > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-508] Upgrade to Maven 4.0.0-alpha-13 [maven-plugin-tools]
gnodet commented on PR #242: URL: https://github.com/apache/maven-plugin-tools/pull/242#issuecomment-2016909806 > I extracted from this huge PR updates that were not really related to Maven 4 alpha but cleanup that caused it hard to get the intent of the PR you'll need to rebase to get a more focused PR, that we'll be able to describe: from what I see, the upgrade adds some very new approach like DI that would be useful to describe > > I'd like to do a release next week: we'll need to define if we can get this update in or not The support for 4.x plugins cannot really be finalised before the API is, given this target is moving. However, we need to keep up to date so that we can work on plugins more easily. I think the plugin could be trimmed down (just the actual plugin, we don't need other modules) and moved to maven-core to support v4 plugins... -- 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] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830290#comment-17830290 ] ASF GitHub Bot commented on MNG-8085: - hboutemy merged PR #1453: URL: https://github.com/apache/maven/pull/1453 > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7, 4.0.0-alpha-14 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ > and https://maven.apache.org/ref/4-LATEST/ vs previous > https://maven.apache.org/ref/4.0.0-alpha-13/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8085] switch png+imagemap to svg [maven]
hboutemy merged PR #1453: URL: https://github.com/apache/maven/pull/1453 -- 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] [Updated] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-8085: --- Fix Version/s: 4.0.0-alpha-14 > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7, 4.0.0-alpha-14 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ > and https://maven.apache.org/ref/4-LATEST/ vs previous > https://maven.apache.org/ref/4.0.0-alpha-13/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-8085: --- Description: result = https://maven.apache.org/ref/3-LATEST/ vs previous https://maven.apache.org/ref/3.9.6/ and https://maven.apache.org/ref/4-LATEST/ vs previous https://maven.apache.org/ref/4.0.0-alpha-13/ was:result = https://maven.apache.org/ref/3-LATEST/ vs previous https://maven.apache.org/ref/3.9.6/ > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ > and https://maven.apache.org/ref/4-LATEST/ vs previous > https://maven.apache.org/ref/4.0.0-alpha-13/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830285#comment-17830285 ] ASF GitHub Bot commented on MNG-8085: - hboutemy opened a new pull request, #1453: URL: https://github.com/apache/maven/pull/1453 https://issues.apache.org/jira/browse/MNG-8085 equivalent to #1452 > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830279#comment-17830279 ] ASF GitHub Bot commented on MNG-8085: - hboutemy merged PR #1452: URL: https://github.com/apache/maven/pull/1452 > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8085] switch png+imagemap to svg [maven]
hboutemy merged PR #1452: URL: https://github.com/apache/maven/pull/1452 -- 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] [Updated] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-8085: --- Description: result = https://maven.apache.org/ref/3-LATEST/ vs previous https://maven.apache.org/ref/3.9.6/ > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7 > > > result = https://maven.apache.org/ref/3-LATEST/ vs previous > https://maven.apache.org/ref/3.9.6/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8085) swtich from png+imagemap to svg
[ https://issues.apache.org/jira/browse/MNG-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830269#comment-17830269 ] ASF GitHub Bot commented on MNG-8085: - hboutemy opened a new pull request, #1452: URL: https://github.com/apache/maven/pull/1452 https://issues.apache.org/jira/browse/MNG-8085 > swtich from png+imagemap to svg > --- > > Key: MNG-8085 > URL: https://issues.apache.org/jira/browse/MNG-8085 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.9.6, 4.0.0-alpha-13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8085) swtich from png+imagemap to svg
Herve Boutemy created MNG-8085: -- Summary: swtich from png+imagemap to svg Key: MNG-8085 URL: https://issues.apache.org/jira/browse/MNG-8085 Project: Maven Issue Type: Improvement Components: Documentation: General Affects Versions: 4.0.0-alpha-13, 3.9.6 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 3.9.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-508) Upgrade to Maven 4.0.0-alpha-12
[ https://issues.apache.org/jira/browse/MPLUGIN-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830263#comment-17830263 ] ASF GitHub Bot commented on MPLUGIN-508: hboutemy commented on PR #242: URL: https://github.com/apache/maven-plugin-tools/pull/242#issuecomment-2016844928 I extracted from this huge PR updates that were not really related to Maven 4 alpha but cleanup that caused it hard to get the intent of the PR you'll need to rebase to get a more focused PR, that we'll be able to describe: from what I see, the upgrade adds some very new approach like DI that would be useful to describe I'd like to do a release next week: we'll need to define if we can get this update in or not > Upgrade to Maven 4.0.0-alpha-12 > --- > > Key: MPLUGIN-508 > URL: https://issues.apache.org/jira/browse/MPLUGIN-508 > Project: Maven Plugin Tools > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-508] Upgrade to Maven 4.0.0-alpha-13 [maven-plugin-tools]
hboutemy commented on PR #242: URL: https://github.com/apache/maven-plugin-tools/pull/242#issuecomment-2016844928 I extracted from this huge PR updates that were not really related to Maven 4 alpha but cleanup that caused it hard to get the intent of the PR you'll need to rebase to get a more focused PR, that we'll be able to describe: from what I see, the upgrade adds some very new approach like DI that would be useful to describe I'd like to do a release next week: we'll need to define if we can get this update in or not -- 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] code simplifications [maven-plugin-tools]
hboutemy merged PR #275: URL: https://github.com/apache/maven-plugin-tools/pull/275 -- 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: [I] `Could not acquire write lock for…` errors [maven-mvnd]
eliasbalasis commented on issue #836: URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-2016776247 I spoke too soon. It is still not working. ``` MAVEN_OPTS=-XX:+TieredCompilation -XX:TieredStopAtLevel=1 -Daether.syncContext.named.factory=rwlock-redisson -Daether.syncContext.named.nameMapper=static -Daether.named.diagnostic.enabled=true ... ... ... mvn -B clean install -Dmaven.logging=byproject --builder smart -T 1C ... ... ... Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) ... ... ... Java version: 17.0.10, vendor: Oracle Corporation, runtime: /usr/lib/jvm/jdk-17-oracle-x64 Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "4.18.0-513.18.0.1.el8_9.x86_64", arch: "amd64", family: "unix" ... ... ... Redisson 3.23.4 1 connections initialized for /: 24 connections initialized for /: ... ... ... Using the SmartBuilder implementation with a thread count of 12 ... ... ... Diagnostic dump of lock factory === Implementation: org.eclipse.aether.named.redisson.RedissonReadWriteLockNamedLockFactory Active locks: 1 Name: static-artifact RefCount: 7 Thread[BuilderThread 5,5,] -> [] Thread[BuilderThread 8,5,] -> [] Thread[BuilderThread 7,5,] -> [] Thread[BuilderThread 2,5,] -> [] Thread[BuilderThread 1,5,] -> [] Thread[resolver-1,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> [] Thread[BuilderThread 11,5,] -> [] Thread[resolver-3,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> [] Thread[BuilderThread 0,5,] -> [] Thread[BuilderThread 9,5,] -> [] Thread[BuilderThread 10,5,] -> [] Thread[BuilderThread 6,5,] -> [] Thread[resolver-5,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> [] Thread[BuilderThread 4,5,] -> [] Thread[resolver-2,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> [] Thread[resolver-4,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> [] Thread[BuilderThread 3,5,] -> [] Reactor Summary for : ... ... ... Could not acquire lock(s) : Could not acquire lock(s) ... ... ... To see the full stack trace of the errors, re-run Maven with the -e switch. Re-run Maven using the -X switch to enable full debug logging. Redisson 3.23.4 1 connections initialized for /: 24 connections initialized for /: ... ... ... ``` As pointed out, no error details -- 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: [I] `Could not acquire write lock for…` errors [maven-mvnd]
eliasbalasis commented on issue #836: URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-2016769249 @cstamas, I am using "aether.named.diagnostic.enabled=true" which now seems to be working after upgrading to Maven 3.9.x Also, identifying the hot artifact is easy. It is included in the build output and it is different on every build. However, this is not the problem I am trying to resolve. The problem I have been trying to resolve for a long time, is the Maven distributed locks malfunction, which didn't seem to be working before Maven 3.9.x but seems to be working now, with "static" name mapper and "redisson" named lock implementation. -- 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-1365) Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.2
[ https://issues.apache.org/jira/browse/MSHARED-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1365. Resolution: Fixed > Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.2 > > > Key: MSHARED-1365 > URL: https://issues.apache.org/jira/browse/MSHARED-1365 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1366) Bump org.apache.maven.shared:maven-shared-components from 40 to 41
[ https://issues.apache.org/jira/browse/MSHARED-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1366. Resolution: Fixed > Bump org.apache.maven.shared:maven-shared-components from 40 to 41 > -- > > Key: MSHARED-1366 > URL: https://issues.apache.org/jira/browse/MSHARED-1366 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 [maven-archiver]
slawekjaranowski merged PR #53: URL: https://github.com/apache/maven-archiver/pull/53 -- 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] (MSHARED-1366) Bump org.apache.maven.shared:maven-shared-components from 40 to 41
Slawomir Jaranowski created MSHARED-1366: Summary: Bump org.apache.maven.shared:maven-shared-components from 40 to 41 Key: MSHARED-1366 URL: https://issues.apache.org/jira/browse/MSHARED-1366 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-archiver Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-archiver-next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1365) Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2
Slawomir Jaranowski created MSHARED-1365: Summary: Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 Key: MSHARED-1365 URL: https://issues.apache.org/jira/browse/MSHARED-1365 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-archiver Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-archiver-next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1365) Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2
[ https://issues.apache.org/jira/browse/MSHARED-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830244#comment-17830244 ] ASF GitHub Bot commented on MSHARED-1365: - slawekjaranowski merged PR #55: URL: https://github.com/apache/maven-archiver/pull/55 > Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 > > > Key: MSHARED-1365 > URL: https://issues.apache.org/jira/browse/MSHARED-1365 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1365) Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.2
[ https://issues.apache.org/jira/browse/MSHARED-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MSHARED-1365: - Summary: Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.2 (was: Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2) > Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.2 > > > Key: MSHARED-1365 > URL: https://issues.apache.org/jira/browse/MSHARED-1365 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-archiver-next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSHARED-1365] Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 [maven-archiver]
slawekjaranowski merged PR #55: URL: https://github.com/apache/maven-archiver/pull/55 -- 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: [I] `Could not acquire write lock for…` errors [maven-mvnd]
cstamas commented on issue #836: URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-2016757692 At least you can do following as written here: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1706549388 You should be able to identity your "hot artifact", if you have one. -- 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] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar
[
https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MJAR-62.
---
Resolution: Fixed
> Build-Jdk in Manifest.mf does not reflect which compiler version actually
> compiled the classes in the jar
> -
>
> Key: MJAR-62
> URL: https://issues.apache.org/jira/browse/MJAR-62
> Project: Maven JAR Plugin
> Issue Type: Bug
>Reporter: Stefan Magnus Landrø
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: example-app.zip
>
>
> Manifest.mf does not reflect the version of the compiler that built the jar,
> but defaults to the version that maven runs under: Build-Jdk:
> ${java.version}.
> I believe this makes users uncertain of which compiler was actually used to
> build the classes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar
[
https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830242#comment-17830242
]
ASF GitHub Bot commented on MJAR-62:
slawekjaranowski merged PR #73:
URL: https://github.com/apache/maven-jar-plugin/pull/73
> Build-Jdk in Manifest.mf does not reflect which compiler version actually
> compiled the classes in the jar
> -
>
> Key: MJAR-62
> URL: https://issues.apache.org/jira/browse/MJAR-62
> Project: Maven JAR Plugin
> Issue Type: Bug
>Reporter: Stefan Magnus Landrø
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: example-app.zip
>
>
> Manifest.mf does not reflect the version of the compiler that built the jar,
> but defaults to the version that maven runs under: Build-Jdk:
> ${java.version}.
> I believe this makes users uncertain of which compiler was actually used to
> build the classes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJAR-62] Set Build-Jdk according to used toolchain [maven-jar-plugin]
slawekjaranowski merged PR #73: URL: https://github.com/apache/maven-jar-plugin/pull/73 -- 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] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar
[
https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830240#comment-17830240
]
ASF GitHub Bot commented on MJAR-62:
slawekjaranowski commented on code in PR #73:
URL: https://github.com/apache/maven-jar-plugin/pull/73#discussion_r1536778031
##
src/main/java/org/apache/maven/plugins/jar/ToolchainsJdkSpecification.java:
##
@@ -0,0 +1,99 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.maven.plugins.jar;
+
+import javax.inject.Named;
+import javax.inject.Singleton;
+
+import java.io.IOException;
+import java.io.UncheckedIOException;
+import java.nio.file.Path;
+import java.nio.file.Paths;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.Optional;
+
+import org.apache.maven.toolchain.Toolchain;
+import org.codehaus.plexus.util.cli.CommandLineException;
+import org.codehaus.plexus.util.cli.CommandLineUtils;
+import org.codehaus.plexus.util.cli.Commandline;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+/**
+ * Component provided JDK specification based on toolchains.
+ */
+@Named
+@Singleton
+class ToolchainsJdkSpecification {
+
+private final Logger logger =
LoggerFactory.getLogger(ToolchainsJdkSpecification.class);
+
+private final Map cache = new HashMap<>();
+
+public synchronized Optional getJDKSpecification(Toolchain
toolchain) {
+Optional javacPath = getJavacPath(toolchain);
+return javacPath.map(path -> cache.computeIfAbsent(path,
this::getSpecForPath));
+}
+
+private Optional getJavacPath(Toolchain toolchain) {
+return
Optional.ofNullable(toolchain.findTool("javac")).map(Paths::get).map(this::getCanonicalPath);
+}
+
+private Path getCanonicalPath(Path path) {
+try {
+return path.toRealPath();
+} catch (IOException e) {
+if (path.getParent() != null) {
+return
getCanonicalPath(path.getParent()).resolve(path.getFileName());
+} else {
+throw new UncheckedIOException(e);
+}
+}
+}
+
+private String getSpecForPath(Path path) {
+try {
+Commandline cl = new Commandline(path.toString());
+cl.createArg().setValue("-version");
+CommandLineUtils.StringStreamConsumer out = new
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.StringStreamConsumer err = new
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.executeCommandLine(cl, out, err);
+String version = out.getOutput().trim();
+if (version.isEmpty()) {
+version = err.getOutput().trim();
+}
+if (version.startsWith("javac ")) {
+version = version.substring(6);
+if (version.startsWith("1.")) {
+version = version.substring(0, 3);
+} else {
+version = version.substring(0, 2);
+}
+return version;
+} else {
+logger.warn("Unrecognized output form " + path + " -version -
" + version);
+return null;
+}
+} catch (CommandLineException e) {
Review Comment:
done
> Build-Jdk in Manifest.mf does not reflect which compiler version actually
> compiled the classes in the jar
> -
>
> Key: MJAR-62
> URL: https://issues.apache.org/jira/browse/MJAR-62
> Project: Maven JAR Plugin
> Issue Type: Bug
>Reporter: Stefan Magnus Landrø
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: example-app.zip
>
>
> Manifest.mf does not reflect the version of the compiler that built the jar,
> but defaults to the version that maven runs under: Build-Jdk:
> ${java.version}.
> I believe this makes users uncertain of which compiler was actually used to
> build the classes.
--
This message was sent by
Re: [PR] [MJAR-62] Set Build-Jdk according to used toolchain [maven-jar-plugin]
slawekjaranowski commented on code in PR #73:
URL: https://github.com/apache/maven-jar-plugin/pull/73#discussion_r1536778031
##
src/main/java/org/apache/maven/plugins/jar/ToolchainsJdkSpecification.java:
##
@@ -0,0 +1,99 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.maven.plugins.jar;
+
+import javax.inject.Named;
+import javax.inject.Singleton;
+
+import java.io.IOException;
+import java.io.UncheckedIOException;
+import java.nio.file.Path;
+import java.nio.file.Paths;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.Optional;
+
+import org.apache.maven.toolchain.Toolchain;
+import org.codehaus.plexus.util.cli.CommandLineException;
+import org.codehaus.plexus.util.cli.CommandLineUtils;
+import org.codehaus.plexus.util.cli.Commandline;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+/**
+ * Component provided JDK specification based on toolchains.
+ */
+@Named
+@Singleton
+class ToolchainsJdkSpecification {
+
+private final Logger logger =
LoggerFactory.getLogger(ToolchainsJdkSpecification.class);
+
+private final Map cache = new HashMap<>();
+
+public synchronized Optional getJDKSpecification(Toolchain
toolchain) {
+Optional javacPath = getJavacPath(toolchain);
+return javacPath.map(path -> cache.computeIfAbsent(path,
this::getSpecForPath));
+}
+
+private Optional getJavacPath(Toolchain toolchain) {
+return
Optional.ofNullable(toolchain.findTool("javac")).map(Paths::get).map(this::getCanonicalPath);
+}
+
+private Path getCanonicalPath(Path path) {
+try {
+return path.toRealPath();
+} catch (IOException e) {
+if (path.getParent() != null) {
+return
getCanonicalPath(path.getParent()).resolve(path.getFileName());
+} else {
+throw new UncheckedIOException(e);
+}
+}
+}
+
+private String getSpecForPath(Path path) {
+try {
+Commandline cl = new Commandline(path.toString());
+cl.createArg().setValue("-version");
+CommandLineUtils.StringStreamConsumer out = new
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.StringStreamConsumer err = new
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.executeCommandLine(cl, out, err);
+String version = out.getOutput().trim();
+if (version.isEmpty()) {
+version = err.getOutput().trim();
+}
+if (version.startsWith("javac ")) {
+version = version.substring(6);
+if (version.startsWith("1.")) {
+version = version.substring(0, 3);
+} else {
+version = version.substring(0, 2);
+}
+return version;
+} else {
+logger.warn("Unrecognized output form " + path + " -version -
" + version);
+return null;
+}
+} catch (CommandLineException e) {
Review Comment:
done
--
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: [I] `Could not acquire write lock for…` errors [maven-mvnd]
eliasbalasis commented on issue #836: URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-2016751783 @cstamas, I cannot share the build output because it contains references to private components. Specifically for "redisson" named lock implementation, trust me when I say that the build output did not reveal much except detailed list of the active locks. It contains only the list of locks at the time of failure and no stack trace or any detailed analysis of the errors. Therefore it is pointless for me trying to cleanup the build output by removing the references to private references. I observed this repeatedly using "gav" , "discriminating" name mappers. (see https://maven.apache.org/resolver/maven-resolver-named-locks/index.html) However, the "static" name mapper seems to be the only one working without producing any locking errors. This is great progress from where I stand. I am now trying to experiment with "hazelcast" named lock implementation and I intend to share the outcome. -- 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] Apply ASF Infra GitHub Actions Policy [maven-gh-actions-shared]
slawekjaranowski merged PR #98: URL: https://github.com/apache/maven-gh-actions-shared/pull/98 -- 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] (MNG-8082) Exceptions of proxied SessionScoped components are not working correctly
[
https://issues.apache.org/jira/browse/MNG-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830213#comment-17830213
]
ASF GitHub Bot commented on MNG-8082:
-
CrazyHZM commented on code in PR #1449:
URL: https://github.com/apache/maven/pull/1449#discussion_r1536759020
##
maven-core/src/main/java/org/apache/maven/session/scope/internal/SessionScope.java:
##
@@ -107,7 +107,11 @@ public Provider scope(final Key key, final
Provider unscoped) {
private T createProxy(Key key, Provider unscoped) {
InvocationHandler dispatcher = (proxy, method, args) -> {
method.setAccessible(true);
-return method.invoke(getScopeState().scope(key, unscoped).get(),
args);
+try {
+return method.invoke(getScopeState().scope(key,
unscoped).get(), args);
+} catch (InvocationTargetException e) {
+throw e.getCause();
Review Comment:
If the target Exception is null, it will throw NPE, and this could affect
exception tracing.
> Exceptions of proxied SessionScoped components are not working correctly
>
>
> Key: MNG-8082
> URL: https://issues.apache.org/jira/browse/MNG-8082
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-13
>Reporter: Jonas Rutishauser
>Priority: Major
>
> As the {{InvocationTargetException}} is not handled in the proxy a runtime
> exception will be wrapped by an {{InvocationTargetException}} and an
> application exception is additional wrapped by an
> {{UndeclaredThrowableException}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8082] - Exceptions of proxied SessionScoped components are not working correctly [maven]
CrazyHZM commented on code in PR #1449:
URL: https://github.com/apache/maven/pull/1449#discussion_r1536759020
##
maven-core/src/main/java/org/apache/maven/session/scope/internal/SessionScope.java:
##
@@ -107,7 +107,11 @@ public Provider scope(final Key key, final
Provider unscoped) {
private T createProxy(Key key, Provider unscoped) {
InvocationHandler dispatcher = (proxy, method, args) -> {
method.setAccessible(true);
-return method.invoke(getScopeState().scope(key, unscoped).get(),
args);
+try {
+return method.invoke(getScopeState().scope(key,
unscoped).get(), args);
+} catch (InvocationTargetException e) {
+throw e.getCause();
Review Comment:
If the target Exception is null, it will throw NPE, and this could affect
exception tracing.
--
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] (MPLUGIN-510) update plugin system requirements history structure
[ https://issues.apache.org/jira/browse/MPLUGIN-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830209#comment-17830209 ] ASF GitHub Bot commented on MPLUGIN-510: hboutemy merged PR #274: URL: https://github.com/apache/maven-plugin-tools/pull/274 > update plugin system requirements history structure > --- > > Key: MPLUGIN-510 > URL: https://issues.apache.org/jira/browse/MPLUGIN-510 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: Plugin Reporting Plugin >Affects Versions: 3.11.0 >Reporter: Herve Boutemy >Priority: Major > Fix For: 3.12.0 > > > in MPLUGIN-400, we added the feature with a list of versions of the plugin, > associated to Maven and JDK prerequisite > https://maven.apache.org/plugin-tools-archives/plugin-tools-3.7.0/maven-plugin-report-plugin/report-mojo.html#requirementshistories > => started to use for example: > [https://maven.apache.org/plugins-archives/maven-assembly-plugin-3.6.0/plugin-info.html] > this lead to questions: should we fill each and every past version? Or should > we group by common prerequisites, showing only ranges? > Tested the range approach: > [https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/plugin-info.html] > the range approach looks good: minimum lines (vs listing every version), > clear choice for users (choose the latest in the range, or pick any > intermediate one) > now, we need to rework the m-p-p configuration to replace "version" with > "from" + "to", instead of hijacking the "version" field to store a String > "from x to y" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPLUGIN-510) update plugin system requirements history structure
[ https://issues.apache.org/jira/browse/MPLUGIN-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-510. - Assignee: Herve Boutemy Resolution: Fixed > update plugin system requirements history structure > --- > > Key: MPLUGIN-510 > URL: https://issues.apache.org/jira/browse/MPLUGIN-510 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: Plugin Reporting Plugin >Affects Versions: 3.11.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.12.0 > > > in MPLUGIN-400, we added the feature with a list of versions of the plugin, > associated to Maven and JDK prerequisite > https://maven.apache.org/plugin-tools-archives/plugin-tools-3.7.0/maven-plugin-report-plugin/report-mojo.html#requirementshistories > => started to use for example: > [https://maven.apache.org/plugins-archives/maven-assembly-plugin-3.6.0/plugin-info.html] > this lead to questions: should we fill each and every past version? Or should > we group by common prerequisites, showing only ranges? > Tested the range approach: > [https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/plugin-info.html] > the range approach looks good: minimum lines (vs listing every version), > clear choice for users (choose the latest in the range, or pick any > intermediate one) > now, we need to rework the m-p-p configuration to replace "version" with > "from" + "to", instead of hijacking the "version" field to store a String > "from x to y" -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-510] group history per common requirements [maven-plugin-tools]
hboutemy merged PR #274: URL: https://github.com/apache/maven-plugin-tools/pull/274 -- 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
