[jira] [Commented] (MSHARED-1425) PMD is too chatty: [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
[
https://issues.apache.org/jira/browse/MSHARED-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875373#comment-17875373
]
Michael Osipov commented on MSHARED-1425:
-
There are two cases regarding the entire line:
1. Standalone execution is per goal. So entire goals are ten lines.
2. Site execution prints once for all sets of reporting goals.
> PMD is too chatty: [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
>
>
> Key: MSHARED-1425
> URL: https://issues.apache.org/jira/browse/MSHARED-1425
> Project: Maven Shared Components
> Issue Type: Wish
> Components: maven-reporting-impl
>Reporter: Gary D. Gregory
>Priority: Minor
>
> PMD is too chatty, it should not log skin logic at the INFO level. I propose
> to log this at the DEBUG or TRACE level:
> {noformat}
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSHARED-1425) PMD is too chatty: [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
[
https://issues.apache.org/jira/browse/MSHARED-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875373#comment-17875373
]
Michael Osipov edited comment on MSHARED-1425 at 8/21/24 7:14 AM:
--
There are two cases regarding the entire line:
1. Standalone execution is per goal. So 10 goals are ten lines.
2. Site execution prints once for all sets of reporting goals.
was (Author: michael-o):
There are two cases regarding the entire line:
1. Standalone execution is per goal. So entire goals are ten lines.
2. Site execution prints once for all sets of reporting goals.
> PMD is too chatty: [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
>
>
> Key: MSHARED-1425
> URL: https://issues.apache.org/jira/browse/MSHARED-1425
> Project: Maven Shared Components
> Issue Type: Wish
> Components: maven-reporting-impl
>Reporter: Gary D. Gregory
>Priority: Minor
>
> PMD is too chatty, it should not log skin logic at the INFO level. I propose
> to log this at the DEBUG or TRACE level:
> {noformat}
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump plexusVersion from 2.1.0 to 2.2.0 [maven]
dependabot[bot] opened a new pull request, #1666: URL: https://github.com/apache/maven/pull/1666 Bumps `plexusVersion` from 2.1.0 to 2.2.0. Updates `org.codehaus.plexus:plexus-component-annotations` from 2.1.0 to 2.2.0 Release notes Sourced from https://github.com/codehaus-plexus/plexus-containers/releases";>org.codehaus.plexus:plexus-component-annotations's releases. 2.2.0 improve documentation to switch to Sisu (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/121";>#121) https://github.com/hboutemy";>@hboutemy pom clean after parent upgrade (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/120";>#120) https://github.com/hboutemy";>@hboutemy Improve plexus-component metadata - remove dependency to plexus-container-default (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/109";>#109) https://github.com/slachiewicz";>@slachiewicz Add deprecation information to Plexus components (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/108";>#108) https://github.com/slachiewicz";>@slachiewicz Require Java 8 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/107";>#107) https://github.com/slachiewicz";>@slachiewicz Drop plexus-container-default artefact (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/135";>#135) https://github.com/slachiewicz";>@slachiewicz Require Maven 3.6.3+ (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/133";>#133) https://github.com/slachiewicz";>@slachiewicz Switch to JUnit5 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/134";>#134) https://github.com/slachiewicz";>@slachiewicz Bump org.eclipse.sisu.plexus from 0.3.0.M1 to 0.9.0.M2 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/113";>#113) https://github.com/dependabot";>@dependabot 📦 Dependency updates Bump org.codehaus.plexus:plexus-testing from 1.2.0 to 1.3.0 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/139";>#139) https://github.com/dependabot";>@dependabot Bump org.codehaus.plexus:plexus from 15 to 16 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/138";>#138) https://github.com/dependabot";>@dependabot Bump org.apache.xbean:xbean-reflect from 4.23 to 4.24 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/131";>#131) https://github.com/dependabot";>@dependabot Reorg dependencyManagement to subprojects. Prepare to drop plexus-container-default (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/132";>#132) https://github.com/slachiewicz";>@slachiewicz Bump org.ow2.asm:asm from 9.5 to 9.6 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/129";>#129) https://github.com/dependabot";>@dependabot Bump maven-invoker-plugin from 3.5.1 to 3.6.0 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/125";>#125) https://github.com/dependabot";>@dependabot Bump xbean-reflect from 4.22 to 4.23 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/116";>#116) https://github.com/dependabot";>@dependabot Bump maven-plugin-annotations from 3.8.1 to 3.8.2 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/104";>#104) https://github.com/dependabot";>@dependabot Bump maven-plugin-plugin from 3.8.1 to 3.8.2 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/105";>#105) https://github.com/dependabot";>@dependabot Bump maven-project-info-reports-plugin from 3.4.2 to 3.4.3 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/102";>#102) https://github.com/dependabot";>@dependabot Bump asm from 9.4 to 9.5 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/99";>#99) https://github.com/dependabot";>@dependabot Bump plexus-utils from 3.5.0 to 3.5.1 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/97";>#97) https://github.com/dependabot";>@dependabot Bump checkstyle from 9.2 to 9.3 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/96";>#96) https://github.com/dependabot";>@dependabot Bump maven-plugin-plugin from 3.7.1 to 3.8.1 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/92";>#92) https://github.com/dependabot";>@dependabot Bump maven-plugin-annotations from 3.7.1 to 3.8.1 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/93";>#93) https://github.com/dependabot";>@dependabot Bump asm from 9.3 to 9.4 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/88";>#88) https://github.com/dependabot";>@dependabot Bump maven-project-info-reports-plugin from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-containers/pull/85";>#85) https://github.com/dependabot";>@dependabot Bump maven-plugin-plugin from 3.7.0 to 3.7.1 (https://redirect
[PR] Bump org.mockito:mockito-core from 4.11.0 to 5.12.0 [maven]
dependabot[bot] opened a new pull request, #1667: URL: https://github.com/apache/maven/pull/1667 Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 4.11.0 to 5.12.0. Release notes Sourced from https://github.com/mockito/mockito/releases";>org.mockito:mockito-core's releases. v5.12.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 5.12.0 2024-05-11 - https://github.com/mockito/mockito/compare/v5.11.0...v5.12.0";>25 commit(s) by Piotr Przybylak, Stefano Cordio, Tim van der Lippe, dependabot[bot], jonghoonpark Bump com.gradle.enterprise from 3.17.2 to 3.17.3 [(https://redirect.github.com/mockito/mockito/issues/3341";>#3341)](https://redirect.github.com/mockito/mockito/pull/3341";>mockito/mockito#3341) Bump org.jetbrains.kotlin:kotlin-stdlib from 1.9.23 to 1.9.24 [(https://redirect.github.com/mockito/mockito/issues/3339";>#3339)](https://redirect.github.com/mockito/mockito/pull/3339";>mockito/mockito#3339) Bump versions.bytebuddy from 1.14.14 to 1.14.15 [(https://redirect.github.com/mockito/mockito/issues/3338";>#3338)](https://redirect.github.com/mockito/mockito/pull/3338";>mockito/mockito#3338) Bump org.shipkit:shipkit-auto-version from 2.0.6 to 2.0.7 [(https://redirect.github.com/mockito/mockito/issues/3337";>#3337)](https://redirect.github.com/mockito/mockito/pull/3337";>mockito/mockito#3337) Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 1.9.23 to 1.9.24 [(https://redirect.github.com/mockito/mockito/issues/3336";>#3336)](https://redirect.github.com/mockito/mockito/pull/3336";>mockito/mockito#3336) Fixes https://redirect.github.com/mockito/mockito/issues/3331";>#3331 : Fix AdditionalMatchers.and() and AdditionalMatchers.or() not to swap the order of matchers [(https://redirect.github.com/mockito/mockito/issues/3335";>#3335)](https://redirect.github.com/mockito/mockito/pull/3335";>mockito/mockito#3335) AdditionalMatchers.and() and or() swap matcher order [(https://redirect.github.com/mockito/mockito/issues/3331";>#3331)](https://redirect.github.com/mockito/mockito/issues/3331";>mockito/mockito#3331) Bump gradle/wrapper-validation-action from 3.3.1 to 3.3.2 [(https://redirect.github.com/mockito/mockito/issues/3327";>#3327)](https://redirect.github.com/mockito/mockito/pull/3327";>mockito/mockito#3327) Bump versions.bytebuddy from 1.14.13 to 1.14.14 [(https://redirect.github.com/mockito/mockito/issues/3324";>#3324)](https://redirect.github.com/mockito/mockito/pull/3324";>mockito/mockito#3324) Bump org.shipkit:shipkit-auto-version from 2.0.5 to 2.0.6 [(https://redirect.github.com/mockito/mockito/issues/3322";>#3322)](https://redirect.github.com/mockito/mockito/pull/3322";>mockito/mockito#3322) Bump gradle/wrapper-validation-action from 3.3.0 to 3.3.1 [(https://redirect.github.com/mockito/mockito/issues/3320";>#3320)](https://redirect.github.com/mockito/mockito/pull/3320";>mockito/mockito#3320) Bump com.gradle.enterprise from 3.17 to 3.17.2 [(https://redirect.github.com/mockito/mockito/issues/3318";>#3318)](https://redirect.github.com/mockito/mockito/pull/3318";>mockito/mockito#3318) Bump gradle/wrapper-validation-action from 2.1.2 to 3.3.0 [(https://redirect.github.com/mockito/mockito/issues/3317";>#3317)](https://redirect.github.com/mockito/mockito/pull/3317";>mockito/mockito#3317) Update codecov-action version [(https://redirect.github.com/mockito/mockito/issues/3316";>#3316)](https://redirect.github.com/mockito/mockito/pull/3316";>mockito/mockito#3316) Bump com.google.googlejavaformat:google-java-format from 1.21.0 to 1.22.0 [(https://redirect.github.com/mockito/mockito/issues/3312";>#3312)](https://redirect.github.com/mockito/mockito/pull/3312";>mockito/mockito#3312) Bump com.gradle.enterprise from 3.16.2 to 3.17 [(https://redirect.github.com/mockito/mockito/issues/3311";>#3311)](https://redirect.github.com/mockito/mockito/pull/3311";>mockito/mockito#3311) Bump versions.bytebuddy from 1.14.12 to 1.14.13 [(https://redirect.github.com/mockito/mockito/issues/3308";>#3308)](https://redirect.github.com/mockito/mockito/pull/3308";>mockito/mockito#3308) Fix README logo [(https://redirect.github.com/mockito/mockito/issues/3305";>#3305)](https://redirect.github.com/mockito/mockito/pull/3305";>mockito/mockito#3305) Bump gradle/wrapper-validation-action from 2.1.1 to 2.1.2 [(https://redirect.github.com/mockito/mockito/issues/3303";>#3303)](https://redirect.github.com/mockito/mockito/pull/3303";>mockito/mockito#3303) Bump org.shipkit:shipkit-auto-version from 2.0.4 to 2.0.5 [(https://redirect.github.com/mockito/mockito/issues/3298";>#3298)](https://redirect.github.com/mockito/mockito/pull/3298";>mockito/mockito#3298) Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 1.9.22 to 1.9.23 [(https://redirect.github.com/mockito/mockito/issues/3296";>#3296)](https://redirect.github.com/mockito/mockito/pull/3296";>mockito/mockito#3296)
[PR] Bump commons-cli:commons-cli from 1.8.0 to 1.9.0 [maven]
dependabot[bot] opened a new pull request, #1665: URL: https://github.com/apache/maven/pull/1665 Bumps commons-cli:commons-cli from 1.8.0 to 1.9.0. [](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 slf4jVersion from 1.7.36 to 2.0.16 [maven]
dependabot[bot] opened a new pull request, #1668: URL: https://github.com/apache/maven/pull/1668 Bumps `slf4jVersion` from 1.7.36 to 2.0.16. Updates `org.slf4j:slf4j-api` from 1.7.36 to 2.0.16 Updates `org.slf4j:slf4j-simple` from 1.7.36 to 2.0.16 Updates `org.slf4j:jcl-over-slf4j` from 1.7.36 to 2.0.16 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 com.google.inject:guice from 5.1.0 to 7.0.0 [maven]
dependabot[bot] opened a new pull request, #1669:
URL: https://github.com/apache/maven/pull/1669
Bumps [com.google.inject:guice](https://github.com/google/guice) from 5.1.0
to 7.0.0.
Release notes
Sourced from https://github.com/google/guice/releases";>com.google.inject:guice's
releases.
Guice 7.0.0
See https://github.com/google/guice/wiki/Guice700";>https://github.com/google/guice/wiki/Guice700
for release notes.
Guice 7.0.0-rc1
See https://github.com/google/guice/wiki/Guice700";>https://github.com/google/guice/wiki/Guice700
for release notes.
Guice 6.0.0
See https://github.com/google/guice/wiki/Guice600";>https://github.com/google/guice/wiki/Guice600
for release notes.
Guice 6.0.0-rc2
See https://github.com/google/guice/wiki/Guice600";>https://github.com/google/guice/wiki/Guice600
for release notes.
Commits
https://github.com/google/guice/commit/b0e1d0fab0167cd555ab8d262333c1a32db7d492";>b0e1d0f
set 7.0.0 release #s.
https://github.com/google/guice/commit/f4a66b797ecc05d80406d6c8fb11e6cc0e5c6d21";>f4a66b7
Make error_prone_annotations dependency optional
https://github.com/google/guice/commit/654032a954d55a00fc5ee90da815da98cb6676a1";>654032a
Internal change.
https://github.com/google/guice/commit/bee813b7cc15e46695ca1baf5041a00e0a612f91";>bee813b
Improve MissingImplementationError to lazily calculate suggestions and
standa...
https://github.com/google/guice/commit/2d64067e99401e50404c6e05a819bce891b725de";>2d64067
Use linked bindings for MapBinder/Multibinder/OptionalBinder aliases,
instead...
https://github.com/google/guice/commit/be0141cc0d01763a13ec0b2fcd32ddbe0748ad6d";>be0141c
Internal change
https://github.com/google/guice/commit/40a5bcfab5cfe45c3b6c5ffc9309b310df82775b";>40a5bcf
Avoid re-initializing factories that are already initialized. This is
necessa...
https://github.com/google/guice/commit/9ac476784e88f4481f8211dcb19ac536f5f2b32d";>9ac4767
Change the way we reference what 6.0 supports in the README, so it doesn't
ge...
https://github.com/google/guice/commit/24324ca6c61f64872376ed7f4ed22a3f1f0724f1";>24324ca
Prepare for the Guice 6.0 & 7.0 releases. This change does the
following:
https://github.com/google/guice/commit/49b1a33c594fd92ad0d1d013fa91d689e8814a6c";>49b1a33
Remove redundant references to javax.{inject,persistence,servlet} and
replace...
Additional commits viewable in https://github.com/google/guice/compare/5.1.0...7.0.0";>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
[PR] Bump slf4jVersion from 1.7.36 to 2.0.16 [maven-resolver]
dependabot[bot] opened a new pull request, #563: URL: https://github.com/apache/maven-resolver/pull/563 Bumps `slf4jVersion` from 1.7.36 to 2.0.16. Updates `org.slf4j:slf4j-api` from 1.7.36 to 2.0.16 Updates `org.slf4j:slf4j-simple` from 1.7.36 to 2.0.16 Updates `org.slf4j:jcl-over-slf4j` from 1.7.36 to 2.0.16 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
Re: [PR] Bump slf4jVersion from 1.7.36 to 2.0.16 [maven-resolver]
dependabot[bot] commented on PR #563: URL: https://github.com/apache/maven-resolver/pull/563#issuecomment-2301558473 The following labels could not be found: `resolver1`. -- 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 com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]
dependabot[bot] opened a new pull request, #564:
URL: https://github.com/apache/maven-resolver/pull/564
Bumps [com.google.inject:guice](https://github.com/google/guice) from 6.0.0
to 7.0.0.
Release notes
Sourced from https://github.com/google/guice/releases";>com.google.inject:guice's
releases.
Guice 7.0.0
See https://github.com/google/guice/wiki/Guice700";>https://github.com/google/guice/wiki/Guice700
for release notes.
Guice 7.0.0-rc1
See https://github.com/google/guice/wiki/Guice700";>https://github.com/google/guice/wiki/Guice700
for release notes.
Commits
https://github.com/google/guice/commit/b0e1d0fab0167cd555ab8d262333c1a32db7d492";>b0e1d0f
set 7.0.0 release #s.
https://github.com/google/guice/commit/f4a66b797ecc05d80406d6c8fb11e6cc0e5c6d21";>f4a66b7
Make error_prone_annotations dependency optional
https://github.com/google/guice/commit/654032a954d55a00fc5ee90da815da98cb6676a1";>654032a
Internal change.
https://github.com/google/guice/commit/bee813b7cc15e46695ca1baf5041a00e0a612f91";>bee813b
Improve MissingImplementationError to lazily calculate suggestions and
standa...
https://github.com/google/guice/commit/2d64067e99401e50404c6e05a819bce891b725de";>2d64067
Use linked bindings for MapBinder/Multibinder/OptionalBinder aliases,
instead...
https://github.com/google/guice/commit/be0141cc0d01763a13ec0b2fcd32ddbe0748ad6d";>be0141c
Internal change
https://github.com/google/guice/commit/40a5bcfab5cfe45c3b6c5ffc9309b310df82775b";>40a5bcf
Avoid re-initializing factories that are already initialized. This is
necessa...
https://github.com/google/guice/commit/9ac476784e88f4481f8211dcb19ac536f5f2b32d";>9ac4767
Change the way we reference what 6.0 supports in the README, so it doesn't
ge...
https://github.com/google/guice/commit/24324ca6c61f64872376ed7f4ed22a3f1f0724f1";>24324ca
Prepare for the Guice 6.0 & 7.0 releases. This change does the
following:
https://github.com/google/guice/commit/49b1a33c594fd92ad0d1d013fa91d689e8814a6c";>49b1a33
Remove redundant references to javax.{inject,persistence,servlet} and
replace...
See full diff in https://github.com/google/guice/compare/6.0.0...7.0.0";>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
[PR] Bump jettyVersion from 9.4.54.v20240208 to 12.0.12 [maven-resolver]
dependabot[bot] opened a new pull request, #565: URL: https://github.com/apache/maven-resolver/pull/565 Bumps `jettyVersion` from 9.4.54.v20240208 to 12.0.12. Updates `org.eclipse.jetty:jetty-server` from 9.4.54.v20240208 to 12.0.12 Updates `org.eclipse.jetty:jetty-util` from 9.4.54.v20240208 to 12.0.12 Updates `org.eclipse.jetty:jetty-http` from 9.4.54.v20240208 to 12.0.12 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
Re: [PR] Bump jettyVersion from 9.4.54.v20240208 to 12.0.12 [maven-resolver]
dependabot[bot] commented on PR #565: URL: https://github.com/apache/maven-resolver/pull/565#issuecomment-2301558783 The following labels could not be found: `resolver1`. -- 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] [MRESOLVER-588] Add env-variables as sys-props in Maven-4 SessionBuilderSupplier [maven-resolver]
HannesWell commented on PR #539: URL: https://github.com/apache/maven-resolver/pull/539#issuecomment-2301559183 > * the goal of supplier is to provide "baseline" only, and nothing in Resolver uses ENV variables I understand that. But the problem can be and that's why I encountered this at all, is that some artifacts cannot be resolved some system properties are missing. For example without any system-properties, org.apache.commons:commons-text:1.12.0 fails to resolve with a `ModelBuildingException` saying something like `[ERROR] Failed to determine Java version for profile`. In this case the `java.version` property is missing and e.g. the `animal-sniffer` profile from the `commons-parent` cannot determine if the activation element `(,9)` is met or not. And since properties and env-properties can also be used to activate profiles in general and profiles can contain additional dependencies, not having them can influence the resolution result. A general property activation will probably not fail the resolution if a property is missing (I haven't tested it), but the result would still be different than in a default maven installation. So the resolver could implicitly use env variablies. But I cannot tell if the latter already is already out of the scope of the baseline? -- 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 sisuVersion from 0.9.0.M2 to 0.9.0.M3 [maven-resolver]
dependabot[bot] opened a new pull request, #566: URL: https://github.com/apache/maven-resolver/pull/566 Bumps `sisuVersion` from 0.9.0.M2 to 0.9.0.M3. Updates `org.eclipse.sisu:org.eclipse.sisu.inject` from 0.9.0.M2 to 0.9.0.M3 Release notes Sourced from https://github.com/eclipse/sisu.inject/releases";>org.eclipse.sisu:org.eclipse.sisu.inject's releases. 0.9.0.M3 What's Changed Annotate new method by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/90";>eclipse-sisu/sisu-project#90 Update workflow to run on Java 21 by https://github.com/mcculls";>@mcculls in https://redirect.github.com/eclipse-sisu/sisu-project/pull/96";>eclipse-sisu/sisu-project#96 ASM 9.6 by https://github.com/mcculls";>@mcculls in https://redirect.github.com/eclipse-sisu/sisu-project/pull/95";>eclipse-sisu/sisu-project#95 Build with final Java 21 on GitHub by https://github.com/kwin";>@kwin in https://redirect.github.com/eclipse-sisu/sisu-project/pull/99";>eclipse-sisu/sisu-project#99 Switch to JUnit5 by https://github.com/kwin";>@kwin in https://redirect.github.com/eclipse-sisu/sisu-project/pull/101";>eclipse-sisu/sisu-project#101 Disable annotation processor by default by https://github.com/kwin";>@kwin in https://redirect.github.com/eclipse-sisu/sisu-project/pull/105";>eclipse-sisu/sisu-project#105 Do not silently fail in case of class scanning exceptions by https://github.com/kwin";>@kwin in https://redirect.github.com/eclipse-sisu/sisu-project/pull/98";>eclipse-sisu/sisu-project#98 Formatting issues by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/109";>eclipse-sisu/sisu-project#109 Update maven wrapper and maven (3.9.6) by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/112";>eclipse-sisu/sisu-project#112 Update Maven Plugins by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/111";>eclipse-sisu/sisu-project#111 Address dependabot alerts by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/128";>eclipse-sisu/sisu-project#128 (deps): Update to ASM 9.7 by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/131";>eclipse-sisu/sisu-project#131 Update CONTRIBUTING.md by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/110";>eclipse-sisu/sisu-project#110 Align Plexus ASM version by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/134";>eclipse-sisu/sisu-project#134 Rename release profile by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/133";>eclipse-sisu/sisu-project#133 Fix Jacoco coverage repots in Sonar by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/136";>eclipse-sisu/sisu-project#136 Add a method to allow LifecycleManager to free keys by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/138";>eclipse-sisu/sisu-project#138 Licence change: From EPL1 to EPL2 by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/135";>eclipse-sisu/sisu-project#135 update documentation for exposed core extensions, fix anchors by https://github.com/HomeOfTheWizard";>@HomeOfTheWizard in https://redirect.github.com/eclipse-sisu/sisu-project/pull/139";>eclipse-sisu/sisu-project#139 Prepare for release by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/141";>eclipse-sisu/sisu-project#141 Trigger Sonarcloud analysis from GHA by https://github.com/kwin";>@kwin in https://redirect.github.com/eclipse-sisu/sisu-project/pull/143";>eclipse-sisu/sisu-project#143 Fix for release process: by https://github.com/cstamas";>@cstamas in https://redirect.github.com/eclipse-sisu/sisu-project/pull/144";>eclipse-sisu/sisu-project#144 New Contributors https://github.com/HomeOfTheWizard";>@HomeOfTheWizard made their first contribution in https://redirect.github.com/eclipse-sisu/sisu-project/pull/139";>eclipse-sisu/sisu-project#139 Full Changelog: https://github.com/eclipse-sisu/sisu-project/compare/milestones/0.9.0.M2...milestones/0.9.0.M3";>https://github.com/eclipse-sisu/sisu-project/compare/milestones/0.9.0.M2...milestones/0.9.0.M3 Commits https://github.com/eclipse-sisu/sisu-project/commit/cd41943d6e0d0953144f1d1121d0c18e58c3eb95";>cd41943 | prepare release milestones/0.9.0.M3 https://github.com/eclipse-sisu/sisu-project/commit/dc2c7366202033626cd3a6ef31d50e30f1ab3103";>dc2c736 Fix for release process: (https://redirect.github.com/eclipse/sisu.injec
Re: [PR] Bump org.mockito:mockito-core from 4.11.0 to 5.12.0 [maven-resolver]
dependabot[bot] commented on PR #567: URL: https://github.com/apache/maven-resolver/pull/567#issuecomment-2301559504 The following labels could not be found: `resolver1`. -- 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 com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]
dependabot[bot] commented on PR #564: URL: https://github.com/apache/maven-resolver/pull/564#issuecomment-2301558596 The following labels could not be found: `resolver1`. -- 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 sisuVersion from 0.9.0.M2 to 0.9.0.M3 [maven-resolver]
dependabot[bot] commented on PR #566: URL: https://github.com/apache/maven-resolver/pull/566#issuecomment-2301559325 The following labels could not be found: `resolver1`. -- 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-core from 4.11.0 to 5.12.0 [maven-resolver]
dependabot[bot] opened a new pull request, #567: URL: https://github.com/apache/maven-resolver/pull/567 Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 4.11.0 to 5.12.0. Release notes Sourced from https://github.com/mockito/mockito/releases";>org.mockito:mockito-core's releases. v5.12.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 5.12.0 2024-05-11 - https://github.com/mockito/mockito/compare/v5.11.0...v5.12.0";>25 commit(s) by Piotr Przybylak, Stefano Cordio, Tim van der Lippe, dependabot[bot], jonghoonpark Bump com.gradle.enterprise from 3.17.2 to 3.17.3 [(https://redirect.github.com/mockito/mockito/issues/3341";>#3341)](https://redirect.github.com/mockito/mockito/pull/3341";>mockito/mockito#3341) Bump org.jetbrains.kotlin:kotlin-stdlib from 1.9.23 to 1.9.24 [(https://redirect.github.com/mockito/mockito/issues/3339";>#3339)](https://redirect.github.com/mockito/mockito/pull/3339";>mockito/mockito#3339) Bump versions.bytebuddy from 1.14.14 to 1.14.15 [(https://redirect.github.com/mockito/mockito/issues/3338";>#3338)](https://redirect.github.com/mockito/mockito/pull/3338";>mockito/mockito#3338) Bump org.shipkit:shipkit-auto-version from 2.0.6 to 2.0.7 [(https://redirect.github.com/mockito/mockito/issues/3337";>#3337)](https://redirect.github.com/mockito/mockito/pull/3337";>mockito/mockito#3337) Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 1.9.23 to 1.9.24 [(https://redirect.github.com/mockito/mockito/issues/3336";>#3336)](https://redirect.github.com/mockito/mockito/pull/3336";>mockito/mockito#3336) Fixes https://redirect.github.com/mockito/mockito/issues/3331";>#3331 : Fix AdditionalMatchers.and() and AdditionalMatchers.or() not to swap the order of matchers [(https://redirect.github.com/mockito/mockito/issues/3335";>#3335)](https://redirect.github.com/mockito/mockito/pull/3335";>mockito/mockito#3335) AdditionalMatchers.and() and or() swap matcher order [(https://redirect.github.com/mockito/mockito/issues/3331";>#3331)](https://redirect.github.com/mockito/mockito/issues/3331";>mockito/mockito#3331) Bump gradle/wrapper-validation-action from 3.3.1 to 3.3.2 [(https://redirect.github.com/mockito/mockito/issues/3327";>#3327)](https://redirect.github.com/mockito/mockito/pull/3327";>mockito/mockito#3327) Bump versions.bytebuddy from 1.14.13 to 1.14.14 [(https://redirect.github.com/mockito/mockito/issues/3324";>#3324)](https://redirect.github.com/mockito/mockito/pull/3324";>mockito/mockito#3324) Bump org.shipkit:shipkit-auto-version from 2.0.5 to 2.0.6 [(https://redirect.github.com/mockito/mockito/issues/3322";>#3322)](https://redirect.github.com/mockito/mockito/pull/3322";>mockito/mockito#3322) Bump gradle/wrapper-validation-action from 3.3.0 to 3.3.1 [(https://redirect.github.com/mockito/mockito/issues/3320";>#3320)](https://redirect.github.com/mockito/mockito/pull/3320";>mockito/mockito#3320) Bump com.gradle.enterprise from 3.17 to 3.17.2 [(https://redirect.github.com/mockito/mockito/issues/3318";>#3318)](https://redirect.github.com/mockito/mockito/pull/3318";>mockito/mockito#3318) Bump gradle/wrapper-validation-action from 2.1.2 to 3.3.0 [(https://redirect.github.com/mockito/mockito/issues/3317";>#3317)](https://redirect.github.com/mockito/mockito/pull/3317";>mockito/mockito#3317) Update codecov-action version [(https://redirect.github.com/mockito/mockito/issues/3316";>#3316)](https://redirect.github.com/mockito/mockito/pull/3316";>mockito/mockito#3316) Bump com.google.googlejavaformat:google-java-format from 1.21.0 to 1.22.0 [(https://redirect.github.com/mockito/mockito/issues/3312";>#3312)](https://redirect.github.com/mockito/mockito/pull/3312";>mockito/mockito#3312) Bump com.gradle.enterprise from 3.16.2 to 3.17 [(https://redirect.github.com/mockito/mockito/issues/3311";>#3311)](https://redirect.github.com/mockito/mockito/pull/3311";>mockito/mockito#3311) Bump versions.bytebuddy from 1.14.12 to 1.14.13 [(https://redirect.github.com/mockito/mockito/issues/3308";>#3308)](https://redirect.github.com/mockito/mockito/pull/3308";>mockito/mockito#3308) Fix README logo [(https://redirect.github.com/mockito/mockito/issues/3305";>#3305)](https://redirect.github.com/mockito/mockito/pull/3305";>mockito/mockito#3305) Bump gradle/wrapper-validation-action from 2.1.1 to 2.1.2 [(https://redirect.github.com/mockito/mockito/issues/3303";>#3303)](https://redirect.github.com/mockito/mockito/pull/3303";>mockito/mockito#3303) Bump org.shipkit:shipkit-auto-version from 2.0.4 to 2.0.5 [(https://redirect.github.com/mockito/mockito/issues/3298";>#3298)](https://redirect.github.com/mockito/mockito/pull/3298";>mockito/mockito#3298) Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 1.9.22 to 1.9.23 [(https://redirect.github.com/mockito/mockito/issues/3296";>#3296)](https://redirect.github.com/mockito/mockito/pull/3296";>mockito/mockito#3
[jira] [Commented] (MRESOLVER-588) Incomplete system properties in SessionBuilderSupplier
[
https://issues.apache.org/jira/browse/MRESOLVER-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875414#comment-17875414
]
ASF GitHub Bot commented on MRESOLVER-588:
--
HannesWell commented on PR #539:
URL: https://github.com/apache/maven-resolver/pull/539#issuecomment-2301559183
> * the goal of supplier is to provide "baseline" only, and nothing in
Resolver uses ENV variables
I understand that. But the problem can be and that's why I encountered this
at all, is that some artifacts cannot be resolved some system properties are
missing.
For example without any system-properties,
org.apache.commons:commons-text:1.12.0 fails to resolve with a
`ModelBuildingException` saying something like `[ERROR] Failed to determine
Java version for profile`. In this case the `java.version` property is missing
and e.g. the `animal-sniffer` profile from the `commons-parent` cannot
determine if the activation element `(,9)` is met or not. And since
properties and env-properties can also be used to activate profiles in general
and profiles can contain additional dependencies, not having them can influence
the resolution result.
A general property activation will probably not fail the resolution if a
property is missing (I haven't tested it), but the result would still be
different than in a default maven installation. So the resolver could
implicitly use env variablies.
But I cannot tell if the latter already is already out of the scope of the
baseline?
> Incomplete system properties in SessionBuilderSupplier
> --
>
> Key: MRESOLVER-588
> URL: https://issues.apache.org/jira/browse/MRESOLVER-588
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.0
>Reporter: Hannes Wellmann
>Priority: Major
>
> The {{SessionBuilderSupplier}} provided for Maven3 sets the java
> System.properties as systemProperties of the Session to be build.
> [https://github.com/apache/maven-resolver/blob/d13019ce5fa38c0951ca0fb0c62a3f5f1254cffc/maven-resolver-supplier-mvn3/src/main/java/org/eclipse/aether/supplier/SessionBuilderSupplier.java#L72]
> But it does not add environment variables with their key prefixed with
> {{env.}} like it is for example done in Maven or MIMA:
> [https://github.com/maveniverse/mima/blob/e851dee08706024929f1004e18e3dbd7b3522b36/runtime/standalone-shared/src/main/java/eu/maveniverse/maven/mima/runtime/shared/StandaloneRuntimeSupport.java#L519-L530]
>
> From looking at the code of the SessionBuilderSupplier for Maven 4, which
> relys heavily on
> {{org.apache.maven.repository.internal.MavenSessionBuilderSupplier }}system
> properties are not set at all.
> My suggestion is to extend the Maven3 SessionBuilderSupplier in
> Maven-Resolver and in maven4 {{MavenSessionBuilderSupplier to have
> system-properties and environment variables fully set by default.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump com.google.inject:guice from 5.1.0 to 7.0.0 [maven]
cstamas closed pull request #1669: Bump com.google.inject:guice from 5.1.0 to 7.0.0 URL: https://github.com/apache/maven/pull/1669 -- 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 com.google.inject:guice from 5.1.0 to 7.0.0 [maven]
cstamas commented on PR #1669: URL: https://github.com/apache/maven/pull/1669#issuecomment-2301562176 We cannot go to Guice 7 yet, we are still stuck on `javax.inject` -- 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 com.google.inject:guice from 5.1.0 to 7.0.0 [maven]
dependabot[bot] commented on PR #1669: URL: https://github.com/apache/maven/pull/1669#issuecomment-2301562242 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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 slf4jVersion from 1.7.36 to 2.0.16 [maven]
cstamas closed pull request #1668: Bump slf4jVersion from 1.7.36 to 2.0.16 URL: https://github.com/apache/maven/pull/1668 -- 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 slf4jVersion from 1.7.36 to 2.0.16 [maven]
cstamas commented on PR #1668: URL: https://github.com/apache/maven/pull/1668#issuecomment-2301562922 Maven3 remains on Slf4j 1.x for now, Maven4 goes 2.x -- 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 slf4jVersion from 1.7.36 to 2.0.16 [maven]
dependabot[bot] commented on PR #1668: URL: https://github.com/apache/maven/pull/1668#issuecomment-2301562979 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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.mockito:mockito-core from 4.11.0 to 5.12.0 [maven]
cstamas closed pull request #1667: Bump org.mockito:mockito-core from 4.11.0 to 5.12.0 URL: https://github.com/apache/maven/pull/1667 -- 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.mockito:mockito-core from 4.11.0 to 5.12.0 [maven]
cstamas commented on PR #1667: URL: https://github.com/apache/maven/pull/1667#issuecomment-2301564367 Maven3 is Java 8 -- 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.mockito:mockito-core from 4.11.0 to 5.12.0 [maven]
dependabot[bot] commented on PR #1667: URL: https://github.com/apache/maven/pull/1667#issuecomment-230156 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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.mockito:mockito-core from 4.11.0 to 5.12.0 [maven-resolver]
cstamas closed pull request #567: Bump org.mockito:mockito-core from 4.11.0 to 5.12.0 URL: https://github.com/apache/maven-resolver/pull/567 -- 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.mockito:mockito-core from 4.11.0 to 5.12.0 [maven-resolver]
cstamas commented on PR #567: URL: https://github.com/apache/maven-resolver/pull/567#issuecomment-2301565537 Resolver 1.x is Java 8 -- 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.mockito:mockito-core from 4.11.0 to 5.12.0 [maven-resolver]
dependabot[bot] commented on PR #567: URL: https://github.com/apache/maven-resolver/pull/567#issuecomment-2301565621 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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 com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]
cstamas commented on PR #564: URL: https://github.com/apache/maven-resolver/pull/564#issuecomment-2301566640 We are stuck still on Sisu and `javax.inject` -- 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 com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]
cstamas closed pull request #564: Bump com.google.inject:guice from 6.0.0 to 7.0.0 URL: https://github.com/apache/maven-resolver/pull/564 -- 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 com.google.inject:guice from 6.0.0 to 7.0.0 [maven-resolver]
dependabot[bot] commented on PR #564: URL: https://github.com/apache/maven-resolver/pull/564#issuecomment-2301566741 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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 slf4jVersion from 1.7.36 to 2.0.16 [maven-resolver]
cstamas closed pull request #563: Bump slf4jVersion from 1.7.36 to 2.0.16 URL: https://github.com/apache/maven-resolver/pull/563 -- 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 slf4jVersion from 1.7.36 to 2.0.16 [maven-resolver]
cstamas commented on PR #563: URL: https://github.com/apache/maven-resolver/pull/563#issuecomment-2301568112 Resolver 1.x is aligned with Maven 3.x: use Slf4j 1.x -- 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 slf4jVersion from 1.7.36 to 2.0.16 [maven-resolver]
dependabot[bot] commented on PR #563: URL: https://github.com/apache/maven-resolver/pull/563#issuecomment-2301568182 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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 jettyVersion from 9.4.54.v20240208 to 12.0.12 [maven-resolver]
cstamas commented on PR #565: URL: https://github.com/apache/maven-resolver/pull/565#issuecomment-2301569480 Going this is not trivial, requires code changes as well. Also, we are still Java 8. @olamy help! -- 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 jettyVersion from 9.4.54.v20240208 to 12.0.12 [maven-resolver]
cstamas closed pull request #565: Bump jettyVersion from 9.4.54.v20240208 to 12.0.12 URL: https://github.com/apache/maven-resolver/pull/565 -- 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 jettyVersion from 9.4.54.v20240208 to 12.0.12 [maven-resolver]
dependabot[bot] commented on PR #565: URL: https://github.com/apache/maven-resolver/pull/565#issuecomment-2301569566 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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] [MNG-8170] Switch to JLine3 JAnsi [maven]
cstamas closed pull request #1650: [MNG-8170] Switch to JLine3 JAnsi URL: https://github.com/apache/maven/pull/1650 -- 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-8170) Maven 3.9.8 contains weird native library for Jansi on Windows/arm64
[
https://issues.apache.org/jira/browse/MNG-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875417#comment-17875417
]
ASF GitHub Bot commented on MNG-8170:
-
cstamas closed pull request #1650: [MNG-8170] Switch to JLine3 JAnsi
URL: https://github.com/apache/maven/pull/1650
> Maven 3.9.8 contains weird native library for Jansi on Windows/arm64
>
>
> Key: MNG-8170
> URL: https://issues.apache.org/jira/browse/MNG-8170
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.8
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.10
>
>
> This doesn't look right:
> {noformat}
> $ tree
> .
> ├── README.txt
> └── Windows
> ├── arm64
> │ └── libjansi.so
> ├── x86
> │ └── jansi.dll
> └── x86_64
> └── jansi.dll
> 5 directories, 4 files
> osipovmi@deblndw011x:/tmp/apache-maven-3.9.8/lib/jansi-native
> $ file Windows/arm64/libjansi.so
> Windows/arm64/libjansi.so: PE32+ executable (DLL) (GUI) Aarch64, for MS
> Windows
> osipovmi@deblndw011x:/tmp/apache-maven-3.9.8/lib/jansi-native
> $ file Windows/x86_64/jansi.dll
> Windows/x86_64/jansi.dll: PE32+ executable (DLL) (console) x86-64, for MS
> Windows
> {noformat}
> 1. It should be console type
> 2. Name should be {{jansi.dll}}
> No?
> [~gnodet], [~cstamas].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MBUILDCACHE-103) Allow incremental restore in case of skipped plugin executions
[
https://issues.apache.org/jira/browse/MBUILDCACHE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Réda Housni Alaoui updated MBUILDCACHE-103:
---
Summary: Allow incremental restore in case of skipped plugin executions
(was: Allow incremental restore of skipped plugin executions)
> Allow incremental restore in case of skipped plugin executions
> --
>
> Key: MBUILDCACHE-103
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-103
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Reporter: Réda Housni Alaoui
>Priority: Major
>
> Property {{groups}} of {{maven-surefire-plugin}} allows to run a subset of
> tests matching the property value. E.g. {{groups=foo}} will only execute
> tests tagged with 'foo'.
> If I run a build with {{groups=foo}}, and if a cache entry exists for
> {{groups=null}} (i.e. no test filter), I want the cache entry to be reused as
> much as possible and the {{maven-surefire-plugin}} to be run on top of that.
> I think I need to specify that every non null value for groups should be
> considered as a skip value.
> Following this, what I need is the ability to declare a reconcile entry in
> xml config file looking like this:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Could we introduce this {{skipValueRegex}} that would allow to match multiple
> skip values and fix my issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MBUILDCACHE-103) Allow incremental restore of skipped plugin executions
[
https://issues.apache.org/jira/browse/MBUILDCACHE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Réda Housni Alaoui updated MBUILDCACHE-103:
---
Summary: Allow incremental restore of skipped plugin executions (was:
Unable to optimally reconcile maven-surefire-plugin 'groups' property)
> Allow incremental restore of skipped plugin executions
> --
>
> Key: MBUILDCACHE-103
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-103
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Reporter: Réda Housni Alaoui
>Priority: Major
>
> Property {{groups}} of {{maven-surefire-plugin}} allows to run a subset of
> tests matching the property value. E.g. {{groups=foo}} will only execute
> tests tagged with 'foo'.
> If I run a build with {{groups=foo}}, and if a cache entry exists for
> {{groups=null}} (i.e. no test filter), I want the cache entry to be reused as
> much as possible and the {{maven-surefire-plugin}} to be run on top of that.
> I think I need to specify that every non null value for groups should be
> considered as a skip value.
> Following this, what I need is the ability to declare a reconcile entry in
> xml config file looking like this:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Could we introduce this {{skipValueRegex}} that would allow to match multiple
> skip values and fix my issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8211] Fail the build if CI Friendly revision used without value [maven]
cstamas commented on PR #1656: URL: https://github.com/apache/maven/pull/1656#issuecomment-2301604056 This PR would really help to reduce user confusion with CI Friendly version. Combined with Nisse https://github.com/maveniverse/nisse they can have full experience. -- 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-8211) Maven should fail builds that use CI Friendly versions but have no values set
[
https://issues.apache.org/jira/browse/MNG-8211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875425#comment-17875425
]
ASF GitHub Bot commented on MNG-8211:
-
cstamas commented on PR #1656:
URL: https://github.com/apache/maven/pull/1656#issuecomment-2301604056
This PR would really help to reduce user confusion with CI Friendly version.
Combined with Nisse https://github.com/maveniverse/nisse they can have full
experience.
> Maven should fail builds that use CI Friendly versions but have no values set
> -
>
> Key: MNG-8211
> URL: https://issues.apache.org/jira/browse/MNG-8211
> Project: Maven
> Issue Type: Bug
> Components: Core
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.10
>
>
> As otherwise it is just source of confusion, Maven will "happily" install and
> deploy artifacts as {{G:A:$revision}} and this is 100% NOT what users wants.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MBUILDCACHE-105) Executing 'clean process-test-classes' then 'clean verify' leads to empty jars
Réda Housni Alaoui created MBUILDCACHE-105: -- Summary: Executing 'clean process-test-classes' then 'clean verify' leads to empty jars Key: MBUILDCACHE-105 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-105 Project: Maven Build Cache Extension Issue Type: Bug Reporter: Réda Housni Alaoui -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-6911) Allow the Maven model cache tto recache a maven model on request
[
https://issues.apache.org/jira/browse/MNG-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875453#comment-17875453
]
Daniel Puiu commented on MNG-6911:
--
Hello,
I encountered this issue on 3.8.4 and 3.9.6.
In my oppinion, the model cache should be updated when the artifact is
installed seeing that the model data references the path in local repo.
Regards
> Allow the Maven model cache tto recache a maven model on request
>
>
> Key: MNG-6911
> URL: https://issues.apache.org/jira/browse/MNG-6911
> Project: Maven
> Issue Type: Bug
> Components: IDEs, POM
>Affects Versions: 3.6.3
> Environment: Linux (Fedora 30-32)
>Reporter: Andrew Obuchowicz
>Priority: Major
>
> Hi, I'm one of the developers of
> [LemMinX-Maven|[https://github.com/eclipse/lemminx-maven]] which is a project
> that implements the Language Server Protocol for editing Maven pom.xml files
> (any LSP client editor can easily gain pom.xml editing features with this
> project).
>
> We've encountered an
> [issue|[https://github.com/eclipse/lemminx-maven/pull/67]] where
> modifications to a parent pom (such as adding a new property) are not
> reflected in the child pom, as the global model cache has an outdated version
> of the parent pom (before the modification was made).
>
> Disabling the global model cache works as a temporary workaround, eg.
>
> {code:java}
> System.setProperty(DefaultProjectBuilder.DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY,
> Boolean.toString(true));
> {code}
>
> However, we'd still like to use the model cache and not have to disable it
> entirely.
>
> Thus, it would be beneficial if the model cache could "uncache" (or refresh)
> a pom that has been modified. From our project, we can easily detect when a
> pom.xml has been modified, thus tracking pom modifications does not need to
> be implemented. *What is required on the Maven API side* is to be able to
> signal that a pom.xml has been modified, and should be recached with the new
> modifications.
>
> Also, I apologize in advance if this was reported under the wrong project or
> component. Feel free to place it where it should be.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-6911) Allow the Maven model cache tto recache a maven model on request
[
https://issues.apache.org/jira/browse/MNG-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875456#comment-17875456
]
Tamas Cservenak edited comment on MNG-6911 at 8/21/24 11:36 AM:
In general, if you put null value, it will "evict" it. Look into model cache
implementation, it just delegates to Resolver RepositoryCache, and
implementation does this:
https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.x/maven-resolver-api/src/main/java/org/eclipse/aether/DefaultRepositoryCache.java#L36-L42
was (Author: cstamas):
In general, if you put null value, it is "uncache" it. Look into model cache
implementation, it just delegates to Resolver RepositoryCache, and
implementation does this:
https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.x/maven-resolver-api/src/main/java/org/eclipse/aether/DefaultRepositoryCache.java#L36-L42
> Allow the Maven model cache tto recache a maven model on request
>
>
> Key: MNG-6911
> URL: https://issues.apache.org/jira/browse/MNG-6911
> Project: Maven
> Issue Type: Bug
> Components: IDEs, POM
>Affects Versions: 3.6.3
> Environment: Linux (Fedora 30-32)
>Reporter: Andrew Obuchowicz
>Priority: Major
>
> Hi, I'm one of the developers of
> [LemMinX-Maven|[https://github.com/eclipse/lemminx-maven]] which is a project
> that implements the Language Server Protocol for editing Maven pom.xml files
> (any LSP client editor can easily gain pom.xml editing features with this
> project).
>
> We've encountered an
> [issue|[https://github.com/eclipse/lemminx-maven/pull/67]] where
> modifications to a parent pom (such as adding a new property) are not
> reflected in the child pom, as the global model cache has an outdated version
> of the parent pom (before the modification was made).
>
> Disabling the global model cache works as a temporary workaround, eg.
>
> {code:java}
> System.setProperty(DefaultProjectBuilder.DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY,
> Boolean.toString(true));
> {code}
>
> However, we'd still like to use the model cache and not have to disable it
> entirely.
>
> Thus, it would be beneficial if the model cache could "uncache" (or refresh)
> a pom that has been modified. From our project, we can easily detect when a
> pom.xml has been modified, thus tracking pom modifications does not need to
> be implemented. *What is required on the Maven API side* is to be able to
> signal that a pom.xml has been modified, and should be recached with the new
> modifications.
>
> Also, I apologize in advance if this was reported under the wrong project or
> component. Feel free to place it where it should be.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6911) Allow the Maven model cache tto recache a maven model on request
[
https://issues.apache.org/jira/browse/MNG-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875456#comment-17875456
]
Tamas Cservenak commented on MNG-6911:
--
In general, if you put null value, it is "uncache" it. Look into model cache
implementation, it just delegates to Resolver RepositoryCache, and
implementation does this:
https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.x/maven-resolver-api/src/main/java/org/eclipse/aether/DefaultRepositoryCache.java#L36-L42
> Allow the Maven model cache tto recache a maven model on request
>
>
> Key: MNG-6911
> URL: https://issues.apache.org/jira/browse/MNG-6911
> Project: Maven
> Issue Type: Bug
> Components: IDEs, POM
>Affects Versions: 3.6.3
> Environment: Linux (Fedora 30-32)
>Reporter: Andrew Obuchowicz
>Priority: Major
>
> Hi, I'm one of the developers of
> [LemMinX-Maven|[https://github.com/eclipse/lemminx-maven]] which is a project
> that implements the Language Server Protocol for editing Maven pom.xml files
> (any LSP client editor can easily gain pom.xml editing features with this
> project).
>
> We've encountered an
> [issue|[https://github.com/eclipse/lemminx-maven/pull/67]] where
> modifications to a parent pom (such as adding a new property) are not
> reflected in the child pom, as the global model cache has an outdated version
> of the parent pom (before the modification was made).
>
> Disabling the global model cache works as a temporary workaround, eg.
>
> {code:java}
> System.setProperty(DefaultProjectBuilder.DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY,
> Boolean.toString(true));
> {code}
>
> However, we'd still like to use the model cache and not have to disable it
> entirely.
>
> Thus, it would be beneficial if the model cache could "uncache" (or refresh)
> a pom that has been modified. From our project, we can easily detect when a
> pom.xml has been modified, thus tracking pom modifications does not need to
> be implemented. *What is required on the Maven API side* is to be able to
> signal that a pom.xml has been modified, and should be recached with the new
> modifications.
>
> Also, I apologize in advance if this was reported under the wrong project or
> component. Feel free to place it where it should be.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6911) Allow the Maven model cache tto recache a maven model on request
[
https://issues.apache.org/jira/browse/MNG-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875458#comment-17875458
]
Daniel Puiu commented on MNG-6911:
--
Ok, but the problem is that both the key and data are package private classes.
It doesn't seem easy to get hold of the key.
Also, I will be forced to implement RepositoryListener to know when artifacts
are installed to evict them.
> Allow the Maven model cache tto recache a maven model on request
>
>
> Key: MNG-6911
> URL: https://issues.apache.org/jira/browse/MNG-6911
> Project: Maven
> Issue Type: Bug
> Components: IDEs, POM
>Affects Versions: 3.6.3
> Environment: Linux (Fedora 30-32)
>Reporter: Andrew Obuchowicz
>Priority: Major
>
> Hi, I'm one of the developers of
> [LemMinX-Maven|[https://github.com/eclipse/lemminx-maven]] which is a project
> that implements the Language Server Protocol for editing Maven pom.xml files
> (any LSP client editor can easily gain pom.xml editing features with this
> project).
>
> We've encountered an
> [issue|[https://github.com/eclipse/lemminx-maven/pull/67]] where
> modifications to a parent pom (such as adding a new property) are not
> reflected in the child pom, as the global model cache has an outdated version
> of the parent pom (before the modification was made).
>
> Disabling the global model cache works as a temporary workaround, eg.
>
> {code:java}
> System.setProperty(DefaultProjectBuilder.DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY,
> Boolean.toString(true));
> {code}
>
> However, we'd still like to use the model cache and not have to disable it
> entirely.
>
> Thus, it would be beneficial if the model cache could "uncache" (or refresh)
> a pom that has been modified. From our project, we can easily detect when a
> pom.xml has been modified, thus tracking pom modifications does not need to
> be implemented. *What is required on the Maven API side* is to be able to
> signal that a pom.xml has been modified, and should be recached with the new
> modifications.
>
> Also, I apologize in advance if this was reported under the wrong project or
> component. Feel free to place it where it should be.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6911) Allow the Maven model cache tto recache a maven model on request
[
https://issues.apache.org/jira/browse/MNG-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875459#comment-17875459
]
Tamas Cservenak commented on MNG-6911:
--
ModelCache is derived from session, so you can just do
{noformat}
ModelCache cache = new DefaultModelCacheFactory().createCache(session);
{noformat}
And it will give you _same_ cache backed by same session (unless model cache
factory overridden, but in Maven is not, unsure for Eclipse universe).
And then just
{noformat}
putCache(groupId, artifactId, version, ModelCacheTag.RAW, null);
{noformat}
> Allow the Maven model cache tto recache a maven model on request
>
>
> Key: MNG-6911
> URL: https://issues.apache.org/jira/browse/MNG-6911
> Project: Maven
> Issue Type: Bug
> Components: IDEs, POM
>Affects Versions: 3.6.3
> Environment: Linux (Fedora 30-32)
>Reporter: Andrew Obuchowicz
>Priority: Major
>
> Hi, I'm one of the developers of
> [LemMinX-Maven|[https://github.com/eclipse/lemminx-maven]] which is a project
> that implements the Language Server Protocol for editing Maven pom.xml files
> (any LSP client editor can easily gain pom.xml editing features with this
> project).
>
> We've encountered an
> [issue|[https://github.com/eclipse/lemminx-maven/pull/67]] where
> modifications to a parent pom (such as adding a new property) are not
> reflected in the child pom, as the global model cache has an outdated version
> of the parent pom (before the modification was made).
>
> Disabling the global model cache works as a temporary workaround, eg.
>
> {code:java}
> System.setProperty(DefaultProjectBuilder.DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY,
> Boolean.toString(true));
> {code}
>
> However, we'd still like to use the model cache and not have to disable it
> entirely.
>
> Thus, it would be beneficial if the model cache could "uncache" (or refresh)
> a pom that has been modified. From our project, we can easily detect when a
> pom.xml has been modified, thus tracking pom modifications does not need to
> be implemented. *What is required on the Maven API side* is to be able to
> signal that a pom.xml has been modified, and should be recached with the new
> modifications.
>
> Also, I apologize in advance if this was reported under the wrong project or
> component. Feel free to place it where it should be.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0 [maven]
cstamas merged PR #1664: URL: https://github.com/apache/maven/pull/1664 -- 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] (MNG-8219) (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0
[ https://issues.apache.org/jira/browse/MNG-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8219. Assignee: Tamas Cservenak Resolution: Fixed > (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to > 0.23.0 > - > > Key: MNG-8219 > URL: https://issues.apache.org/jira/browse/MNG-8219 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8219) (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0
Tamas Cservenak created MNG-8219: Summary: (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0 Key: MNG-8219 URL: https://issues.apache.org/jira/browse/MNG-8219 Project: Maven Issue Type: Dependency upgrade Components: Bootstrap & Build Reporter: Tamas Cservenak Fix For: 4.0.0, 4.0.0-beta-4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-6911) Allow the Maven model cache tto recache a maven model on request
[
https://issues.apache.org/jira/browse/MNG-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875490#comment-17875490
]
Daniel Puiu commented on MNG-6911:
--
Yes, it works on maven 3.9.6 which is great.
Unfortunately for us, we have multiple long term branches for our code, running
on 3.9.6, 3.8.4 and 3.6.3.
Fortunately for us, we can install the parent pom as a workaround before
starting the build.
Thanks for the help.
> Allow the Maven model cache tto recache a maven model on request
>
>
> Key: MNG-6911
> URL: https://issues.apache.org/jira/browse/MNG-6911
> Project: Maven
> Issue Type: Bug
> Components: IDEs, POM
>Affects Versions: 3.6.3
> Environment: Linux (Fedora 30-32)
>Reporter: Andrew Obuchowicz
>Priority: Major
>
> Hi, I'm one of the developers of
> [LemMinX-Maven|[https://github.com/eclipse/lemminx-maven]] which is a project
> that implements the Language Server Protocol for editing Maven pom.xml files
> (any LSP client editor can easily gain pom.xml editing features with this
> project).
>
> We've encountered an
> [issue|[https://github.com/eclipse/lemminx-maven/pull/67]] where
> modifications to a parent pom (such as adding a new property) are not
> reflected in the child pom, as the global model cache has an outdated version
> of the parent pom (before the modification was made).
>
> Disabling the global model cache works as a temporary workaround, eg.
>
> {code:java}
> System.setProperty(DefaultProjectBuilder.DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY,
> Boolean.toString(true));
> {code}
>
> However, we'd still like to use the model cache and not have to disable it
> entirely.
>
> Thus, it would be beneficial if the model cache could "uncache" (or refresh)
> a pom that has been modified. From our project, we can easily detect when a
> pom.xml has been modified, thus tracking pom modifications does not need to
> be implemented. *What is required on the Maven API side* is to be able to
> signal that a pom.xml has been modified, and should be recached with the new
> modifications.
>
> Also, I apologize in advance if this was reported under the wrong project or
> component. Feel free to place it where it should be.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MBUILDCACHE-101] mvn test fails on missing classes after mvn compile leads to empty jars [maven-build-cache-extension]
reda-alaoui opened a new pull request, #176: URL: https://github.com/apache/maven-build-cache-extension/pull/176 This PR makes sure any cached build that doesn't involve phase `package` is considered as invalid. -- Following this checklist to help us incorporate your contribution quickly and easily: - [X] Make sure there is a [MBUILDCACHE JIRA issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- 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] (MBUILDCACHE-101) mvn test fails on missing classes after mvn compile
[
https://issues.apache.org/jira/browse/MBUILDCACHE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated MBUILDCACHE-101:
---
Labels: pull-request-available (was: )
> mvn test fails on missing classes after mvn compile
> ---
>
> Key: MBUILDCACHE-101
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-101
> Project: Maven Build Cache Extension
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Amir Hadadi
>Priority: Major
> Labels: pull-request-available
>
> Using a project whose artifacts are not cached locally or remotely, do the
> following:
> {code:java}
> mvn compile{code}
> This will compile the code and mark the compile plugin goal as cached.
> If you now run:
> {code:java}
> mvn clean test{code}
> You will see in the log:
> {code:java}
> Skipping plugin execution (cached): compiler:compile{code}
> and then the build will fail due to missing classes, since it will not run
> the compile phase again (as it was marked cached) and it has nowhere to pull
> the compiled classes from.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-101) mvn test fails on missing classes after mvn compile
[
https://issues.apache.org/jira/browse/MBUILDCACHE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875519#comment-17875519
]
ASF GitHub Bot commented on MBUILDCACHE-101:
reda-alaoui opened a new pull request, #176:
URL: https://github.com/apache/maven-build-cache-extension/pull/176
This PR makes sure any cached build that doesn't involve phase `package` is
considered as invalid.
--
Following this checklist to help us incorporate your
contribution quickly and easily:
- [X] Make sure there is a [MBUILDCACHE JIRA
issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [X] Each commit in the pull request should have a meaningful subject line
and body.
- [X] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue.
Best practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [X] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [X] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [X] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [X] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
> mvn test fails on missing classes after mvn compile
> ---
>
> Key: MBUILDCACHE-101
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-101
> Project: Maven Build Cache Extension
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Amir Hadadi
>Priority: Major
>
> Using a project whose artifacts are not cached locally or remotely, do the
> following:
> {code:java}
> mvn compile{code}
> This will compile the code and mark the compile plugin goal as cached.
> If you now run:
> {code:java}
> mvn clean test{code}
> You will see in the log:
> {code:java}
> Skipping plugin execution (cached): compiler:compile{code}
> and then the build will fail due to missing classes, since it will not run
> the compile phase again (as it was marked cached) and it has nowhere to pull
> the compiled classes from.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set
Bruno Villegas created MWRAPPER-146:
---
Summary: Bad substitution on Windows if MVNW_REPOURL is set
Key: MWRAPPER-146
URL: https://issues.apache.org/jira/browse/MWRAPPER-146
Project: Maven Wrapper
Issue Type: Bug
Components: Maven Wrapper Scripts
Affects Versions: 3.3.2, 3.3.1, 3.3.0
Environment: Windows 10, Windows Server 2022 with powershell 5.1
Reporter: Bruno Villegas
Since version 3.3.0, we cannot set MVNW_REPOURL on Windows platforms (Windows
10, Windows Server 2022).
If MVNW_VERBOSE is set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Villegas updated MWRAPPER-146:
Description:
Since version 3.3.0, we cannot set MVNW_REPOURL on Windows platforms (Windows
10, Windows Server 2022).
If MVNW_VERBOSE is set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
{noformat}
was:
Since version 3.3.0, we cannot set MVNW_REPOURL on Windows platforms (Windows
10, Windows Server 2022).
If MVNW_VERBOSE is set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME,
[jira] [Updated] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Villegas updated MWRAPPER-146:
Description:
Since version 3.3.0, we cannot set MVNW_REPOURL on Windows platforms (Windows
10, Windows Server 2022).
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
{noformat}
was:
Since version 3.3.0, we cannot set MVNW_REPOURL on Windows platforms (Windows
10, Windows Server 2022).
If MVNW_VERBOSE is set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN
[jira] [Updated] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Villegas updated MWRAPPER-146:
Description:
Since version 3.3.0, we cannot download Maven distribution if we set
MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022).
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) : «
Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
{noformat}
was:
Since version 3.3.0, we cannot set MVNW_REPOURL on Windows platforms (Windows
10, Windows Server 2022).
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATT
[jira] [Updated] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Villegas updated MWRAPPER-146:
Summary: Bad substitution on Windows if MVNW_REPOURL is set on script-only
(was: Bad substitution on Windows if MVNW_REPOURL is set )
> Bad substitution on Windows if MVNW_REPOURL is set on script-only
> -
>
> Key: MWRAPPER-146
> URL: https://issues.apache.org/jira/browse/MWRAPPER-146
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0, 3.3.1, 3.3.2
> Environment: Windows 10, Windows Server 2022 with powershell 5.1
>Reporter: Bruno Villegas
>Priority: Major
>
> Since version 3.3.0, we cannot download Maven distribution if we set
> MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022).
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) :
> « Le serveur distant a retourné une erreur : (404) Introuvable. »
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> If MVNW_VERBOSE is also set to "true" we can have some hints
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
> icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
> serveur distant a retourné une erreur:
> (404) Introuvable.»
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> $env:MVNW_REPOURL is concatened with mvnd context and the actual
> distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
> Looking at script mvnw.cmd, it seems that the following block is at fault
> {code:java}
> # apply MVNW_REPOURL and calculate MAVEN_HOME
> # maven home pattern:
> ~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
> if ($env:MVNW_REPOURL) {
> $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
> "/maven/mvnd/" }
> $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
> -replace '^.*'+$MVNW_REPO_PATTERN,'')"
> } {code}
> Two "bugs" in my opinion
> - USE_MVND evaluation is incorrect: should have been
> {code:java}
> if ($USE_MVND -eq $False){code}
> the variable USE_MVND is previously set to either $true or $false
>
> - The string substitution doesn't work correctly, the following works for my
> environment
> {code:java}
> $($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
> After fixing these two lines
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Villegas updated MWRAPPER-146:
Description:
Since version 3.3.0, we cannot download Maven distribution if we set
MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
script-only.
{noformat}
wrapperVersion=3.3.2
distributionType=only-script
distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip{noformat}
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) : «
Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
{noformat}
was:
Since version 3.3.0, we cannot download Maven distribution if we set
MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
script-only.
{noformat}
*aucun* autre _formatage_ n'est effectué ici{noformat}
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) : «
Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
[jira] [Updated] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Villegas updated MWRAPPER-146:
Description:
Since version 3.3.0, we cannot download Maven distribution if we set
MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
script-only.
{noformat}
*aucun* autre _formatage_ n'est effectué ici{noformat}
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) : «
Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
$env:MVNW_REPOURL is concatened with mvnd context and the actual
distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
Looking at script mvnw.cmd, it seems that the following block is at fault
{code:java}
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
$MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
$distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
} {code}
Two "bugs" in my opinion
- USE_MVND evaluation is incorrect: should have been
{code:java}
if ($USE_MVND -eq $False){code}
the variable USE_MVND is previously set to either $true or $false
- The string substitution doesn't work correctly, the following works for my
environment
{code:java}
$($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
After fixing these two lines
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
{noformat}
was:
Since version 3.3.0, we cannot download Maven distribution if we set
MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022).
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) : «
Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw ...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper{noformat}
If MVNW_VERBOSE is also set to "true" we can have some hints
{noformat}
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock (
[PR] [MWRAPPER-146] Bad substitution on Windows if MVNW_REPOURL is set on script-only [maven-wrapper]
jahk04 opened a new pull request, #151:
URL: https://github.com/apache/maven-wrapper/pull/151
Since version 3.3.0, we cannot download Maven distribution if we set
`MVNW_REPOURL` on Windows platforms (Windows 10, Windows Server 2022) with
script-only.
``` text
wrapperVersion=3.3.2
distributionType=only-script
distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.z
```ip
Current result (3.3.2)
``` text
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) :
« Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper
```
Expected result was
``` text
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
```
If *MVNW_VERBOSE* is also set to `true` we can have some hints
``` text
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper
```
`$env:MVNW_REPOURL` is concatened with mvnd context and the actual
`distributionUrl` defined inside `.mvn/wrapper/maven-wrapper.properties`
Looking at script `mvnw.cmd`, it seems that the following block is at fault
with two "bugs"
- `USE_MVND` evaluation is incorrect
- string substitution of `distributionUrl` is incorrect
``` diff
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
- $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
+ $MVNW_REPO_PATTERN = if ($USE_MVND -eq $False) { "/org/apache/maven/" }
else { "/maven/mvnd/" }
- $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
+ $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace "^.*$MVNW_REPO_PATTERN",'')"
}
```
I hereby declare this contribution to be licenced under the [Apache License
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
--
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] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875541#comment-17875541
]
ASF GitHub Bot commented on MWRAPPER-146:
-
jahk04 opened a new pull request, #151:
URL: https://github.com/apache/maven-wrapper/pull/151
Since version 3.3.0, we cannot download Maven distribution if we set
`MVNW_REPOURL` on Windows platforms (Windows 10, Windows Server 2022) with
script-only.
``` text
wrapperVersion=3.3.2
distributionType=only-script
distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.z
```ip
Current result (3.3.2)
``` text
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) :
« Le serveur distant a retourné une erreur : (404) Introuvable. »
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper
```
Expected result was
``` text
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
```
If *MVNW_VERBOSE* is also set to `true` we can have some hints
``` text
PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
COMMENTAIRES : Downloading from:
https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
COMMENTAIRES : Downloading to:
C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
serveur distant a retourné une erreur:
(404) Introuvable.»
Au caractère Ligne:1 : 72
+ ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
...
+ ~
+ CategoryInfo : NotSpecified: (:) [Invoke-Command],
MethodInvocationException
+ FullyQualifiedErrorId :
WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
Commande ECHO activée.
Cannot start maven from wrapper
```
`$env:MVNW_REPOURL` is concatened with mvnd context and the actual
`distributionUrl` defined inside `.mvn/wrapper/maven-wrapper.properties`
Looking at script `mvnw.cmd`, it seems that the following block is at fault
with two "bugs"
- `USE_MVND` evaluation is incorrect
- string substitution of `distributionUrl` is incorrect
``` diff
# apply MVNW_REPOURL and calculate MAVEN_HOME
# maven home pattern:
~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
if ($env:MVNW_REPOURL) {
- $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
"/maven/mvnd/" }
+ $MVNW_REPO_PATTERN = if ($USE_MVND -eq $False) { "/org/apache/maven/" }
else { "/maven/mvnd/" }
- $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace '^.*'+$MVNW_REPO_PATTERN,'')"
+ $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
-replace "^.*$MVNW_REPO_PATTERN",'')"
}
```
I hereby declare this contribution to be licenced under the [Apache License
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
> Bad substitution on Windows if MVNW_REPOURL is set on script-only
> -
>
> Key: MWRAPPER-146
> URL: https://issues.apache.org/jira/browse/MWRAPPER-146
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0, 3.3.1, 3.3.2
> Environment: Windows 10, Windows Server 2022 with powershell 5.1
>Reporter: Bruno Villegas
>Priority: Major
>
> Since version 3.3.0, we cannot download Maven distribution if we set
> MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
> script-only.
> {noformat}
> wrapperVersion=3.3.2
> distributionType=only-script
> distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip{noformat}
> {noformat}
> P
[jira] [Commented] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875543#comment-17875543
]
Bruno Villegas commented on MWRAPPER-146:
-
[Pull-request #151|https://github.com/apache/maven-wrapper/pull/151]
> Bad substitution on Windows if MVNW_REPOURL is set on script-only
> -
>
> Key: MWRAPPER-146
> URL: https://issues.apache.org/jira/browse/MWRAPPER-146
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0, 3.3.1, 3.3.2
> Environment: Windows 10, Windows Server 2022 with powershell 5.1
>Reporter: Bruno Villegas
>Priority: Major
>
> Since version 3.3.0, we cannot download Maven distribution if we set
> MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
> script-only.
> {noformat}
> wrapperVersion=3.3.2
> distributionType=only-script
> distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip{noformat}
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) :
> « Le serveur distant a retourné une erreur : (404) Introuvable. »
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> If MVNW_VERBOSE is also set to "true" we can have some hints
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
> icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
> serveur distant a retourné une erreur:
> (404) Introuvable.»
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> $env:MVNW_REPOURL is concatened with mvnd context and the actual
> distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
> Looking at script mvnw.cmd, it seems that the following block is at fault
> {code:java}
> # apply MVNW_REPOURL and calculate MAVEN_HOME
> # maven home pattern:
> ~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
> if ($env:MVNW_REPOURL) {
> $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
> "/maven/mvnd/" }
> $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
> -replace '^.*'+$MVNW_REPO_PATTERN,'')"
> } {code}
> Two "bugs" in my opinion
> - USE_MVND evaluation is incorrect: should have been
> {code:java}
> if ($USE_MVND -eq $False){code}
> the variable USE_MVND is previously set to either $true or $false
>
> - The string substitution doesn't work correctly, the following works for my
> environment
> {code:java}
> $($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
> After fixing these two lines
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-952) Unpack fails if extension of artifact is used
Pascal Schumacher created MDEP-952:
--
Summary: Unpack fails if extension of artifact is used
Key: MDEP-952
URL: https://issues.apache.org/jira/browse/MDEP-952
Project: Maven Dependency Plugin
Issue Type: Bug
Components: unpack
Affects Versions: 3.7.1, 3.7.0
Reporter: Pascal Schumacher
With 3.6.0 this works:
{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
Downloading from artifactory-dms-maven-virtual:
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
Downloaded from artifactory-dms-maven-virtual:
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at 4.2
kB/s)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.231 s
[INFO] Finished at: 2024-08-21T16:59:57+02:00
[INFO]
{quote}
but it fails with 3.7.0 and 3.7.1:
{quote}
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.859 s
{quote}
If the extension is omitted it works with all version (This is a simplified
example, the real use case is a private zip artifact.)
I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.
By the way: Thank you very much for developing/providing the Maven Dependency
Plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-952) Unpack fails if extension of artifact is used
[
https://issues.apache.org/jira/browse/MDEP-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated MDEP-952:
---
Description:
With 3.6.0 this works:
{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.859 s
[INFO] Finished at: 2024-08-21T17:00:12+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.:
NullPointerException -> [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/PluginExecutionException
{quote}
but it fails with 3.7.0 and 3.7.1:
{quote}
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.859 s
{quote}
If the extension is omitted it works with all version (This is a simplified
example, the real use case is a private zip artifact.)
I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.
By the way: Thank you very much for developing/providing the Maven Dependency
Plugin.
was:
With 3.6.0 this works:
{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
Downloading from artifactory-dms-maven-virtual:
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
Downloaded from artifactory-dms-maven-virtual:
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at 4.2
kB/s)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.231 s
[INFO] Finished at: 2024-08-21T16:59:57+02:00
[INFO]
{quote}
but it fails with 3.7.0 and 3.7.1:
{quote}
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.859 s
{quote}
If the extension is omitted it works with all version (This is a simplified
example, the real use case is a private zip artifact.)
I tried it with Maven
[jira] [Updated] (MDEP-952) Unpack fails if extension of artifact is used
[
https://issues.apache.org/jira/browse/MDEP-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated MDEP-952:
---
Description:
With 3.6.0 this works:
{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
Downloading from artifactory-dms-maven-virtual:
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
Downloaded from artifactory-dms-maven-virtual:
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at 4.2
kB/s)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.231 s
[INFO] Finished at: 2024-08-21T16:59:57+02:00
[INFO]
{quote}
but it fails with 3.7.0 and 3.7.1:
{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.859 s
[INFO] Finished at: 2024-08-21T17:00:12+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.:
NullPointerException -> [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/PluginExecutionException
{quote}
If the extension is omitted it works with all version (This is a simplified
example, the real use case is a private zip artifact.)
I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.
By the way: Thank you very much for developing/providing the Maven Dependency
Plugin.
was:
With 3.6.0 this works:
{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.859 s
[INFO] Finished at: 2024-08-21T17:00:12+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.:
NullPointerException -> [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/PluginExecutionException
{quote}
but it fails with 3.7.0 and 3.7.1:
{quote}
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[jira] [Commented] (MDEP-952) Unpack fails if extension of artifact is used
[
https://issues.apache.org/jira/browse/MDEP-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875590#comment-17875590
]
Michael Osipov commented on MDEP-952:
-
I would recommend bisecting to the change which introduced this issue.
> Unpack fails if extension of artifact is used
> -
>
> Key: MDEP-952
> URL: https://issues.apache.org/jira/browse/MDEP-952
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
>Affects Versions: 3.7.0, 3.7.1
>Reporter: Pascal Schumacher
>Priority: Major
> Labels: regresion
>
> With 3.6.0 this works:
> {quote}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack
> -Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven:standalone-pom
> >---
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
> [INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
> Downloading from artifactory-dms-maven-virtual:
> https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
> Downloaded from artifactory-dms-maven-virtual:
> https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at
> 4.2 kB/s)
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 2.231 s
> [INFO] Finished at: 2024-08-21T16:59:57+02:00
> [INFO]
>
> {quote}
> but it fails with 3.7.0 and 3.7.1:
> {quote}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack
> -Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
> tory=.
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven:standalone-pom
> >---
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
> [INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.859 s
> [INFO] Finished at: 2024-08-21T17:00:12+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli)
> on project standalone-pom: Execution default-cli of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.:
> NullPointerException -> [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/PluginExecutionException
> {quote}
> If the extension is omitted it works with all version (This is a simplified
> example, the real use case is a private zip artifact.)
> I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.
> By the way: Thank you very much for developing/providing the Maven Dependency
> Plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MBUILDCACHE-103] Allow incremental restore in case of plugin parameter mismatch [maven-build-cache-extension]
reda-alaoui opened a new pull request, #177: URL: https://github.com/apache/maven-build-cache-extension/pull/177 Following this checklist to help us incorporate your contribution quickly and easily: - [X] Make sure there is a [MBUILDCACHE JIRA issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- 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] (MBUILDCACHE-103) Allow incremental restore in case of plugin parameter mismatch
[
https://issues.apache.org/jira/browse/MBUILDCACHE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875594#comment-17875594
]
ASF GitHub Bot commented on MBUILDCACHE-103:
reda-alaoui opened a new pull request, #177:
URL: https://github.com/apache/maven-build-cache-extension/pull/177
Following this checklist to help us incorporate your
contribution quickly and easily:
- [X] Make sure there is a [MBUILDCACHE JIRA
issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [X] Each commit in the pull request should have a meaningful subject line
and body.
- [X] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue.
Best practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [X] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [X] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [X] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [X] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
> Allow incremental restore in case of plugin parameter mismatch
> --
>
> Key: MBUILDCACHE-103
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-103
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Reporter: Réda Housni Alaoui
>Priority: Major
>
> Property {{groups}} of {{maven-surefire-plugin}} allows to run a subset of
> tests matching the property value. E.g. {{groups=foo}} will only execute
> tests tagged with 'foo'.
> If I run a build with {{groups=foo}}, and if a cache entry exists for
> {{groups=null}} (i.e. no test filter), I want the cache entry to be reused as
> much as possible and the {{maven-surefire-plugin}} to be run on top of that.
> I think I need to specify that every non null value for groups should be
> considered as a skip value.
> Following this, what I need is the ability to declare a reconcile entry in
> xml config file looking like this:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Could we introduce this {{skipValueRegex}} that would allow to match multiple
> skip values and fix my issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MBUILDCACHE-103) Allow incremental restore in case of plugin parameter mismatch
[
https://issues.apache.org/jira/browse/MBUILDCACHE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated MBUILDCACHE-103:
---
Labels: pull-request-available (was: )
> Allow incremental restore in case of plugin parameter mismatch
> --
>
> Key: MBUILDCACHE-103
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-103
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Reporter: Réda Housni Alaoui
>Priority: Major
> Labels: pull-request-available
>
> Property {{groups}} of {{maven-surefire-plugin}} allows to run a subset of
> tests matching the property value. E.g. {{groups=foo}} will only execute
> tests tagged with 'foo'.
> If I run a build with {{groups=foo}}, and if a cache entry exists for
> {{groups=null}} (i.e. no test filter), I want the cache entry to be reused as
> much as possible and the {{maven-surefire-plugin}} to be run on top of that.
> I think I need to specify that every non null value for groups should be
> considered as a skip value.
> Following this, what I need is the ability to declare a reconcile entry in
> xml config file looking like this:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Could we introduce this {{skipValueRegex}} that would allow to match multiple
> skip values and fix my issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MBUILDCACHE-103) Allow incremental restore in case of plugin parameter mismatch
[
https://issues.apache.org/jira/browse/MBUILDCACHE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Réda Housni Alaoui updated MBUILDCACHE-103:
---
Summary: Allow incremental restore in case of plugin parameter mismatch
(was: Allow incremental restore in case of skipped plugin executions)
> Allow incremental restore in case of plugin parameter mismatch
> --
>
> Key: MBUILDCACHE-103
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-103
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Reporter: Réda Housni Alaoui
>Priority: Major
>
> Property {{groups}} of {{maven-surefire-plugin}} allows to run a subset of
> tests matching the property value. E.g. {{groups=foo}} will only execute
> tests tagged with 'foo'.
> If I run a build with {{groups=foo}}, and if a cache entry exists for
> {{groups=null}} (i.e. no test filter), I want the cache entry to be reused as
> much as possible and the {{maven-surefire-plugin}} to be run on top of that.
> I think I need to specify that every non null value for groups should be
> considered as a skip value.
> Following this, what I need is the ability to declare a reconcile entry in
> xml config file looking like this:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Could we introduce this {{skipValueRegex}} that would allow to match multiple
> skip values and fix my issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.apache.commons:commons-compress from 1.27.0 to 1.27.1 [maven-surefire]
michael-o merged PR #771: URL: https://github.com/apache/maven-surefire/pull/771 -- 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] [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack [maven-pmd-plugin]
michael-o closed pull request #126: [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack URL: https://github.com/apache/maven-pmd-plugin/pull/126 -- 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] [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack [maven-pmd-plugin]
michael-o merged PR #126: URL: https://github.com/apache/maven-pmd-plugin/pull/126 -- 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-389) Upgrade to Doxia 2.0.0 Milestone Stack
[
https://issues.apache.org/jira/browse/MPMD-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875626#comment-17875626
]
ASF GitHub Bot commented on MPMD-389:
-
michael-o merged PR #126:
URL: https://github.com/apache/maven-pmd-plugin/pull/126
> Upgrade to Doxia 2.0.0 Milestone Stack
> --
>
> Key: MPMD-389
> URL: https://issues.apache.org/jira/browse/MPMD-389
> Project: Maven PMD Plugin
> Issue Type: Dependency upgrade
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.25.0
>
>
> * Upgrade to Doxia 2.0.0-M12
> * Upgrade to Maven Site Plugin 3.20.0
> * Upgrade to Maven Project Info Reports Plugin 3.7.0
> * Upgrade to Maven JXR Plugin 3.4.0
> * Upgrade to Maven Reporting Impl 4.0.0-M15
> Also, for consistency reasons the parameter {{includeXmlInSite}} will be
> renamed to {{includeXmlInReports}} to better reflect that this plugin does
> not only run in site mode, but also in standalone mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-389) Upgrade to Doxia 2.0.0 Milestone Stack
[
https://issues.apache.org/jira/browse/MPMD-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875625#comment-17875625
]
ASF GitHub Bot commented on MPMD-389:
-
michael-o closed pull request #126: [MPMD-389] Upgrade to Doxia 2.0.0 Milestone
Stack
URL: https://github.com/apache/maven-pmd-plugin/pull/126
> Upgrade to Doxia 2.0.0 Milestone Stack
> --
>
> Key: MPMD-389
> URL: https://issues.apache.org/jira/browse/MPMD-389
> Project: Maven PMD Plugin
> Issue Type: Dependency upgrade
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.25.0
>
>
> * Upgrade to Doxia 2.0.0-M12
> * Upgrade to Maven Site Plugin 3.20.0
> * Upgrade to Maven Project Info Reports Plugin 3.7.0
> * Upgrade to Maven JXR Plugin 3.4.0
> * Upgrade to Maven Reporting Impl 4.0.0-M15
> Also, for consistency reasons the parameter {{includeXmlInSite}} will be
> renamed to {{includeXmlInReports}} to better reflect that this plugin does
> not only run in site mode, but also in standalone mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-389) Upgrade to Doxia 2.0.0 Milestone Stack
[
https://issues.apache.org/jira/browse/MPMD-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-389.
---
Resolution: Fixed
Fixed with
[c31b29af9835652db9ab0b9e919c8e14bc4efabf|https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=c31b29af9835652db9ab0b9e919c8e14bc4efabf].
> Upgrade to Doxia 2.0.0 Milestone Stack
> --
>
> Key: MPMD-389
> URL: https://issues.apache.org/jira/browse/MPMD-389
> Project: Maven PMD Plugin
> Issue Type: Dependency upgrade
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.25.0
>
>
> * Upgrade to Doxia 2.0.0-M12
> * Upgrade to Maven Site Plugin 3.20.0
> * Upgrade to Maven Project Info Reports Plugin 3.7.0
> * Upgrade to Maven JXR Plugin 3.4.0
> * Upgrade to Maven Reporting Impl 4.0.0-M15
> Also, for consistency reasons the parameter {{includeXmlInSite}} will be
> renamed to {{includeXmlInReports}} to better reflect that this plugin does
> not only run in site mode, but also in standalone mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-390) Dynamically calculate xrefLocation/xrefTestLocation
[ https://issues.apache.org/jira/browse/MPMD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-390. --- Resolution: Fixed Fixed with [249824077aef91372a323f69bb3b060ec44679ce|https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=249824077aef91372a323f69bb3b060ec44679ce]. > Dynamically calculate xrefLocation/xrefTestLocation > --- > > Key: MPMD-390 > URL: https://issues.apache.org/jira/browse/MPMD-390 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.21.2 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.25.0 > > > After MSHARED-1327 we need to dynamically calculate where (Test) XRef report > resides. Unless an explicit value has been provided. > The calculation considers both standalone mode *and* site mode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-368) Parameter 'localRepository' is deprecated
[
https://issues.apache.org/jira/browse/MPMD-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-368.
---
Resolution: Fixed
Fixed required issue.
> Parameter 'localRepository' is deprecated
> -
>
> Key: MPMD-368
> URL: https://issues.apache.org/jira/browse/MPMD-368
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.20.0, 3.21.0
>Reporter: Elliotte Rusty Harold
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.25.0
>
>
> Probably since Maven 3.9.1 this warning is seen in builds:
> [WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to '${repositorySystemSession}' expression and get LRM from it instead.
> This broke the CI and has been worked around (MPMD-367) but the root cause
> should be addressed. This same issue might appear in other plugins as well
> and break their CIs that check to see there are no warnings in a build.
> I'm not sure whether this can be fixed without breaking compatibility with
> older Maven versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJAVADOC-784] Upgrade to Doxia 2.0.0 Milestone Stack [maven-javadoc-plugin]
asfgit closed pull request #204: [MJAVADOC-784] Upgrade to Doxia 2.0.0 Milestone Stack URL: https://github.com/apache/maven-javadoc-plugin/pull/204 -- 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] [MJAVADOC-784] Upgrade to Doxia 2.0.0 Milestone Stack [maven-javadoc-plugin]
asfgit merged PR #204: URL: https://github.com/apache/maven-javadoc-plugin/pull/204 -- 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] (MJAVADOC-784) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MJAVADOC-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875631#comment-17875631 ] ASF GitHub Bot commented on MJAVADOC-784: - asfgit merged PR #204: URL: https://github.com/apache/maven-javadoc-plugin/pull/204 > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MJAVADOC-784 > URL: https://issues.apache.org/jira/browse/MJAVADOC-784 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.10.0 > > > * Ugprade to Doxia 2.0.0-M12 > * Ugprade to Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Plugin Tools 3.14.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJAVADOC-785) Align plugin implementation with AbstractMavenReport (maven-reporting-impl)
[
https://issues.apache.org/jira/browse/MJAVADOC-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-785.
---
Resolution: Fixed
Fixed with
[9638a6a76c6db53c3bf8ffbd5cec7318b0e25303|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=9638a6a76c6db53c3bf8ffbd5cec7318b0e25303].
> Align plugin implementation with AbstractMavenReport (maven-reporting-impl)
> ---
>
> Key: MJAVADOC-785
> URL: https://issues.apache.org/jira/browse/MJAVADOC-785
> Project: Maven Javadoc Plugin
> Issue Type: Task
> Components: javadoc
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.0
>
>
> Due to its complex nature this plugin has never used {{AbstractMavenReport}},
> thus not its behavior as well. This causes inconsistencies compared with our
> other plugins in configuration and runtime behavior. After MSHARED-1327 this
> plugin will be logically aligned with maven-reporting-impl to mimic the
> behavior to the extent necessary from {{AbstractMavenReport}}.
> This change the following parameters:
> * {{outputDirectory}} uses the semantics from {{AbstractMavenReport}} and is
> not exlusive anymore
> * {{destDir}} is gone and folded into {{outputDirectory}}
> * {{reportOutputDirectory}}/{{reportTestOutputDirectory}} is gone and is
> private according to {{AbstractMavenReport}}, it will be calculated at runtime
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-784) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MJAVADOC-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875630#comment-17875630 ] ASF GitHub Bot commented on MJAVADOC-784: - asfgit closed pull request #204: [MJAVADOC-784] Upgrade to Doxia 2.0.0 Milestone Stack URL: https://github.com/apache/maven-javadoc-plugin/pull/204 > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MJAVADOC-784 > URL: https://issues.apache.org/jira/browse/MJAVADOC-784 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.10.0 > > > * Ugprade to Doxia 2.0.0-M12 > * Ugprade to Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Plugin Tools 3.14.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJAVADOC-784) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MJAVADOC-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-784. --- Resolution: Fixed Fixed with [9d339255f160d259a64189d31ab4325f1d3fae4e|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=9d339255f160d259a64189d31ab4325f1d3fae4e]. > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MJAVADOC-784 > URL: https://issues.apache.org/jira/browse/MJAVADOC-784 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.10.0 > > > * Ugprade to Doxia 2.0.0-M12 > * Ugprade to Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Plugin Tools 3.14.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJAVADOC-776) Plugin depends on plexus-container-default, which is EOL
[ https://issues.apache.org/jira/browse/MJAVADOC-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-776. --- Resolution: Fixed Fixed. > Plugin depends on plexus-container-default, which is EOL > > > Key: MJAVADOC-776 > URL: https://issues.apache.org/jira/browse/MJAVADOC-776 > Project: Maven Javadoc Plugin > Issue Type: Task >Reporter: Hua Zhang >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.10.0 > > > [WARNING] * org.apache.maven.plugins:maven-javadoc-plugin:3.6.0 > ... > [WARNING] Plugin issue(s): > [WARNING] * Plugin depends on plexus-container-default, which is EOL -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJAVADOC-560) Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc documentation
[
https://issues.apache.org/jira/browse/MJAVADOC-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-560.
---
Resolution: Fixed
This has been now cleaned up and aligned with other reporting plugins.
> Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc
> documentation
> ---
>
> Key: MJAVADOC-560
> URL: https://issues.apache.org/jira/browse/MJAVADOC-560
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.1.0
>Reporter: Gili
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.0
>
>
> Looking at the documentation for javadoc:javadoc at
> [https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html] I
> see three problems:
> # The documentation lists both *outputDirectory* and *reportOutputDirectory*
> parameters, having the same description. It's not clear what each one is used
> for or what happens if one property is changed without the other.
> # The default value of *outputDirectory* is listed as
> *${project.build.directory}/apidocs* but the value that is actually used is
> *${project.reporting.outputDirectory}/apidocs* (the value of
> *reportOutputDirectory*).
> # It was extremely difficult to find any documentation on
> *${project.reporting.outputDirectory}***, such as what its default value is.
> I eventually found [https://maven.apache.org/pom.html#Reporting] but Google
> does not link directly to this page/section because it doesn't contain an
> explicit reference to *${project.reporting}*.
> Suggested fix(es):
> # Drop one of the two parameters, ideally *reportOutputDirectory*, to avoid
> confusion.
> # Update the documentation so it lists the correct default value for
> *outputDirectory*.
> # Link directly from mention of *${project.reporting.outputDirectory}* to
> [https://maven.apache.org/pom.html#Reporting]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MPLUGIN-501] Upgrade to Doxia 2.0.0 Milestone Stack [maven-plugin-tools]
asfgit closed pull request #212: [MPLUGIN-501] Upgrade to Doxia 2.0.0 Milestone Stack URL: https://github.com/apache/maven-plugin-tools/pull/212 -- 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-501) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MPLUGIN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875637#comment-17875637 ] ASF GitHub Bot commented on MPLUGIN-501: asfgit closed pull request #212: [MPLUGIN-501] Upgrade to Doxia 2.0.0 Milestone Stack URL: https://github.com/apache/maven-plugin-tools/pull/212 > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MPLUGIN-501 > URL: https://issues.apache.org/jira/browse/MPLUGIN-501 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-2, 3.15.0 > > > * Upgrade to Doxia 2.0.0-M12 > * Upgrade to Commons Lang 3.16.0 > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 > * Upgrade to Plexus Velocity 2.1.0 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Reporting Impl 4.0.0-M15 > * Upgrade to Velocity Engine 2.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.commons:commons-lang3 from 3.8.1 to 3.16.0 [maven-plugin-tools]
dependabot[bot] commented on PR #315: URL: https://github.com/apache/maven-plugin-tools/pull/315#issuecomment-2302916215 Looks like org.apache.commons:commons-lang3 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 org.apache.commons:commons-lang3 from 3.8.1 to 3.16.0 [maven-plugin-tools]
dependabot[bot] closed pull request #315: Bump org.apache.commons:commons-lang3 from 3.8.1 to 3.16.0 URL: https://github.com/apache/maven-plugin-tools/pull/315 -- 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] [MPLUGIN-501] Upgrade to Doxia 2.0.0 Milestone Stack (Maven 3.x) [maven-plugin-tools]
asfgit merged PR #297: URL: https://github.com/apache/maven-plugin-tools/pull/297 -- 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] (MPLUGIN-501) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MPLUGIN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPLUGIN-501. -- Resolution: Fixed Fixed with [df699db7253ae623c2cb76fd7d308e54a81e7640|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git;a=commit;h=df699db7253ae623c2cb76fd7d308e54a81e7640] and with [663511476a041b2067b47d5b37e19baefab7cc2e|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git;a=commit;h=663511476a041b2067b47d5b37e19baefab7cc2e]. for 3.x > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MPLUGIN-501 > URL: https://issues.apache.org/jira/browse/MPLUGIN-501 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-2, 3.15.0 > > > * Upgrade to Doxia 2.0.0-M12 > * Upgrade to Commons Lang 3.16.0 > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 > * Upgrade to Plexus Velocity 2.1.0 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Reporting Impl 4.0.0-M15 > * Upgrade to Velocity Engine 2.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-501) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MPLUGIN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875638#comment-17875638 ] ASF GitHub Bot commented on MPLUGIN-501: asfgit merged PR #297: URL: https://github.com/apache/maven-plugin-tools/pull/297 > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MPLUGIN-501 > URL: https://issues.apache.org/jira/browse/MPLUGIN-501 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-2, 3.15.0 > > > * Upgrade to Doxia 2.0.0-M12 > * Upgrade to Commons Lang 3.16.0 > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 > * Upgrade to Plexus Velocity 2.1.0 > * Upgrade to Maven Reporting API 4.0.0-M12 > * Upgrade to Maven Reporting Impl 4.0.0-M15 > * Upgrade to Velocity Engine 2.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
