[jira] [Commented] (MPH-160) help:effective-pom -Dverbose: add source location as comments in effective pom.xml
[
https://issues.apache.org/jira/browse/MPH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465565#comment-17465565
]
abccbaandy commented on MPH-160:
I think this feature is good but not enough.
In my situation, I know the version come from, but what's next?
I don't know how can I find the definition, especially I have complex pom
inherit structure.
> help:effective-pom -Dverbose: add source location as comments in effective
> pom.xml
> --
>
> Key: MPH-160
> URL: https://issues.apache.org/jira/browse/MPH-160
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: effective-pom
>Affects Versions: 3.1.0
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> during in-memory effective pom building (by maven-model-builder), the source
> location of content is kept in memory: see [Modello documentation on location
> tracking|https://codehaus-plexus.github.io/modello/location-tracking.html]
> and MNG-1803 for its integration into Maven model
> adding this information as comment on every line of generated XML would ease
> tracking for end users (and not only m2e users, who get "Jump to location"
> hint when editing their pom.xml in Eclipse...)
> This will require a Modello enhancement (see [Modello
> #28|https://github.com/codehaus-plexus/modello/issues/28]) then integration
> (idea found during [Devoxx 2018 Maven
> BoF|https://dvbe18.confinabox.com/talk/EVC-1727/Apache_Maven_BOF], since
> users were missing ways to diagnose unexpected result in effective pom)
> Sample result is the addition of comments with modelId and "line xxx" at the
> end of each line of generated XML:
> {code:xml}$ mvn -Dverbose
> org.apache.maven.plugins:maven-help-plugin:3.1.2-SNAPSHOT:effective-pom
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< org.apache.maven.plugins:maven-help-plugin
> >-
> [INFO] Building Apache Maven Help Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-help-plugin:3.1.2-SNAPSHOT:effective-pom (default-cli) @
> maven-help-plugin ---
> [INFO]
> Effective POMs, after inheritance, interpolation, and profiles are applied:
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
>
> maven-plugins
> org.apache.maven.plugins
> 33
> ../../pom/maven/maven-plugins/pom.xml
>
> org.apache.maven.plugins
> maven-help-plugin
> 3.1.2-SNAPSHOT
> maven-plugin
> Apache Maven Help Plugin
> The Maven Help plugin provides goals aimed at helping to make
> sense out of
> the build environment. It includes the ability to view the effective
> POM and settings files, after inheritance and active profiles
> have been applied, as well as a describe a particular plugin goal to give
> usage information.
> https://maven.apache.org/plugins/maven-help-plugin/
> 2001
>
> The Apache Software Foundation
> https://www.apache.org/
>
>
>
> Apache License, Version 2.0
> https://www.apache.org/licenses/LICENSE-2.0.txt
> repo
>
>
> ...{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-mvnd] coderYii removed a comment on issue #544: jdk 1.8 exception
coderYii removed a comment on issue #544: URL: https://github.com/apache/maven-mvnd/issues/544#issuecomment-1001358176 [Build mvnd](https://github.com/apache/maven-mvnd#build-mvnd) -- 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
[GitHub] [maven-mvnd] lihao0324 removed a comment on issue #415: Cannot connect to private repositories
lihao0324 removed a comment on issue #415: URL: https://github.com/apache/maven-mvnd/issues/415#issuecomment-1001382857 > Maybe using some docker image based on Apache Archiva could help setting up an integration test / reproducer ? This is a serious bug, half of the jars in our project are in self-service, this will cause the build to fail, please look into this issue, thank you. -- 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
[GitHub] [maven-mvnd] lihao0324 commented on issue #415: Cannot connect to private repositories
lihao0324 commented on issue #415: URL: https://github.com/apache/maven-mvnd/issues/415#issuecomment-1001382857 > Maybe using some docker image based on Apache Archiva could help setting up an integration test / reproducer ? This is a serious bug, half of the jars in our project are in self-service, this will cause the build to fail, please look into this issue, thank you. -- 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
[GitHub] [maven-mvnd] coderYii commented on issue #544: jdk 1.8 exception
coderYii commented on issue #544: URL: https://github.com/apache/maven-mvnd/issues/544#issuecomment-1001358176 [Build mvnd](https://github.com/apache/maven-mvnd#build-mvnd) -- 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
[GitHub] [maven-surefire] dependabot[bot] opened a new pull request #416: Bump plexus-java from 1.0.7 to 1.1.0
dependabot[bot] opened a new pull request #416: URL: https://github.com/apache/maven-surefire/pull/416 Bumps [plexus-java](https://github.com/codehaus-plexus/plexus-languages) from 1.0.7 to 1.1.0. Commits https://github.com/codehaus-plexus/plexus-languages/commit/abcd162ed3edadda409bc8bb4f2707d52a3a8551";>abcd162 [maven-release-plugin] prepare release plexus-languages-1.1.0 https://github.com/codehaus-plexus/plexus-languages/commit/868b3d7439634c35d05cfc6aa8a012adb070d02d";>868b3d7 Support requires static transitive https://github.com/codehaus-plexus/plexus-languages/commit/1c91b4f0a8efe10bcba20d45697bfe42d159c8fd";>1c91b4f Bump maven-enforcer-plugin from 3.0.0-M3 to 3.0.0 https://github.com/codehaus-plexus/plexus-languages/commit/5bfae5f0a49ec8fdd630946c124a090d6217cdfb";>5bfae5f Bump plexus from 7 to 8 https://github.com/codehaus-plexus/plexus-languages/commit/cee4f63c15ac6ea8b3d71093716c5da99a89804d";>cee4f63 Require Java 8 https://github.com/codehaus-plexus/plexus-languages/commit/34731971454cbc8a22f9e9e03d42343cbba92714";>3473197 Update CI setup https://github.com/codehaus-plexus/plexus-languages/commit/5cadf50f10b9c19a497c38c2cb842762b450cd6a";>5cadf50 Removed outdated java versions from CI https://github.com/codehaus-plexus/plexus-languages/commit/b8baee463de716f55e5a01dc09754563d91e79b0";>b8baee4 Bump actions/setup-java from 2.1.0 to 2.2.0 https://github.com/codehaus-plexus/plexus-languages/commit/7cd361b8f52451afef11947dd493f4518c7c65fc";>7cd361b Bump mockito-core from 3.11.2 to 3.12.1 https://github.com/codehaus-plexus/plexus-languages/commit/c9c9cfe1532c4e551faea559295b5d253a8353ec";>c9c9cfe update search.maven.org url Additional commits viewable in https://github.com/codehaus-plexus/plexus-languages/compare/plexus-languages-1.0.7...plexus-languages-1.1.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 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
[GitHub] [maven-indexer] dependabot[bot] opened a new pull request #152: Bump logback-classic from 1.2.7 to 1.2.10
dependabot[bot] opened a new pull request #152: URL: https://github.com/apache/maven-indexer/pull/152 Bumps logback-classic from 1.2.7 to 1.2.10. [](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 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
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #103: Bump commons-collections from 3.2.1 to 3.2.2
dependabot[bot] opened a new pull request #103: URL: https://github.com/apache/maven-archetype/pull/103 Bumps commons-collections from 3.2.1 to 3.2.2. [](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 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
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #100: Bump mavenVersion from 3.0 to 3.8.4
dependabot[bot] opened a new pull request #100: URL: https://github.com/apache/maven-archetype/pull/100 Bumps `mavenVersion` from 3.0 to 3.8.4. Updates `maven-compat` from 3.0 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.0...maven-3.8.4";>compare view Updates `maven-artifact` from 3.0 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.0...maven-3.8.4";>compare view Updates `maven-core` from 3.0 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #102: Bump maven-script-interpreter from 1.2 to 1.3
dependabot[bot] opened a new pull request #102: URL: https://github.com/apache/maven-archetype/pull/102 Bumps [maven-script-interpreter](https://github.com/apache/maven-script-interpreter) from 1.2 to 1.3. Commits https://github.com/apache/maven-script-interpreter/commit/2aa327f40927248f6148d2ba5bf96e7a687935b7";>2aa327f [maven-release-plugin] prepare release maven-script-interpreter-1.3 https://github.com/apache/maven-script-interpreter/commit/0ea9cd6d8cf6e5c00c88f68f6026c9d9bdfa5569";>0ea9cd6 Merge pull request https://github-redirect.dependabot.com/apache/maven-script-interpreter/issues/31";>#31 from apache/dependabot/github_actions/actions/cache-v2... https://github.com/apache/maven-script-interpreter/commit/f35b40b18d211c5d8f7db5817e8bdccda70c34fb";>f35b40b Merge pull request https://github-redirect.dependabot.com/apache/maven-script-interpreter/issues/30";>#30 from apache/dependabot/maven/junit-junit-4.13.1 https://github.com/apache/maven-script-interpreter/commit/194760e38dc40247904530deabe1ae15852b82dd";>194760e Bump actions/cache from v2.1.1 to v2.1.2 https://github.com/apache/maven-script-interpreter/commit/ab4de26ef1e61c7bcf07e0b45c812dd5e1c19ea2";>ab4de26 Bump junit from 4.13 to 4.13.1 https://github.com/apache/maven-script-interpreter/commit/ed02d197695a9a856a9a4c7b1e3e5223817617f1";>ed02d19 Use maven-fluido-skin 1.9 https://github.com/apache/maven-script-interpreter/commit/70edebbcf85be0457388d5553532128435d6e3ce";>70edebb [MSHARED-961] Upgrde to BeanShell 2.0b6 https://github.com/apache/maven-script-interpreter/commit/237a68c62cd0f1435a99ea9ba14893aefec3b97d";>237a68c Javadoc fixes https://github.com/apache/maven-script-interpreter/commit/ac94b27807bfd7422925f382e21493b6a7c30383";>ac94b27 Update plugins to latest versions https://github.com/apache/maven-script-interpreter/commit/9c6c18dd0d3369c0ed1c24f9ff77be2f2c020af4";>9c6c18d Run Github CI with Java 15 Additional commits viewable in https://github.com/apache/maven-script-interpreter/compare/maven-script-interpreter-1.2...maven-script-interpreter-1.3";>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 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
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #101: Bump groovy-all from 2.4.16 to 2.4.21
dependabot[bot] opened a new pull request #101: URL: https://github.com/apache/maven-archetype/pull/101 Bumps [groovy-all](https://github.com/apache/groovy) from 2.4.16 to 2.4.21. Commits See full diff in https://github.com/apache/groovy/commits";>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 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
[GitHub] [maven-archetype] dependabot[bot] closed pull request #98: Bump wagonVersion from 3.3.3 to 3.5.0
dependabot[bot] closed pull request #98: URL: https://github.com/apache/maven-archetype/pull/98 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #99: Bump wagonVersion from 3.3.3 to 3.5.1
dependabot[bot] opened a new pull request #99: URL: https://github.com/apache/maven-archetype/pull/99 Bumps `wagonVersion` from 3.3.3 to 3.5.1. Updates `wagon-provider-api` from 3.3.3 to 3.5.1 Commits https://github.com/apache/maven-wagon/commit/a40b7196f72f23a68b765c0a9a3c6984edbc221d";>a40b719 [maven-release-plugin] prepare release wagon-3.5.1 https://github.com/apache/maven-wagon/commit/fd2ae925fab62da455df61d915126cee13a1d31b";>fd2ae92 [WAGON-623] Upgrade HttpCore to 4.4.15 https://github.com/apache/maven-wagon/commit/c9aa4c51fd256b4a949c658aabbdcc057bcc253e";>c9aa4c5 [WAGON-622] Upgrade Plexus Interactivity to 1.1 https://github.com/apache/maven-wagon/commit/3b5f142b7054962cd28b91cc9f3e2cf94e24f4f8";>3b5f142 [WAGON-621] Upgrade JUnit to 4.13.2 https://github.com/apache/maven-wagon/commit/90a952d6ab4ba676128a377aba13f0af88d26896";>90a952d [WAGON-620] Upgrade SLF4J to 1.7.32 https://github.com/apache/maven-wagon/commit/561fe11029c1aa6199d1658259f85c4bca6b0eac";>561fe11 [WAGON-619] Remove shading of JSoup https://github.com/apache/maven-wagon/commit/efbee57381490b1b93b587212022fcf769a1b209";>efbee57 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-wagon/commit/59c3cbbcf53d43689c6bfaeb897a764aa39f7832";>59c3cbb [maven-release-plugin] prepare release wagon-3.5.0 https://github.com/apache/maven-wagon/commit/f23b6a350e1f1e6d90a539429a88ebaeb069df8d";>f23b6a3 [WAGON-618] Remove HTTP file listing with JSoup https://github.com/apache/maven-wagon/commit/bd44727b8c86ee10f783adab3c0d100a8ba1a8ea";>bd44727 Add grant deprecation notice Additional commits viewable in https://github.com/apache/maven-wagon/compare/wagon-3.3.3...wagon-3.5.1";>compare view Updates `wagon-http` from 3.3.3 to 3.5.1 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 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
[GitHub] [maven-archetype] dependabot[bot] commented on pull request #98: Bump wagonVersion from 3.3.3 to 3.5.0
dependabot[bot] commented on pull request #98: URL: https://github.com/apache/maven-archetype/pull/98#issuecomment-1001327958 Superseded by #99. -- 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
[GitHub] [maven-help-plugin] dependabot[bot] opened a new pull request #43: Bump maven-site-plugin from 3.9.1 to 3.10.0
dependabot[bot] opened a new pull request #43: URL: https://github.com/apache/maven-help-plugin/pull/43 Bumps [maven-site-plugin](https://github.com/apache/maven-site-plugin) from 3.9.1 to 3.10.0. Commits https://github.com/apache/maven-site-plugin/commit/c56b7b2ad2baecbf4286151c645ff4ee9190f420";>c56b7b2 [maven-release-plugin] prepare release maven-site-plugin-3.10.0 https://github.com/apache/maven-site-plugin/commit/7029bab59cac4fe83b62c245e55c37bcb79d9061";>7029bab [MSITE-878] Upgrade Doxia to 1.11.1 and Doxia Tools to 1.11.1 https://github.com/apache/maven-site-plugin/commit/7f8fe7ead4e42b7797eed7eb87c878a16e10b5be";>7f8fe7e [MSITE-877] Shared GitHub Actions (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/65";>#65) https://github.com/apache/maven-site-plugin/commit/e3302845bd4fac62e7869d1afd0faadd0499becc";>e330284 require CDATA https://github.com/apache/maven-site-plugin/commit/eeba50cf6854c9cca709ae47a626d57d924e463e";>eeba50c Add PR template https://github.com/apache/maven-site-plugin/commit/7813e8f193131faec8898b54b0e59c82602ab665";>7813e8f add Sitetools' integration tool and skin model https://github.com/apache/maven-site-plugin/commit/fda2a84b09a6d08ceb26efee963f00a21e02ffc2";>fda2a84 Updated CI setup https://github.com/apache/maven-site-plugin/commit/0cd2070cf4e32086fe936ea09c5f80c7d5a988cb";>0cd2070 Bump slf4jVersion from 1.7.31 to 1.7.32 (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/58";>#58) https://github.com/apache/maven-site-plugin/commit/9f24d2bd21f3d7a741ea74b4f41aa42ee02ce625";>9f24d2b update CI url https://github.com/apache/maven-site-plugin/commit/e06aa7822797f6ee54ee4dd309d955c3822df801";>e06aa78 [MSITE-875] add 3.10.0 in history table Additional commits viewable in https://github.com/apache/maven-site-plugin/compare/maven-site-plugin-3.9.1...maven-site-plugin-3.10.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 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
[GitHub] [maven-help-plugin] dependabot[bot] opened a new pull request #42: Bump mavenVersion from 3.1.1 to 3.8.4
dependabot[bot] opened a new pull request #42: URL: https://github.com/apache/maven-help-plugin/pull/42 Bumps `mavenVersion` from 3.1.1 to 3.8.4. Updates `maven-artifact` from 3.1.1 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.1.1...maven-3.8.4";>compare view Updates `maven-core` from 3.1.1 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.1.1...maven-3.8.4";>compare view Updates `maven-plugin-api` from 3.1.1 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Add
[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request #89: Bump mockito-core from 4.1.0 to 4.2.0
dependabot[bot] opened a new pull request #89: URL: https://github.com/apache/maven-invoker-plugin/pull/89 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.1.0 to 4.2.0. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.2.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.2.0 2021-12-16 - https://github.com/mockito/mockito/compare/v4.1.0...v4.2.0";>21 commit(s) by Liam Miller-Cushon, Rafael Winterhalter, Tim van der Lippe, dependabot[bot], temp-droid Update ByteBuddy to 1.12.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2515";>#2515)](https://github-redirect.dependabot.com/mockito/mockito/pull/2515";>mockito/mockito#2515) Bump kotlinVersion from 1.6.0 to 1.6.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2514";>#2514)](https://github-redirect.dependabot.com/mockito/mockito/pull/2514";>mockito/mockito#2514) Add DoNotMock mention to main JavaDoc [(https://github-redirect.dependabot.com/mockito/mockito/issues/2512";>#2512)](https://github-redirect.dependabot.com/mockito/mockito/pull/2512";>mockito/mockito#2512) Replace ExpectedException in MissingInvocationInOrderCheckerTest [(https://github-redirect.dependabot.com/mockito/mockito/issues/2511";>#2511)](https://github-redirect.dependabot.com/mockito/mockito/pull/2511";>mockito/mockito#2511) Update Gradle to version 7.3.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2509";>#2509)](https://github-redirect.dependabot.com/mockito/mockito/pull/2509";>mockito/mockito#2509) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2497";>#2497: Throw exception on invalid matchers for mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2506";>#2506)](https://github-redirect.dependabot.com/mockito/mockito/pull/2506";>mockito/mockito#2506) Make sure interface types are initialized before inline mocking to avoid blocking code of static initializers. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2505";>#2505)](https://github-redirect.dependabot.com/mockito/mockito/pull/2505";>mockito/mockito#2505) Bump org.eclipse.osgi from 3.17.0 to 3.17.100 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2504";>#2504)](https://github-redirect.dependabot.com/mockito/mockito/pull/2504";>mockito/mockito#2504) Bump com.diffplug.spotless from 6.0.2 to 6.0.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2501";>#2501)](https://github-redirect.dependabot.com/mockito/mockito/pull/2501";>mockito/mockito#2501) Bump com.diffplug.spotless from 6.0.1 to 6.0.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2498";>#2498)](https://github-redirect.dependabot.com/mockito/mockito/pull/2498";>mockito/mockito#2498) ArgumentMatchers not working for Mockito.mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2497";>#2497)](https://github-redirect.dependabot.com/mockito/mockito/issues/2497";>mockito/mockito#2497) Bump versions.bytebuddy from 1.12.2 to 1.12.3 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2496";>#2496)](https://github-redirect.dependabot.com/mockito/mockito/pull/2496";>mockito/mockito#2496) Bump com.diffplug.spotless from 6.0.0 to 6.0.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2495";>#2495)](https://github-redirect.dependabot.com/mockito/mockito/pull/2495";>mockito/mockito#2495) Remove the recommendation to import ArgumentMatchers methods using Mockito [(https://github-redirect.dependabot.com/mockito/mockito/issues/2494";>#2494)](https://github-redirect.dependabot.com/mockito/mockito/pull/2494";>mockito/mockito#2494) Bump versions.junitJupiter from 5.8.1 to 5.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2491";>#2491)](https://github-redirect.dependabot.com/mockito/mockito/pull/2491";>mockito/mockito#2491) Bump junit-platform-launcher from 1.8.1 to 1.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2490";>#2490)](https://github-redirect.dependabot.com/mockito/mockito/pull/2490";>mockito/mockito#2490) Fix typo 'DoNoMock' should be 'DoNotMock' [(https://github-redirect.dependabot.com/mockito/mockito/issues/2487";>#2487)](https://github-redirect.dependabot.com/mockito/mockito/pull/2487";>mockito/mockito#2487) Bump biz.aQute.bnd.gradle from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2486";>#2486)](https://github-redirect.dependabot.com/mockito/mockito/pull/2486";>mockito/mockito#2486) Bump biz.aQute.bnd.builder from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2485";>#2485)](https://github-redirect.dependabot.com/mockito/mockito/pull/2485";>mockito/mockito#2485) Bump versions.bytebuddy from 1.12.1 to 1.12.2 [(https://github-redirect.dependabot.com/m
[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request #88: Bump maven-site-plugin from 3.9.1 to 3.10.0
dependabot[bot] opened a new pull request #88: URL: https://github.com/apache/maven-invoker-plugin/pull/88 Bumps [maven-site-plugin](https://github.com/apache/maven-site-plugin) from 3.9.1 to 3.10.0. Commits https://github.com/apache/maven-site-plugin/commit/c56b7b2ad2baecbf4286151c645ff4ee9190f420";>c56b7b2 [maven-release-plugin] prepare release maven-site-plugin-3.10.0 https://github.com/apache/maven-site-plugin/commit/7029bab59cac4fe83b62c245e55c37bcb79d9061";>7029bab [MSITE-878] Upgrade Doxia to 1.11.1 and Doxia Tools to 1.11.1 https://github.com/apache/maven-site-plugin/commit/7f8fe7ead4e42b7797eed7eb87c878a16e10b5be";>7f8fe7e [MSITE-877] Shared GitHub Actions (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/65";>#65) https://github.com/apache/maven-site-plugin/commit/e3302845bd4fac62e7869d1afd0faadd0499becc";>e330284 require CDATA https://github.com/apache/maven-site-plugin/commit/eeba50cf6854c9cca709ae47a626d57d924e463e";>eeba50c Add PR template https://github.com/apache/maven-site-plugin/commit/7813e8f193131faec8898b54b0e59c82602ab665";>7813e8f add Sitetools' integration tool and skin model https://github.com/apache/maven-site-plugin/commit/fda2a84b09a6d08ceb26efee963f00a21e02ffc2";>fda2a84 Updated CI setup https://github.com/apache/maven-site-plugin/commit/0cd2070cf4e32086fe936ea09c5f80c7d5a988cb";>0cd2070 Bump slf4jVersion from 1.7.31 to 1.7.32 (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/58";>#58) https://github.com/apache/maven-site-plugin/commit/9f24d2bd21f3d7a741ea74b4f41aa42ee02ce625";>9f24d2b update CI url https://github.com/apache/maven-site-plugin/commit/e06aa7822797f6ee54ee4dd309d955c3822df801";>e06aa78 [MSITE-875] add 3.10.0 in history table Additional commits viewable in https://github.com/apache/maven-site-plugin/compare/maven-site-plugin-3.9.1...maven-site-plugin-3.10.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 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
[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request #87: Bump assertj-core from 3.20.2 to 3.21.0
dependabot[bot] opened a new pull request #87: URL: https://github.com/apache/maven-invoker-plugin/pull/87 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.20.2 to 3.21.0. Commits https://github.com/assertj/assertj-core/commit/8f8b742a20885a14e8b1af9418e7f219f084738e";>8f8b742 [maven-release-plugin] prepare release assertj-core-3.21.0 https://github.com/assertj/assertj-core/commit/a7ef096951d363d3bc5eb72d38685d77c70acbf5";>a7ef096 Add hasNoExtension to File assertions. https://github.com/assertj/assertj-core/commit/5bef9b2915334eebc419ea4b45e20236918c6077";>5bef9b2 Bump byte-buddy.version from 1.11.15 to 1.11.16 https://github.com/assertj/assertj-core/commit/931b5920e9a1eaa93dd7fd30885db3f7a4d22cdf";>931b592 Add hasNoExtension to Path assertions https://github.com/assertj/assertj-core/commit/cd2ce8251adac65884460c0f2db0e56adcc1d9ae";>cd2ce82 Javadoc improvements https://github.com/assertj/assertj-core/commit/daf13ee9e651ddfc58ea48d76f488e1ff2350103";>daf13ee Add additional tests for Path assertions https://github.com/assertj/assertj-core/commit/620ec2983e15e3d15ab05e15605ba81789d62892";>620ec29 Bump org.eclipse.osgi from 3.16.300 to 3.17.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2343";>#2343) https://github.com/assertj/assertj-core/commit/a0e7214c866252ac390aff6f48f0c2b7a4536051";>a0e7214 Bump spring-core from 5.3.9 to 5.3.10 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2344";>#2344) https://github.com/assertj/assertj-core/commit/9e5161f5ff6b271bda2e1e387d3b22f762f8ec82";>9e5161f Use Java 17 GA, remove EOL Java 16 https://github.com/assertj/assertj-core/commit/48ed152ca335612fffb7182646cbe2c13a026806";>48ed152 Path and File assertions refactoring Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.20.2...assertj-core-3.21.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 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
[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request #86: Bump mavenVersion from 3.2.5 to 3.8.4
dependabot[bot] opened a new pull request #86: URL: https://github.com/apache/maven-invoker-plugin/pull/86 Bumps `mavenVersion` from 3.2.5 to 3.8.4. Updates `maven-core` from 3.2.5 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.2.5...maven-3.8.4";>compare view Updates `maven-model` from 3.2.5 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.2.5...maven-3.8.4";>compare view Updates `maven-plugin-api` from 3.2.5 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Add
[GitHub] [maven-doxia-converter] dependabot[bot] opened a new pull request #22: Bump plexus-container-default from 2.1.0 to 2.1.1
dependabot[bot] opened a new pull request #22: URL: https://github.com/apache/maven-doxia-converter/pull/22 Bumps [plexus-container-default](https://github.com/codehaus-plexus/plexus-containers) from 2.1.0 to 2.1.1. Release notes Sourced from https://github.com/codehaus-plexus/plexus-containers/releases";>plexus-container-default's releases. 2.1.1 Plexus Containers 2.1.1 requires Java 7 and Maven 3.2.5+ Upgrade ASM to 9.2 [Snyk] Security upgrade org.jdom:jdom2 from 2.0.6 to 2.0.6.1 by https://github.com/snyk-bot";>@snyk-bot Changelog Sourced from https://github.com/codehaus-plexus/plexus-containers/blob/master/ReleaseNotes.md";>plexus-container-default's changelog. Plexus Containers 2.1.1 Plexus Containers 2.1.1 requires Java 7 and Maven 3.2.5+ Improvements Upgrade ASM to 9.2 Upgrade JDOM2 to 2.0.6.1 Commits https://github.com/codehaus-plexus/plexus-containers/commit/3b0a8d5fd086e3f74ccdeecaac9cd63e44047e91";>3b0a8d5 [maven-release-plugin] prepare release plexus-containers-2.1.1 https://github.com/codehaus-plexus/plexus-containers/commit/2f4800dcfdcd1177341cb7682792e30be2c7ec60";>2f4800d Fix issues with release https://github.com/codehaus-plexus/plexus-containers/commit/e4878028b3104d45cd5c6e91fce07dd08f06f2b3";>e487802 Add release notes for 2.1.1 https://github.com/codehaus-plexus/plexus-containers/commit/85e7f402fbf7e2527736cd0654c9ce905a57c6dd";>85e7f40 Fix build errors https://github.com/codehaus-plexus/plexus-containers/commit/31f3f0ab782154d088354ea1029ef0b0f716356f";>31f3f0a Restore Java 7 compatibility https://github.com/codehaus-plexus/plexus-containers/commit/ff15fcf0384913301e46a05cb28facfb6287ce88";>ff15fcf Bump ASM to 9.2 https://github.com/codehaus-plexus/plexus-containers/commit/7da2a9884382635fe41ecf66049ef70224fb9340";>7da2a98 Require Maven 3.2.5 https://github.com/codehaus-plexus/plexus-containers/commit/977d99324e5fb94968a601284592675803bfe954";>977d993 Require Java 8 https://github.com/codehaus-plexus/plexus-containers/commit/5d49068f1d2f962fb27096aa79aa3a7dea623fe4";>5d49068 Bump plexus from 5.1 to 8 https://github.com/codehaus-plexus/plexus-containers/commit/4f0743cc70f0eedc1bcd64d043d41cda77343eed";>4f0743c Bump qdox from 2.0-M10 to 2.0.1 Additional commits viewable in https://github.com/codehaus-plexus/plexus-containers/compare/plexus-containers-2.1.0...plexus-containers-2.1.1";>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 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
[GitHub] [maven-parent] dependabot[bot] opened a new pull request #44: Bump extra-enforcer-rules from 1.4 to 1.5.1
dependabot[bot] opened a new pull request #44: URL: https://github.com/apache/maven-parent/pull/44 Bumps [extra-enforcer-rules](https://github.com/mojohaus/extra-enforcer-rules) from 1.4 to 1.5.1. Release notes Sourced from https://github.com/mojohaus/extra-enforcer-rules/releases";>extra-enforcer-rules's releases. 1.5.1 No changes Last release has issues with oss.sonatype.org so trying again 1.5.0 Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/enforce-bytecode-version-multirelease (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/154";>#154) https://github.com/dependabot";>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-fail-when-not-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155";>#155) https://github.com/dependabot";>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-ignore-when-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156";>#156) https://github.com/dependabot";>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-jdk9 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157";>#157) https://github.com/dependabot";>@dependabot Bump mockito-core from 3.12.4 to 4.1.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/151";>#151) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 2.3.1 to 2.4.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/153";>#153) https://github.com/dependabot";>@dependabot Bump mojo-parent from 63 to 65 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/152";>#152) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 2.3.0 to 2.3.1 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/145";>#145) https://github.com/dependabot";>@dependabot 🐛 Bug Fixes Bytecode version of multirelease metadata should be lower or equal to specified version (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/158";>#158) https://github.com/Vlatombe";>@Vlatombe Commits https://github.com/mojohaus/extra-enforcer-rules/commit/da069393305d91ff1bf24fecd1725d145cf3a121";>da06939 [maven-release-plugin] prepare release extra-enforcer-rules-1.5.1 https://github.com/mojohaus/extra-enforcer-rules/commit/24c1b61b670f4ad6495762e6f86377ef783c733a";>24c1b61 [maven-release-plugin] prepare for next development iteration https://github.com/mojohaus/extra-enforcer-rules/commit/4e4e2db3df60fc8af22c877e38f27b391c6be1f8";>4e4e2db [maven-release-plugin] prepare release extra-enforcer-rules-1.5 https://github.com/mojohaus/extra-enforcer-rules/commit/5553dfc45a7cc4090b270b9bcd5d429804f8e7f4";>5553dfc fix IT test https://github.com/mojohaus/extra-enforcer-rules/commit/ecff4d7c5eae7d9e9e1f61a7cb9f43ffb06ea17c";>ecff4d7 Bump log4j-api in /src/it/enforce-bytecode-version-multirelease https://github.com/mojohaus/extra-enforcer-rules/commit/4db8e82362ebf79fd2ca373d38511c8ad0cf1cd1";>4db8e82 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155";>#155 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/b21d419d09def4665e0cc1209967e4d986ebfb13";>b21d419 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156";>#156 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/9aded1a52b48a1ca3b720e41a7a7251b2784f3ef";>9aded1a Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157";>#157 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/90ac027afa09353989f9ba1173f49fe2dcd41404";>90ac027 Bytecode version of multirelease metadata should be lower or equal to specifi... https://github.com/mojohaus/extra-enforcer-rules/commit/0cdcfacfbfaa29c5c22ad5bfb669983748f1d36d";>0cdcfac Bump log4j-api in /src/it/banduplicate-classes-jdk9 Additional commits viewable in https://github.com/mojohaus/extra-enforcer-rules/compare/extra-enforcer-rules-1.4...extra-enforcer-rules-1.5.1";>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 tri
[GitHub] [maven-doxia-converter] dependabot[bot] opened a new pull request #21: Bump doxiaVersion from 1.10 to 1.11.1
dependabot[bot] opened a new pull request #21: URL: https://github.com/apache/maven-doxia-converter/pull/21 Bumps `doxiaVersion` from 1.10 to 1.11.1. Updates `doxia-core` from 1.10 to 1.11.1 Commits https://github.com/apache/maven-doxia/commit/84c3babdeeadafb546985e00353c1dc71c770344";>84c3bab [maven-release-plugin] prepare release doxia-1.11.1 https://github.com/apache/maven-doxia/commit/88fdae390aef87d540037133177be5f85670";>88fda88 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-doxia/commit/ea9e1c6a54165daebe043067cfd0a72cba7ad91b";>ea9e1c6 [maven-release-plugin] prepare release doxia-1.11 https://github.com/apache/maven-doxia/commit/a5145159ec5d8c993612560fb2bb2ef10b3815ab";>a514515 [DOXIA-629] Deprecate SwfMacro https://github.com/apache/maven-doxia/commit/80e02c5cbf0ada390789af21235d41168ac8874a";>80e02c5 [DOXIA-628] Deprecate SsiMacro https://github.com/apache/maven-doxia/commit/21b3b82f9d74cd329258a1b137048a2205d169e6";>21b3b82 [DOXIA-620] Deprecate Doxia Logging API in favor of SLF4J https://github.com/apache/maven-doxia/commit/05d719a105d1504fe78b72cc204185968c40ee20";>05d719a [DOXIA-627] Deprecate doxia-module-twiki https://github.com/apache/maven-doxia/commit/ca9af5a8ef8298a8f21d6c5de2a3ccc53509b5b8";>ca9af5a [DOXIA-626] Deprecate doxia-module-rtf https://github.com/apache/maven-doxia/commit/37cfeda9607a3aae177171e801c180b94f733ced";>37cfeda [DOXIA-625] Deprecate doxia-module-latex https://github.com/apache/maven-doxia/commit/4df28158c8a291228b30a1bbb2506b7421a6a9fd";>4df2815 [DOXIA-624] Deprecate doxia-module-itext Additional commits viewable in https://github.com/apache/maven-doxia/compare/doxia-1.10...doxia-1.11.1";>compare view Updates `doxia-logging-api` from 1.10 to 1.11.1 Commits https://github.com/apache/maven-doxia/commit/84c3babdeeadafb546985e00353c1dc71c770344";>84c3bab [maven-release-plugin] prepare release doxia-1.11.1 https://github.com/apache/maven-doxia/commit/88fdae390aef87d540037133177be5f85670";>88fda88 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-doxia/commit/ea9e1c6a54165daebe043067cfd0a72cba7ad91b";>ea9e1c6 [maven-release-plugin] prepare release doxia-1.11 https://github.com/apache/maven-doxia/commit/a5145159ec5d8c993612560fb2bb2ef10b3815ab";>a514515 [DOXIA-629] Deprecate SwfMacro https://github.com/apache/maven-doxia/commit/80e02c5cbf0ada390789af21235d41168ac8874a";>80e02c5 [DOXIA-628] Deprecate SsiMacro https://github.com/apache/maven-doxia/commit/21b3b82f9d74cd329258a1b137048a2205d169e6";>21b3b82 [DOXIA-620] Deprecate Doxia Logging API in favor of SLF4J https://github.com/apache/maven-doxia/commit/05d719a105d1504fe78b72cc204185968c40ee20";>05d719a [DOXIA-627] Deprecate doxia-module-twiki https://github.com/apache/maven-doxia/commit/ca9af5a8ef8298a8f21d6c5de2a3ccc53509b5b8";>ca9af5a [DOXIA-626] Deprecate doxia-module-rtf https://github.com/apache/maven-doxia/commit/37cfeda9607a3aae177171e801c180b94f733ced";>37cfeda [DOXIA-625] Deprecate doxia-module-latex https://github.com/apache/maven-doxia/commit/4df28158c8a291228b30a1bbb2506b7421a6a9fd";>4df2815 [DOXIA-624] Deprecate doxia-module-itext Additional commits viewable in https://github.com/apache/maven-doxia/compare/doxia-1.10...doxia-1.11.1";>compare view Updates `doxia-sink-api` from 1.10 to 1.11.1 Commits https://github.com/apache/maven-doxia/commit/84c3babdeeadafb546985e00353c1dc71c770344";>84c3bab [maven-release-plugin] prepare release doxia-1.11.1 https://github.com/apache/maven-doxia/commit/88fdae390aef87d540037133177be5f85670";>88fda88 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-doxia/commit/ea9e1c6a54165daebe043067cfd0a72cba7ad91b";>ea9e1c6 [maven-release-plugin] prepare release doxia-1.11 https://github.com/apache/maven-doxia/commit/a5145159ec5d8c993612560fb2bb2ef10b3815ab";>a514515 [DOXIA-629] Deprecate SwfMacro https://github.com/apache/maven-doxia/commit/80e02c5cbf0ada390789af21235d41168ac8874a";>80e02c5 [DOXIA-628] Deprecate SsiMacro https://github.com/apache/maven-doxia/commit/21b3b82f9d74cd329258a1b137048a2205d169e6";>21b3b82 [DOXIA-620] Deprecate Doxia Logging API in favor of SLF4J https://github.com/apache/maven-doxia/commit/05d719a105d1504fe78b72cc204185968c40ee20";>05d719a [DOXIA-627] Deprecate doxia-module-twiki https://github.com/apache/maven-doxia/commit/ca9af5a8ef8298a8f21d6c5de2a3ccc53509b5b8";>ca9af5a [DOXIA-626] Deprecate doxia-module-rtf https://github.com/apache/maven-doxia/commit/37cfeda9607a3aae177171e801c180b94f733ced";>37cfeda [DOXIA-625] Deprecate doxia-module-latex https://github.com/apache/maven-doxia/commit/4df28158c8a291228b30a1bbb2506b7421a6a9fd";>4df2815 [DOXIA-624] Deprecate doxia-module-itext Additional commits viewab
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request #58: Bump maven-site-plugin from 3.9.1 to 3.10.0
dependabot[bot] opened a new pull request #58: URL: https://github.com/apache/maven-apache-parent/pull/58 Bumps [maven-site-plugin](https://github.com/apache/maven-site-plugin) from 3.9.1 to 3.10.0. Commits https://github.com/apache/maven-site-plugin/commit/c56b7b2ad2baecbf4286151c645ff4ee9190f420";>c56b7b2 [maven-release-plugin] prepare release maven-site-plugin-3.10.0 https://github.com/apache/maven-site-plugin/commit/7029bab59cac4fe83b62c245e55c37bcb79d9061";>7029bab [MSITE-878] Upgrade Doxia to 1.11.1 and Doxia Tools to 1.11.1 https://github.com/apache/maven-site-plugin/commit/7f8fe7ead4e42b7797eed7eb87c878a16e10b5be";>7f8fe7e [MSITE-877] Shared GitHub Actions (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/65";>#65) https://github.com/apache/maven-site-plugin/commit/e3302845bd4fac62e7869d1afd0faadd0499becc";>e330284 require CDATA https://github.com/apache/maven-site-plugin/commit/eeba50cf6854c9cca709ae47a626d57d924e463e";>eeba50c Add PR template https://github.com/apache/maven-site-plugin/commit/7813e8f193131faec8898b54b0e59c82602ab665";>7813e8f add Sitetools' integration tool and skin model https://github.com/apache/maven-site-plugin/commit/fda2a84b09a6d08ceb26efee963f00a21e02ffc2";>fda2a84 Updated CI setup https://github.com/apache/maven-site-plugin/commit/0cd2070cf4e32086fe936ea09c5f80c7d5a988cb";>0cd2070 Bump slf4jVersion from 1.7.31 to 1.7.32 (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/58";>#58) https://github.com/apache/maven-site-plugin/commit/9f24d2bd21f3d7a741ea74b4f41aa42ee02ce625";>9f24d2b update CI url https://github.com/apache/maven-site-plugin/commit/e06aa7822797f6ee54ee4dd309d955c3822df801";>e06aa78 [MSITE-875] add 3.10.0 in history table Additional commits viewable in https://github.com/apache/maven-site-plugin/compare/maven-site-plugin-3.9.1...maven-site-plugin-3.10.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 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
[GitHub] [maven-parent] dependabot[bot] opened a new pull request #43: Bump plexus-component-annotations from 2.1.0 to 2.1.1
dependabot[bot] opened a new pull request #43: URL: https://github.com/apache/maven-parent/pull/43 Bumps [plexus-component-annotations](https://github.com/codehaus-plexus/plexus-containers) from 2.1.0 to 2.1.1. Release notes Sourced from https://github.com/codehaus-plexus/plexus-containers/releases";>plexus-component-annotations's releases. 2.1.1 Plexus Containers 2.1.1 requires Java 7 and Maven 3.2.5+ Upgrade ASM to 9.2 [Snyk] Security upgrade org.jdom:jdom2 from 2.0.6 to 2.0.6.1 by https://github.com/snyk-bot";>@snyk-bot Changelog Sourced from https://github.com/codehaus-plexus/plexus-containers/blob/master/ReleaseNotes.md";>plexus-component-annotations's changelog. Plexus Containers 2.1.1 Plexus Containers 2.1.1 requires Java 7 and Maven 3.2.5+ Improvements Upgrade ASM to 9.2 Upgrade JDOM2 to 2.0.6.1 Commits https://github.com/codehaus-plexus/plexus-containers/commit/3b0a8d5fd086e3f74ccdeecaac9cd63e44047e91";>3b0a8d5 [maven-release-plugin] prepare release plexus-containers-2.1.1 https://github.com/codehaus-plexus/plexus-containers/commit/2f4800dcfdcd1177341cb7682792e30be2c7ec60";>2f4800d Fix issues with release https://github.com/codehaus-plexus/plexus-containers/commit/e4878028b3104d45cd5c6e91fce07dd08f06f2b3";>e487802 Add release notes for 2.1.1 https://github.com/codehaus-plexus/plexus-containers/commit/85e7f402fbf7e2527736cd0654c9ce905a57c6dd";>85e7f40 Fix build errors https://github.com/codehaus-plexus/plexus-containers/commit/31f3f0ab782154d088354ea1029ef0b0f716356f";>31f3f0a Restore Java 7 compatibility https://github.com/codehaus-plexus/plexus-containers/commit/ff15fcf0384913301e46a05cb28facfb6287ce88";>ff15fcf Bump ASM to 9.2 https://github.com/codehaus-plexus/plexus-containers/commit/7da2a9884382635fe41ecf66049ef70224fb9340";>7da2a98 Require Maven 3.2.5 https://github.com/codehaus-plexus/plexus-containers/commit/977d99324e5fb94968a601284592675803bfe954";>977d993 Require Java 8 https://github.com/codehaus-plexus/plexus-containers/commit/5d49068f1d2f962fb27096aa79aa3a7dea623fe4";>5d49068 Bump plexus from 5.1 to 8 https://github.com/codehaus-plexus/plexus-containers/commit/4f0743cc70f0eedc1bcd64d043d41cda77343eed";>4f0743c Bump qdox from 2.0-M10 to 2.0.1 Additional commits viewable in https://github.com/codehaus-plexus/plexus-containers/compare/plexus-containers-2.1.0...plexus-containers-2.1.1";>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 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
[GitHub] [maven-jar-plugin] dependabot[bot] opened a new pull request #31: Bump mavenVersion from 3.1.0 to 3.8.4
dependabot[bot] opened a new pull request #31: URL: https://github.com/apache/maven-jar-plugin/pull/31 Bumps `mavenVersion` from 3.1.0 to 3.8.4. Updates `maven-plugin-api` from 3.1.0 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.1.0...maven-3.8.4";>compare view Updates `maven-core` from 3.1.0 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Additional commits viewable in https://github.com/apache/maven/compare/maven-3.1.0...maven-3.8.4";>compare view Updates `maven-artifact` from 3.1.0 to 3.8.4 Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [maven-release-plugin] prepare release maven-3.8.4 https://github.com/apache/maven/commit/19c3b917b3604f93fef0583a08e70f8695d3a359";>19c3b91 [MNG-7331] Upgrade Jansi to 2.4.0 https://github.com/apache/maven/commit/5c36bf5ef78a162cefea47ccdaf0d28e01c1426c";>5c36bf5 [MNG-7312] Revert ThreadLocal approach from MNG-6843 and MNG-7251 https://github.com/apache/maven/commit/fb5f3f5b0f36d3232b0193c1d9b33fd0b36b9601";>fb5f3f5 [MNG-7270] Switch to shell alternative to "which" https://github.com/apache/maven/commit/b6186e2c7714158b5a2709f4af9d40b194c53f55";>b6186e2 Remove swap file https://github.com/apache/maven/commit/21e597ec777f0b74eed4e067b58b6eb8b0c9fad4";>21e597e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/ff8e977a158738155dc465c6a97ffaf31982d739";>ff8e977 [maven-release-plugin] prepare release maven-3.8.3 https://github.com/apache/maven/commit/0a6bbb8301717d386e6588a7ea32e3e2451c7060";>0a6bbb8 [MNG-7235] Speed improvements when calculating the sorted project graph https://github.com/apache/maven/commit/8882a9c599013182e42f0c7c321396c23b84dbe0";>8882a9c [MNG-7164] Add constructor MojoExecutionException(Throwable) https://github.com/apache/maven/commit/ab54d17dc2ec355c1e002e8751739edd9a96fcc3";>ab54d17 [MNG-7253] Display relocation message defined in model Addi
[GitHub] [maven-resolver] caiwei-ebay removed a comment on pull request #136: [MRESOLVER-228] skip & reconcile
caiwei-ebay removed a comment on pull request #136: URL: https://github.com/apache/maven-resolver/pull/136#issuecomment-987514827 Basically the strategy of this approach is: - Skip more nodes - Reconcile least nodes There is one more case that the node can be skipped reconciling: the node's parents includes any conflict losers. In such case, maven won't pick up such node at all, so it is safe to skip reconciling. Also renamed a few variables, added a few comments to make it easy to understand. Here is the commit: https://github.com/apache/maven-resolver/pull/136/commits/78e5e98b6430ba71c982cbc9bce6f603cc2cb286 We have recertified this code changes by running large numbers of applications in our company by comparing dependency:tree and dependency:list result. Now most of the applications skipped quite a few nodes and just need to reconcile 0 nodes. And if there is version conflicts, this approach just needs to reconcile least nodes. -- 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] (MCOMPILER-478) testCompile with specific module-info.java partially copy target/classes to target/test-classes
[
https://issues.apache.org/jira/browse/MCOMPILER-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rocher Suchard updated MCOMPILER-478:
-
Description:
Hello,
I am trying to understand how I can fix this particular bug that occurs while
compiling test sources with {{src/test/java/module-info.java}} (or
{{src/test/jpms/module-info.java}} in my case because this would make Eclipse
fails, due to having two module-info.java).
The {{module-info}} that I put in {{src/test/jpms}} is more or less the same as
{{{}src/main/jpms{}}}, but with some test modules (like {{{}org.opentest4j{}}},
{{{}org.junit.jupiter.api{}}}, and {{{}org.assertj.core{}}}). This is pretty
much what is explained here at the end of page:
[https://maven.apache.org/surefire/maven-surefire-plugin/examples/jpms.html#].
When I try to run tests, maven-surefire-plugin fails: the JVM is not happy
about a package not found.
{code:java}
# Created at 2021-12-26T23:43:40.644
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Error occurred during initialization of boot layer'.
# Created at 2021-12-26T23:43:40.647
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'java.lang.module.FindException: Error reading module:'.
# Created at 2021-12-26T23:43:40.647
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'...\target\test-classes'.
# Created at 2021-12-26T23:43:40.648
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Caused by: java.lang.module.InvalidModuleDescriptorException:'.
# Created at 2021-12-26T23:43:40.649
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Package org.acme.functions not found in module'.
{code}
At first, I thought it was something related to maven-surefire-plugin and I
wanted to create a SUREFIRE JIRA issue, but I discovered that something - I
presume maven-compiler-plugin - is copying used classes from {{target/classes}}
to {{target/test-classes}} during test compilation.
In the case of my interface, it is not used and I presume the "something" that
I speak about do partial copy of used files during compilation.
If we edit the src\main\java\org\acme\impl\AImpl.java to use the interface
(should be commented in the attached ZIP):
{code:java}
public class AImpl implements A {
@Override public void doSomethingCool() {
org.acme.functions.BooleanConsumer bc = v -> {};
throw new UnsupportedOperationException("no doing something cool");
}
}
{code}
The class file is copied and surefire does not fail.
The attached ZIP file exhibit the problem :
If we simply compile with tests: {{{}mvn install{}}}: {{maven-surefire-plugin}}
will fails to execute test because of missing package. I could probably remove
the offending package from test/module-info but I don't think I should tinker
to much : the test/module-info should really "extends" the main/module-info and
only add packages/modules.
If we skip test : {{{}mvn install -DskipTests{}}}: {{maven-jar-plugin}} will
fails to execute to process due to a jar error {_}(jar: Package
org.acme.functions missing from ModulePackages class file attribute{_}){_}.{_}
A solution to both issues would be to create dedicated tests project, with its
own module-info.java and another module name (eg: org.acme.tests) but that
would no longer be a (modular) white box testing.
*Note :* the attached project requires Maven 3.8.4 (there is a maven wrapper
inside) and Java 17. I don't know if this fail with Java 11.
was:
Hello,
I am trying to understand how I can fix this particular bug that occurs while
compiling test sources with {{src/test/java/module-info.java}} (or
{{src/test/jpms/module-info.java}} in my case because this would make Eclipse
fails, due to having two module-info.java).
The {{module-info}} that I put in {{src/test/jpms}} is more or less the same as
{{{}src/main/jpms{}}}, but with some test modules (like {{{}org.opentest4j{}}},
{{{}org.junit.jupiter.api{}}}, and {{{}org.assertj.core{}}}). This is pretty
much what is explained here at the end of page:
[https://maven.apache.org/surefire/maven-surefire-plugin/examples/jpms.html#].
When I try to run tests, maven-surefire-plugin fails: the JVM is not happy
about a package not found.
{code:java}
# Created at 2021-12-26T23:43:40.644
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Error occurred during initialization of boot layer'.
# Created at 2021-12-26T23:43:40.647
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'java.lang.module.FindException: Error reading module:'.
# Created at 2021-12-26T23:43:40.647
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'...\target\test-classes'.
# Created at 2021-12-26T23:43:40.648
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Str
[jira] [Created] (MCOMPILER-478) testCompile with specific module-info.java partially copy target/classes to target/test-classes
Rocher Suchard created MCOMPILER-478:
Summary: testCompile with specific module-info.java partially copy
target/classes to target/test-classes
Key: MCOMPILER-478
URL: https://issues.apache.org/jira/browse/MCOMPILER-478
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.8.1
Reporter: Rocher Suchard
Attachments: surefire-empty-packages.zip
Hello,
I am trying to understand how I can fix this particular bug that occurs while
compiling test sources with {{src/test/java/module-info.java}} (or
{{src/test/jpms/module-info.java}} in my case because this would make Eclipse
fails, due to having two module-info.java).
The {{module-info}} that I put in {{src/test/jpms}} is more or less the same as
{{{}src/main/jpms{}}}, but with some test modules (like {{{}org.opentest4j{}}},
{{{}org.junit.jupiter.api{}}}, and {{{}org.assertj.core{}}}). This is pretty
much what is explained here at the end of page:
[https://maven.apache.org/surefire/maven-surefire-plugin/examples/jpms.html#].
When I try to run tests, maven-surefire-plugin fails: the JVM is not happy
about a package not found.
{code:java}
# Created at 2021-12-26T23:43:40.644
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Error occurred during initialization of boot layer'.
# Created at 2021-12-26T23:43:40.647
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'java.lang.module.FindException: Error reading module:'.
# Created at 2021-12-26T23:43:40.647
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'...\target\test-classes'.
# Created at 2021-12-26T23:43:40.648
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Caused by: java.lang.module.InvalidModuleDescriptorException:'.
# Created at 2021-12-26T23:43:40.649
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream
'Package org.acme.functions not found in module'.
{code}
At first, I thought it was something related to maven-surefire-plugin and I
wanted to create a SUREFIRE JIRA issue, but I discovered that something - I
presume maven-compiler-plugin - is copying used classes from {{target/classes}}
to {{target/test-classes}} during test compilation.
In the case of my interface, it is not used and I presume the "something" that
I speak about do partial copy of used files during compilation.
If we edit the src\main\java\org\acme\impl\AImpl.java to use the interface
(should be commented in the attached ZIP):
{code:java}
public class AImpl implements A {
@Override public void doSomethingCool() {
org.acme.functions.BooleanConsumer bc = v -> {};
throw new UnsupportedOperationException("no doing something cool");
}
}
{code}
The class file is copied and surefire does not fail.
The attached ZIP file exhibit the problem :
If we simply compile with tests: {{{}mvn install{}}}: {{maven-surefire-plugin}}
will fails to execute test because of missing package. I could probably remove
the offending package from test/module-info but I don't think I should tinker
to much : the test/module-info should really "extends" the main/module-info and
only add packages/modules.
If we skip test : {{{}mvn install -DskipTests{}}}: {{maven-jar-plugin}} will
fails to execute to process due to a jar error {_}(jar: Package
org.acme.functions missing from ModulePackages class file attribute{_}){_}.{_}
A solution to both issues would be to create dedicated tests project, with its
own module-info.java and another module name (eg: org.acme.tests).
*Note :* the attached project requires Maven 3.8.4 (there is a maven wrapper
inside) and Java 17. I don't know if this fail with Java 11.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MPOM-281) Update maven-plugin-plugin to 3.6.3
[ https://issues.apache.org/jira/browse/MPOM-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-281: --- Description: As 3.6.3 has several issues all fixed now https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20fixVersion%20%3D%203.6.3 (was: As 3.6.2 has several issues all fixed now https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20fixVersion%20%3D%203.6.3) > Update maven-plugin-plugin to 3.6.3 > --- > > Key: MPOM-281 > URL: https://issues.apache.org/jira/browse/MPOM-281 > Project: Maven POMs > Issue Type: Task > Components: maven >Reporter: Tamás Cservenák >Priority: Major > Fix For: MAVEN-35 > > > As 3.6.3 has several issues all fixed now > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20fixVersion%20%3D%203.6.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MPOM-218) consider impact of maven-remote-resources-plugin in plugins not pluginManagement
[ https://issues.apache.org/jira/browse/MPOM-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465473#comment-17465473 ] Herve Boutemy commented on MPOM-218: it looks a little bit like MPOM-134 > consider impact of maven-remote-resources-plugin in plugins not > pluginManagement > - > > Key: MPOM-218 > URL: https://issues.apache.org/jira/browse/MPOM-218 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-16, ASF-24 >Reporter: Adrian Cole >Priority: Major > > While maven-remote-resources-plugin in plugins, it is difficult to work with > vs if it were in pluginManagement. For example, the parent pom can spit out a > distracting empty DEPENDENCIES file, which ends up by default in the source > distribution. > I've noticed multiple projects (ex dubbo, edgent) creating separate > distribution modules which on one hand works around this issue, but on the > other is a source of maintenance. > I'd ask to consider using pluginManagement instead, or possibly having the > ability to not create a DEPENDENCIES file when there are none, which would > also solve the problem. Maybe there's also another way to strip this out with > an assembly, but I've failed to figure this out. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MPOM-134) Add profile to use a different resource bundle for incubator projects
[
https://issues.apache.org/jira/browse/MPOM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPOM-134:
---
Component/s: asf
> Add profile to use a different resource bundle for incubator projects
> -
>
> Key: MPOM-134
> URL: https://issues.apache.org/jira/browse/MPOM-134
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-18
>Reporter: Christopher Tubbs
>Priority: Major
>
> The {{org.apache:apache-jar-resource-bundle:1.4}} resourceBundle currently
> specified in the parent POM does not handle the DISCLAIMER file for incubator
> projects.
> It would be nice if there were an incubation profile, which could be
> activated for incubating projects, to use an incubating resource bundle which
> did handle this DISCLAIMER file.
> This could be done in several ways:
> # An optional second execution of the {{maven-remote-resources-plugin}} could
> run when the profile is activated, which handles a second resource bundle for
> the DISCLAIMER file.
> # The current resourceBundle could be turned into a property, which is
> overridden when the profile is activated, using a resourceBundle which
> handles everything the current one does, plus the DISCLAIMER file.
> # The current {{maven-remote-resources-plugin}} execution could have the
> {{}} element changed to {{ combine.children="append">}}, and the profile could specify an additional
> {{}} to handle the DISCLAIMER file, for the same execution id
> of {{maven-remote-resources-plugin}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MPOM-218) consider impact of maven-remote-resources-plugin in plugins not pluginManagement
[ https://issues.apache.org/jira/browse/MPOM-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-218: --- Component/s: asf > consider impact of maven-remote-resources-plugin in plugins not > pluginManagement > - > > Key: MPOM-218 > URL: https://issues.apache.org/jira/browse/MPOM-218 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Reporter: Adrian Cole >Priority: Major > > While maven-remote-resources-plugin in plugins, it is difficult to work with > vs if it were in pluginManagement. For example, the parent pom can spit out a > distracting empty DEPENDENCIES file, which ends up by default in the source > distribution. > I've noticed multiple projects (ex dubbo, edgent) creating separate > distribution modules which on one hand works around this issue, but on the > other is a source of maintenance. > I'd ask to consider using pluginManagement instead, or possibly having the > ability to not create a DEPENDENCIES file when there are none, which would > also solve the problem. Maybe there's also another way to strip this out with > an assembly, but I've failed to figure this out. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MPOM-218) consider impact of maven-remote-resources-plugin in plugins not pluginManagement
[ https://issues.apache.org/jira/browse/MPOM-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-218: --- Affects Version/s: ASF-24 ASF-16 > consider impact of maven-remote-resources-plugin in plugins not > pluginManagement > - > > Key: MPOM-218 > URL: https://issues.apache.org/jira/browse/MPOM-218 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-16, ASF-24 >Reporter: Adrian Cole >Priority: Major > > While maven-remote-resources-plugin in plugins, it is difficult to work with > vs if it were in pluginManagement. For example, the parent pom can spit out a > distracting empty DEPENDENCIES file, which ends up by default in the source > distribution. > I've noticed multiple projects (ex dubbo, edgent) creating separate > distribution modules which on one hand works around this issue, but on the > other is a source of maintenance. > I'd ask to consider using pluginManagement instead, or possibly having the > ability to not create a DEPENDENCIES file when there are none, which would > also solve the problem. Maybe there's also another way to strip this out with > an assembly, but I've failed to figure this out. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MPOM-218) consider impact of maven-remote-resources-plugin in plugins not pluginManagement
[
https://issues.apache.org/jira/browse/MPOM-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465472#comment-17465472
]
Herve Boutemy commented on MPOM-218:
yes, there is an execution that has been defined intentionally 12 years ago to
run: here is the code
{code:xml}
org.apache.maven.plugins
maven-remote-resources-plugin
process-resource-bundles
process
org.apache:apache-jar-resource-bundle:1.4
{code}
using the Apache jar resource bundle
https://maven.apache.org/apache-resource-bundles/index.html#jar-resource-bundle-and-incubator-disclaimer-resource-bundle
it was added in
https://github.com/apache/maven-apache-parent/commit/b6d76ce21b88c46a95e4c851d9da47013972152b
I must admit I don't really know the content, what would be the consequence of
simply removing that config, or if we can make it easily configurable
> consider impact of maven-remote-resources-plugin in plugins not
> pluginManagement
> -
>
> Key: MPOM-218
> URL: https://issues.apache.org/jira/browse/MPOM-218
> Project: Maven POMs
> Issue Type: Improvement
>Reporter: Adrian Cole
>Priority: Major
>
> While maven-remote-resources-plugin in plugins, it is difficult to work with
> vs if it were in pluginManagement. For example, the parent pom can spit out a
> distracting empty DEPENDENCIES file, which ends up by default in the source
> distribution.
> I've noticed multiple projects (ex dubbo, edgent) creating separate
> distribution modules which on one hand works around this issue, but on the
> other is a source of maintenance.
> I'd ask to consider using pluginManagement instead, or possibly having the
> ability to not create a DEPENDENCIES file when there are none, which would
> also solve the problem. Maybe there's also another way to strip this out with
> an assembly, but I've failed to figure this out.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWRAPPER-14) Make maven wrapper functional
[
https://issues.apache.org/jira/browse/MWRAPPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465469#comment-17465469
]
Hudson commented on MWRAPPER-14:
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #96
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/96/
> Make maven wrapper functional
> -
>
> Key: MWRAPPER-14
> URL: https://issues.apache.org/jira/browse/MWRAPPER-14
> Project: Maven Wrapper
> Issue Type: Task
>Affects Versions: 3.0.2
>Reporter: Tamás Cservenák
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.1.0
>
>
> Make a wrapper a normal wrapper. The wrapper is not meant to be part of any
> distribution, but a lightweight way to bootstrap maven without the need to
> install it onto target machine.
> With legacy wrapper:
> * checked out project "just works"
> * you know it builds with proper maven
> * exclude any mistake like install ancient mvn version or some distro
> mutilated mvn
> This is the main goal, and by having apache groupId, {{wrapper:wrapper}}
> should work like before.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7335) [Regression] Parallel build fails due to missing JAR artifacts in compilePath
[
https://issues.apache.org/jira/browse/MNG-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465467#comment-17465467
]
Hudson commented on MNG-7335:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #96
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/96/
> [Regression] Parallel build fails due to missing JAR artifacts in compilePath
> -
>
> Key: MNG-7335
> URL: https://issues.apache.org/jira/browse/MNG-7335
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.4, 4.0.0-alpha-1
> Environment: - Linux (tested Docker using maven:3-jdk-8 tag): happens
> most times.
> - Windows 10: happens sometimes.
>Reporter: Falko Modler
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5
>
>
> *The following was cloned from MNG-6843 which was fixed in 3.8.2 and 3.8.3,
> but came back in 3.8.4 due to MNG-7312:*
> Build of our multi module (57) Java maven project is failing phase when
> running it as parallel in 4 threads (mvn -T 4 clean install). The failure
> happens during compilation because packages/classes from compile dependencies
> cannot be found:
> {noformat}
> [main] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> (default-compile) on project common: Compilation failure: Compilation
> failure:
> [main] [ERROR]
> /home/common/src/main/java/com/foo/ZonedDateTimeParser.java:[6,32] package
> org.apache.commons.lang3 does not exist{noformat}
> After enabling debug logging (with thread names) I have found out that a
> compile path of the failing module is empty (besides target/classes):
> When running in 4 threads (-T 4):
> {noformat}
> [BuilderThread 2] [DEBUG] (f) compilePath = [/home/common/target/classes]
> ...
> [BuilderThread 2] [DEBUG] Command line options:
> [BuilderThread 2] [DEBUG] -d /home/common/target/classes -classpath
> /home/common/target/classes: -sourcepath
> /home/common/src/main/java:/home/common/target/generated-sources/annotations:
> -s /home/common/target/generated-sources/annotations -g -nowarn -target 1.8
> -source 1.8 -encoding UTF-8{noformat}
> When running in a single thread (-T 1):
> {noformat}
> [BuilderThread 0] [DEBUG] (f) compilePath = [/home/common/target/classes,
> /root/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar,
>
> /root/.m2/repository/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar,
>
> /root/.m2/repository/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar,
>
> /root/.m2/repository/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar,
> /root/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar,
> /root/.m2/repository/org/slf4j/slf4j-api/1.7.26/slf4j-api-1.7.26.jar,
> /root/.m2/repository/org/springframework/spring-beans/5.1.8.RELEASE/spring-beans-5.1.8.RELEASE.jar,
>
> /root/.m2/repository/org/springframework/spring-core/5.1.8.RELEASE/spring-core-5.1.8.RELEASE.jar,
>
> /root/.m2/repository/org/springframework/spring-context/5.1.8.RELEASE/spring-context-5.1.8.RELEASE.jar]
> ...
> [BuilderThread 0] [DEBUG] Command line options:
> [BuilderThread 0] [DEBUG] -d /home/common/target/classes -classpath
> /home/common/target/classes:/root/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar:/root/.m2/repository/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar:/root/.m2/repository/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar:/root/.m2/repository/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar:/root/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:/root/.m2/repository/org/slf4j/slf4j-api/1.7.26/slf4j-api-1.7.26.jar:/root/.m2/repository/org/springframework/spring-beans/5.1.8.RELEASE/spring-beans-5.1.8.RELEASE.jar:/root/.m2/repository/org/springframework/spring-core/5.1.8.RELEASE/spring-core-5.1.8.RELEASE.jar:/root/.m2/repository/org/springframework/spring-context/5.1.8.RELEASE/spring-context-5.1.8.RELEASE.jar:
> -sourcepath
> /home/common/src/main/java:/home/common/target/generated-sources/annotations:
> -s /home/common/target/generated-sources/annotations -g -nowarn -target 1.8
> -source 1.8 -encoding UTF-8{noformat}
> After adding custom log messages I have found out that the root cause is that
> org.apache.maven.project.MavenProject.setArtifactFilter() is called with null
> artifactFilter parameter. The call happens for the failing module from a
> thread that is building another module. The call stack is:
> {code:java}
> "BuilderThread 0@2513" prio=5 tid=0xe nid=NA runnable
> java.lang.Thread.State
[jira] [Commented] (MNG-7045) Drop CDI API from Maven
[ https://issues.apache.org/jira/browse/MNG-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465468#comment-17465468 ] Hudson commented on MNG-7045: - Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #96 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/96/ > Drop CDI API from Maven > --- > > Key: MNG-7045 > URL: https://issues.apache.org/jira/browse/MNG-7045 > Project: Maven > Issue Type: Bug > Components: Core >Reporter: Romain Manni-Bucau >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 3.8.3, 4.0.0, 4.0.0-alpha-1 > > > This is an old leak which triggered a lot of regressions and still triggers > bugs in mojos. > Since there is on real justification in maven itself (@Typed is not since > there are alternative and cdi is not used in any piece of maven), let's drop > it. > If a plugin needs it, it already has it since cdi-api is outdated anyway. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MPOM-266) Incorrect message with missing property "project.build.outputTimestamp"
[
https://issues.apache.org/jira/browse/MPOM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPOM-266.
--
Fix Version/s: ASF-25
Assignee: Herve Boutemy
Resolution: Invalid
message was simply removed when re-enabling reproducible builds for Apache
parent release MPOM-265
> Incorrect message with missing property "project.build.outputTimestamp"
> ---
>
> Key: MPOM-266
> URL: https://issues.apache.org/jira/browse/MPOM-266
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-24
>Reporter: Konrad Windszus
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-25
>
>
> The check introduced with MPOM-255 emits the following error message:
> bq. The property "project.build.outputTimestamp" must be set on the reactor's
> root pom.xml to make the build reproducible. Further information at
> "https://maven.apache.org/guides/mini/guide-reproducible-builds.html";.
> Having the property on the reactor's root pom.xml is not sufficient though in
> case reactor root != parent.
> Consider the following project structure
> {code}
> reactor root (has no parent)
> + module1 (has parent: parent)
> + parent (has parent: asf-parent)
> {code}
> In this case setting the property in {{reactor root}} is not enough, as each
> module's effective pom.xml must contain the property
> {{project.build.outputTimestamp}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MPOM-265) re-enable reproducible builds for ASF parent POM source-release.zip
[ https://issues.apache.org/jira/browse/MPOM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPOM-265. -- Assignee: Herve Boutemy Resolution: Fixed done in https://github.com/apache/maven-apache-parent/commit/30f681c9b3c5ecb60315f5d205692208864e86a4 > re-enable reproducible builds for ASF parent POM source-release.zip > --- > > Key: MPOM-265 > URL: https://issues.apache.org/jira/browse/MPOM-265 > Project: Maven POMs > Issue Type: Bug > Components: asf >Affects Versions: ASF-24 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Blocker > Fix For: ASF-25 > > > project.build.outputTimestamp property was removed in MPOM-255 > need to add it back for ASF parent POM source-release zip file -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[
https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465464#comment-17465464
]
Michael Osipov commented on MWAR-446:
-
Just debugged, the {{ConcurrentJarCreator}} is never used here. I assume that
this class is only used for JARs...
> Add an option to put libs in STORED mode (instead of DEFLATED)
> --
>
> Key: MWAR-446
> URL: https://issues.apache.org/jira/browse/MWAR-446
> Project: Maven WAR Plugin
> Issue Type: New Feature
>Reporter: Gaël Lalire
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[
https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465462#comment-17465462
]
Michael Osipov commented on MWAR-446:
-
I did a bit of analysis. The issue is not in Plexus Archiver because there is a
test which guarantees that ZIP types aren't recompressed:
{noformat}
$ zipinfo dont-recompress-added-zips.zip
Archive: dont-recompress-added-zips.zip
Zip file size: 3368 bytes, number of entries: 5
-rw-r--r-- 2.0 unx 383 b- defN 21-Dec-19 15:02 test.tar.gz
-rw-r--r-- 2.0 unx 157 b- stor 21-Dec-19 15:02 test.zip
-rw-r--r-- 2.0 unx 167 b- stor 21-Dec-19 15:02 namelessrootfolder.jar
-rw-r--r-- 2.0 unx 1070 b- stor 21-Dec-19 15:02 test.jar
-rwxr-xr-x 2.0 unx 1070 b- stor 21-Dec-19 15:02 test.rar
5 files, 2847 bytes uncompressed, 2852 bytes compressed: -0.2%
{noformat}
So the bug must be either in MWAR or MARCHIVER.
> Add an option to put libs in STORED mode (instead of DEFLATED)
> --
>
> Key: MWAR-446
> URL: https://issues.apache.org/jira/browse/MWAR-446
> Project: Maven WAR Plugin
> Issue Type: New Feature
>Reporter: Gaël Lalire
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465426#comment-17465426 ] Michael Osipov commented on MWAR-446: - Thanks, I reproducer is always good. I will take a look. > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MWAR-446 > URL: https://issues.apache.org/jira/browse/MWAR-446 > Project: Maven WAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MWAR-446: Fix Version/s: (was: waiting-for-feedback) > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MWAR-446 > URL: https://issues.apache.org/jira/browse/MWAR-446 > Project: Maven WAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465421#comment-17465421 ] Gaël Lalire commented on MWAR-446: -- recompressZippedFiles does not seems to do anything (at least for Maven dependencies, I don't know if you put a zip in src/main/resources). Tested with 3.3.2 at [https://github.com/vestige-java-app/mywar/tree/testRecompressOption] with false and true value, the dependencies are always deflated. > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MWAR-446 > URL: https://issues.apache.org/jira/browse/MWAR-446 > Project: Maven WAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > Fix For: waiting-for-feedback > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven] michael-o opened a new pull request #644: [MNG-7370] Upgrade Maven Wagon to 3.5.1
michael-o opened a new pull request #644: URL: https://github.com/apache/maven/pull/644 This closes #644 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) 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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MNG-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MNG-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. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] 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. - [ ] 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
[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #400: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #400: URL: https://github.com/apache/maven-surefire/pull/400#issuecomment-1001225444 @imonteroperez We already discussed this feature request with @olamy in ASF. This feature brings chaos to the meaning of the config parameter and a duplicate to filter `test` which have the space for the method filtering. Naturally, `includesFile` cannot be about filtering methods. Instead of those parameters pls use `*Test#test*One+testTwo?`. Why you do not use the config parameter `test`? Do you want to override or merge this parameter with system property `test`? -- 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
[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #400: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #400: URL: https://github.com/apache/maven-surefire/pull/400#issuecomment-1001225444 @imonteroperez We already discussed this feature request with @olamy in ASF. This feature bring chaos to the meaning of the config parameter and a duplicate to inclusion filter which have the space for the method filtering. Naturally, `includesFile` cannot be about filtering methods. Instead of those parameters pls use `*Test#test*One+testTwo?`. Why you do not use the config parameter `test`? Do you want to override or merge this parameter with system property `test`? -- 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
[GitHub] [maven-surefire] Tibor17 commented on pull request #400: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 commented on pull request #400: URL: https://github.com/apache/maven-surefire/pull/400#issuecomment-1001225444 @imonteroperez We already discussed this feature request with @olamy in ASF. This feature bring chaos to the meaning of the config parameter and a duplicate to inclusion filter which have the space for the method filtering. Naturally, `includesFile` cannot be about filtering methods. Instead of those parameters pls use `*Test#test*One+testTwo?`. Why you do not use the config parameter `test`? Do you want to override or merge this parameter with system property `test`? TestListResolver -- 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-7227) Fix CVE-2021-37714 present in apache-maven
[ https://issues.apache.org/jira/browse/MNG-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-7227. --- Resolution: Won't Fix > Fix CVE-2021-37714 present in apache-maven > -- > > Key: MNG-7227 > URL: https://issues.apache.org/jira/browse/MNG-7227 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.8.2 >Reporter: swapnil bharshankar >Priority: Minor > > Following high severity CVE-2021-37714 present in apache maven. > Description: jsoup is a Java library for working with HTML. Those using jsoup > versions prior to 1.14.2 to parse untrusted HTML or XML may be vulnerable to > DOS attacks. If the parser is run on user supplied input, an attacker may > supply content that causes the parser to get stuck (loop indefinitely until > cancelled), to complete more slowly than usual, or to throw an unexpected > exception. This effect may support a denial of service attack. The issue is > patched in version 1.14.2. There are a few available workarounds. Users may > rate limit input parsing, limit the size of inputs based on system resources, > and/or implement thread watchdogs to cap and timeout parse runtimes. > Ref: > * [https://github.com/jhy/jsoup/security/advisories/GHSA-m72m-mhq2-9p6c] > * [https://nvd.nist.gov/vuln/detail/CVE-2021-37714] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (WAGON-612) Update jsoup to >= 1.14.2 for fix security issue
[ https://issues.apache.org/jira/browse/WAGON-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-612. Resolution: Won't Fix > Update jsoup to >= 1.14.2 for fix security issue > > > Key: WAGON-612 > URL: https://issues.apache.org/jira/browse/WAGON-612 > Project: Maven Wagon > Issue Type: Dependency upgrade > Components: wagon-http >Affects Versions: 3.4.3 >Reporter: Nikolay Krasko >Priority: Minor > > There's a vulnerability report for the jsoup <= 1.14.2 > [https://www.cvedetails.com/cve/CVE-2021-37714|https://www.cvedetails.com/cve/CVE-2021-37714/] > jsoup:1.12.1 is used by wagon-http-shared:3.4.3, that triggers security bots > alerts. > Please could you update the dependency and release a new version? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (WAGON-574) improve license management when distributing Wagon shaded binary
[ https://issues.apache.org/jira/browse/WAGON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-574. Resolution: Won't Fix > improve license management when distributing Wagon shaded binary > > > Key: WAGON-574 > URL: https://issues.apache.org/jira/browse/WAGON-574 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-http >Affects Versions: 2.5, 2.6, 2.7, 2.8, 2.9, 2.10, 2.11, 2.12, 3.0.0, 3.1.0, > 3.2.0, 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Herve Boutemy >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > as discussed during Wagon 3.3.4 release vote > https://lists.apache.org/thread.html/7526295d1eb080d8d573cfcc2fe4c006c0d948287da7163cc85eadff@%3Cdev.maven.apache.org%3E > , > wagon-http-3.3.4-shaded.jar includes jsoup, which is MIT licensed > this should be advertised (since wagon 2.5...) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWRAPPER-14) Make maven wrapper functional
[
https://issues.apache.org/jira/browse/MWRAPPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465413#comment-17465413
]
Hudson commented on MWRAPPER-14:
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #298
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/298/
> Make maven wrapper functional
> -
>
> Key: MWRAPPER-14
> URL: https://issues.apache.org/jira/browse/MWRAPPER-14
> Project: Maven Wrapper
> Issue Type: Task
>Affects Versions: 3.0.2
>Reporter: Tamás Cservenák
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.1.0
>
>
> Make a wrapper a normal wrapper. The wrapper is not meant to be part of any
> distribution, but a lightweight way to bootstrap maven without the need to
> install it onto target machine.
> With legacy wrapper:
> * checked out project "just works"
> * you know it builds with proper maven
> * exclude any mistake like install ancient mvn version or some distro
> mutilated mvn
> This is the main goal, and by having apache groupId, {{wrapper:wrapper}}
> should work like before.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7045) Drop CDI API from Maven
[ https://issues.apache.org/jira/browse/MNG-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465414#comment-17465414 ] Hudson commented on MNG-7045: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #298 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/298/ > Drop CDI API from Maven > --- > > Key: MNG-7045 > URL: https://issues.apache.org/jira/browse/MNG-7045 > Project: Maven > Issue Type: Bug > Components: Core >Reporter: Romain Manni-Bucau >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 3.8.3, 4.0.0, 4.0.0-alpha-1 > > > This is an old leak which triggered a lot of regressions and still triggers > bugs in mojos. > Since there is on real justification in maven itself (@Typed is not since > there are alternative and cdi is not used in any piece of maven), let's drop > it. > If a plugin needs it, it already has it since cdi-api is outdated anyway. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-shade-plugin] radio-rogal commented on pull request #51: [MSHADE-371] Update Shade Apache[Notice/LICENSE] ResourceTransformer to use [NOTICE/LICENSE].md
radio-rogal commented on pull request #51: URL: https://github.com/apache/maven-shade-plugin/pull/51#issuecomment-1001217193 It's marked as closed not merged. So I have thought that it was declined as there are no tests. Then I have checked Git history and found these changes are in **master**. I have edited my previous comment :) -- 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
[GitHub] [maven-shade-plugin] radio-rogal edited a comment on pull request #51: [MSHADE-371] Update Shade Apache[Notice/LICENSE] ResourceTransformer to use [NOTICE/LICENSE].md
radio-rogal edited a comment on pull request #51: URL: https://github.com/apache/maven-shade-plugin/pull/51#issuecomment-1001168329 ~~Could you reopen this PR?~~ Not needed, it was merged. -- 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-14) Make maven wrapper functional
[
https://issues.apache.org/jira/browse/MWRAPPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465404#comment-17465404
]
Herve Boutemy commented on MWRAPPER-14:
---
wrapper removed from Maven Core in
https://github.com/apache/maven/commit/f793d862e3158f8dde98f00905f907b6bd5e0aaf
and ITs in
https://github.com/apache/maven-integration-testing/commit/1ce55e0cb8b41d3930512a8aac25b51548a16701
> Make maven wrapper functional
> -
>
> Key: MWRAPPER-14
> URL: https://issues.apache.org/jira/browse/MWRAPPER-14
> Project: Maven Wrapper
> Issue Type: Task
>Affects Versions: 3.0.2
>Reporter: Tamás Cservenák
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.1.0
>
>
> Make a wrapper a normal wrapper. The wrapper is not meant to be part of any
> distribution, but a lightweight way to bootstrap maven without the need to
> install it onto target machine.
> With legacy wrapper:
> * checked out project "just works"
> * you know it builds with proper maven
> * exclude any mistake like install ancient mvn version or some distro
> mutilated mvn
> This is the main goal, and by having apache groupId, {{wrapper:wrapper}}
> should work like before.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SCM-872) Support git-svn for buildnumber-maven-plugin
[ https://issues.apache.org/jira/browse/SCM-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-872. -- Resolution: Won't Fix Many components have been deprecated in SCM. We deliberately will not support git-svn. svnjava is also dead. Use gitexe or svnexe. > Support git-svn for buildnumber-maven-plugin > > > Key: SCM-872 > URL: https://issues.apache.org/jira/browse/SCM-872 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-gitexe, maven-scm-provider-svn >Affects Versions: future >Reporter: Alberto Fanjul Alonso >Priority: Major > > Related with https://github.com/mojohaus/buildnumber-maven-plugin/issues/72 > Can svnjava provider detect project is a git-svn repo and retrieve revision > from git log commit? > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MRESOLVER-216) [ERROR] Malformed \uxxxx encoding.
[
https://issues.apache.org/jira/browse/MRESOLVER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465393#comment-17465393
]
Michael Osipov commented on MRESOLVER-216:
--
I have already written in October:
https://issues.apache.org/jira/browse/MRESOLVER-216?focusedCommentId=17424958&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17424958
Please perform those steps.
> [ERROR] Malformed \u encoding.
> --
>
> Key: MRESOLVER-216
> URL: https://issues.apache.org/jira/browse/MRESOLVER-216
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Lado Kumsiashvili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: Screenshot 2021-12-26 at 14.44.41.png, Screenshot
> 2021-12-26 at 14.44.50.png, consoleText.txt
>
>
> We do still experience this "supposed to be fixed" Bug in maven resolver in
> our team. We use maven 3.8.2 and I guess it is packaged with 1.6.3 resolver.
> It occurs sometimes and never with
> {code:java}
> -Daether.metadataResolver.threads=1 {code}
>
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_301, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" {code}
>
> This is how the maven run with
> {code:java}
> mvn -X install {code}
> fails
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.035 s
> [INFO] Finished at: 2021-10-06T10:04:20+02:00
> [INFO]
>
> [ERROR] Malformed \u encoding.
> java.lang.IllegalArgumentException: Malformed \u encoding.
> at java.util.Properties.loadConvert (Properties.java:574)
> at java.util.Properties.load0 (Properties.java:391)
> at java.util.Properties.load (Properties.java:341)
> at org.eclipse.aether.internal.impl.TrackingFileManager.read
> (TrackingFileManager.java:56)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.read
> (DefaultUpdateCheckManager.java:511)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkMetadata
> (DefaultUpdateCheckManager.java:250)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
> (DefaultMetadataResolver.java:302)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
> (DefaultMetadataResolver.java:181)
> at
> org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion
> (DefaultVersionResolver.java:213)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom
> (DefaultArtifactDescriptorReader.java:204)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor
> (DefaultArtifactDescriptorReader.java:171)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor
> (DefaultDependencyCollector.java:538)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult
> (DefaultDependencyCollector.java:523)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:410)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.doRecurse
> (DefaultDependencyCollector.java:506)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:458)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies
> (DefaultDependencyCollector.java:254)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies
> (DefaultRepositorySystem.java:284)
> at org.apache.maven.project.DefaultProjectDependenciesResolver.reso
[jira] [Comment Edited] (MRESOLVER-216) [ERROR] Malformed \uxxxx encoding.
[
https://issues.apache.org/jira/browse/MRESOLVER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424958#comment-17424958
]
Michael Osipov edited comment on MRESOLVER-216 at 12/26/21, 3:19 PM:
-
MRESOLVER-177 should have solved this because the write actions to the
properties file have been serialized.
Please do the following:
1. Delete your local repo and try again.
2. Enable {{-X}}, I need to see what is happening.
3. Meanwhile please build Maven from Maven branch
{{maven-3.8.x-resolver-1.7.x}} and run your builds again. I'd like to see
whether this solves the issue.
4. Try
[this|https://maven.apache.org/resolver-archives/resolver-1.6.3/maven-resolver-synccontext-global/index.html]
with Maven 3.8.4.
was (Author: michael-o):
MRESOLVER-177 should have solved this because the write actions to the
properties file have been serialized.
Please do the following:
1. Delete your local repo and try again.
2. Enable {{-X}}, I need to see what is happening.
3. Meanwhile please build Maven from Maven branch
{{maven-3.8.x-resolver-1.7.x}} and run your builds again. I'd like to see
whether this solves the issue.
4. Try
[this|https://maven.apache.org/resolver-archives/resolver-1.6.3/maven-resolver-synccontext-global/index.html]
with Maven 3.8.3.
> [ERROR] Malformed \u encoding.
> --
>
> Key: MRESOLVER-216
> URL: https://issues.apache.org/jira/browse/MRESOLVER-216
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Lado Kumsiashvili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: Screenshot 2021-12-26 at 14.44.41.png, Screenshot
> 2021-12-26 at 14.44.50.png, consoleText.txt
>
>
> We do still experience this "supposed to be fixed" Bug in maven resolver in
> our team. We use maven 3.8.2 and I guess it is packaged with 1.6.3 resolver.
> It occurs sometimes and never with
> {code:java}
> -Daether.metadataResolver.threads=1 {code}
>
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_301, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" {code}
>
> This is how the maven run with
> {code:java}
> mvn -X install {code}
> fails
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.035 s
> [INFO] Finished at: 2021-10-06T10:04:20+02:00
> [INFO]
>
> [ERROR] Malformed \u encoding.
> java.lang.IllegalArgumentException: Malformed \u encoding.
> at java.util.Properties.loadConvert (Properties.java:574)
> at java.util.Properties.load0 (Properties.java:391)
> at java.util.Properties.load (Properties.java:341)
> at org.eclipse.aether.internal.impl.TrackingFileManager.read
> (TrackingFileManager.java:56)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.read
> (DefaultUpdateCheckManager.java:511)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkMetadata
> (DefaultUpdateCheckManager.java:250)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
> (DefaultMetadataResolver.java:302)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
> (DefaultMetadataResolver.java:181)
> at
> org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion
> (DefaultVersionResolver.java:213)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom
> (DefaultArtifactDescriptorReader.java:204)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor
> (DefaultArtifactDescriptorReader.java:171)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor
> (DefaultDependencyCollector.java:538)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult
> (DefaultDependencyCollector.java:523)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:410)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependen
[jira] [Commented] (MEAR-306) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MEAR-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465391#comment-17465391 ] Michael Osipov commented on MEAR-306: - It seems that the EAR plugin does not expose what the WAR plugin exposes. I believe that this is straight forward to implement. > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MEAR-306 > URL: https://issues.apache.org/jira/browse/MEAR-306 > Project: Maven EAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465390#comment-17465390 ] Michael Osipov commented on MWAR-446: - I expect this to work: https://codehaus-plexus.github.io/plexus-archiver/xref/org/codehaus/plexus/archiver/zip/ConcurrentJarCreator.html#L264 > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MWAR-446 > URL: https://issues.apache.org/jira/browse/MWAR-446 > Project: Maven WAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MWAR-446: Fix Version/s: waiting-for-feedback > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MWAR-446 > URL: https://issues.apache.org/jira/browse/MWAR-446 > Project: Maven WAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > Fix For: waiting-for-feedback > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MWAR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465388#comment-17465388 ] Michael Osipov commented on MWAR-446: - What about https://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#recompressZippedFiles? > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MWAR-446 > URL: https://issues.apache.org/jira/browse/MWAR-446 > Project: Maven WAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MEAR-306) Add an option to put libs in STORED mode (instead of DEFLATED)
[ https://issues.apache.org/jira/browse/MEAR-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MEAR-306: Summary: Add an option to put libs in STORED mode (instead of DEFLATED) (was: Add an option to put libs in STORED mode (instead of deflated)) > Add an option to put libs in STORED mode (instead of DEFLATED) > -- > > Key: MEAR-306 > URL: https://issues.apache.org/jira/browse/MEAR-306 > Project: Maven EAR Plugin > Issue Type: New Feature >Reporter: Gaël Lalire >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (MRESOLVER-216) [ERROR] Malformed \uxxxx encoding.
[
https://issues.apache.org/jira/browse/MRESOLVER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465378#comment-17465378
]
Lado Kumsiashvili edited comment on MRESOLVER-216 at 12/26/21, 1:46 PM:
[~michael-o] it happened today with maven 3.8.4 on mac, run within intelij
Terminal Tab. Which information would be useful now? Because I am not sure,
when i deleted the maven repository and retry, if it will fail again.
!Screenshot 2021-12-26 at 14.44.41.png!!Screenshot 2021-12-26 at 14.44.50.png!
was (Author: herrlado):
[~michael-o] it happened today with maven 3.8.4 on mac, run within intelij
Terminal Tab. Which information would be usefull now? Because I am not sure,
when i deleted the maven repository and retry, if it will fail again.
!Screenshot 2021-12-26 at 14.44.41.png!
> [ERROR] Malformed \u encoding.
> --
>
> Key: MRESOLVER-216
> URL: https://issues.apache.org/jira/browse/MRESOLVER-216
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Lado Kumsiashvili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: Screenshot 2021-12-26 at 14.44.41.png, Screenshot
> 2021-12-26 at 14.44.50.png, consoleText.txt
>
>
> We do still experience this "supposed to be fixed" Bug in maven resolver in
> our team. We use maven 3.8.2 and I guess it is packaged with 1.6.3 resolver.
> It occurs sometimes and never with
> {code:java}
> -Daether.metadataResolver.threads=1 {code}
>
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_301, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" {code}
>
> This is how the maven run with
> {code:java}
> mvn -X install {code}
> fails
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.035 s
> [INFO] Finished at: 2021-10-06T10:04:20+02:00
> [INFO]
>
> [ERROR] Malformed \u encoding.
> java.lang.IllegalArgumentException: Malformed \u encoding.
> at java.util.Properties.loadConvert (Properties.java:574)
> at java.util.Properties.load0 (Properties.java:391)
> at java.util.Properties.load (Properties.java:341)
> at org.eclipse.aether.internal.impl.TrackingFileManager.read
> (TrackingFileManager.java:56)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.read
> (DefaultUpdateCheckManager.java:511)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkMetadata
> (DefaultUpdateCheckManager.java:250)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
> (DefaultMetadataResolver.java:302)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
> (DefaultMetadataResolver.java:181)
> at
> org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion
> (DefaultVersionResolver.java:213)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom
> (DefaultArtifactDescriptorReader.java:204)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor
> (DefaultArtifactDescriptorReader.java:171)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor
> (DefaultDependencyCollector.java:538)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult
> (DefaultDependencyCollector.java:523)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:410)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.doRecurse
> (DefaultDependencyCollector.java:506)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:458)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl
[jira] [Commented] (MRESOLVER-216) [ERROR] Malformed \uxxxx encoding.
[
https://issues.apache.org/jira/browse/MRESOLVER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465378#comment-17465378
]
Lado Kumsiashvili commented on MRESOLVER-216:
-
[~michael-o] it happened today with maven 3.8.4 on mac, run within intelij
Terminal Tab. Which information would be usefull now? Because I am not sure,
when i deleted the maven repository and retry, if it will fail again.
!Screenshot 2021-12-26 at 14.44.41.png!
> [ERROR] Malformed \u encoding.
> --
>
> Key: MRESOLVER-216
> URL: https://issues.apache.org/jira/browse/MRESOLVER-216
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Lado Kumsiashvili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: Screenshot 2021-12-26 at 14.44.41.png, Screenshot
> 2021-12-26 at 14.44.50.png, consoleText.txt
>
>
> We do still experience this "supposed to be fixed" Bug in maven resolver in
> our team. We use maven 3.8.2 and I guess it is packaged with 1.6.3 resolver.
> It occurs sometimes and never with
> {code:java}
> -Daether.metadataResolver.threads=1 {code}
>
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_301, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" {code}
>
> This is how the maven run with
> {code:java}
> mvn -X install {code}
> fails
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.035 s
> [INFO] Finished at: 2021-10-06T10:04:20+02:00
> [INFO]
>
> [ERROR] Malformed \u encoding.
> java.lang.IllegalArgumentException: Malformed \u encoding.
> at java.util.Properties.loadConvert (Properties.java:574)
> at java.util.Properties.load0 (Properties.java:391)
> at java.util.Properties.load (Properties.java:341)
> at org.eclipse.aether.internal.impl.TrackingFileManager.read
> (TrackingFileManager.java:56)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.read
> (DefaultUpdateCheckManager.java:511)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkMetadata
> (DefaultUpdateCheckManager.java:250)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
> (DefaultMetadataResolver.java:302)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
> (DefaultMetadataResolver.java:181)
> at
> org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion
> (DefaultVersionResolver.java:213)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom
> (DefaultArtifactDescriptorReader.java:204)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor
> (DefaultArtifactDescriptorReader.java:171)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor
> (DefaultDependencyCollector.java:538)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult
> (DefaultDependencyCollector.java:523)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:410)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.doRecurse
> (DefaultDependencyCollector.java:506)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:458)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies
> (DefaultDependencyCollector.java:254)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies
> (DefaultRepositorySystem.java:284)
> at org.apache.maven.proj
[jira] [Updated] (MRESOLVER-216) [ERROR] Malformed \uxxxx encoding.
[
https://issues.apache.org/jira/browse/MRESOLVER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lado Kumsiashvili updated MRESOLVER-216:
Attachment: Screenshot 2021-12-26 at 14.44.41.png
Screenshot 2021-12-26 at 14.44.50.png
> [ERROR] Malformed \u encoding.
> --
>
> Key: MRESOLVER-216
> URL: https://issues.apache.org/jira/browse/MRESOLVER-216
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Lado Kumsiashvili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: Screenshot 2021-12-26 at 14.44.41.png, Screenshot
> 2021-12-26 at 14.44.50.png, consoleText.txt
>
>
> We do still experience this "supposed to be fixed" Bug in maven resolver in
> our team. We use maven 3.8.2 and I guess it is packaged with 1.6.3 resolver.
> It occurs sometimes and never with
> {code:java}
> -Daether.metadataResolver.threads=1 {code}
>
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_301, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" {code}
>
> This is how the maven run with
> {code:java}
> mvn -X install {code}
> fails
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.035 s
> [INFO] Finished at: 2021-10-06T10:04:20+02:00
> [INFO]
>
> [ERROR] Malformed \u encoding.
> java.lang.IllegalArgumentException: Malformed \u encoding.
> at java.util.Properties.loadConvert (Properties.java:574)
> at java.util.Properties.load0 (Properties.java:391)
> at java.util.Properties.load (Properties.java:341)
> at org.eclipse.aether.internal.impl.TrackingFileManager.read
> (TrackingFileManager.java:56)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.read
> (DefaultUpdateCheckManager.java:511)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkMetadata
> (DefaultUpdateCheckManager.java:250)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
> (DefaultMetadataResolver.java:302)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
> (DefaultMetadataResolver.java:181)
> at
> org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion
> (DefaultVersionResolver.java:213)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom
> (DefaultArtifactDescriptorReader.java:204)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor
> (DefaultArtifactDescriptorReader.java:171)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor
> (DefaultDependencyCollector.java:538)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult
> (DefaultDependencyCollector.java:523)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:410)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.doRecurse
> (DefaultDependencyCollector.java:506)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:458)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
> (DefaultDependencyCollector.java:362)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process
> (DefaultDependencyCollector.java:349)
> at
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies
> (DefaultDependencyCollector.java:254)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies
> (DefaultRepositorySystem.java:284)
> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
> (DefaultProjectDependenciesResolver.java:170)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResol
[jira] [Created] (MEAR-306) Add an option to put libs in STORED mode (instead of deflated)
Gaël Lalire created MEAR-306: Summary: Add an option to put libs in STORED mode (instead of deflated) Key: MEAR-306 URL: https://issues.apache.org/jira/browse/MEAR-306 Project: Maven EAR Plugin Issue Type: New Feature Reporter: Gaël Lalire -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MWAR-446) Add an option to put libs in STORED mode (instead of DEFLATED)
Gaël Lalire created MWAR-446: Summary: Add an option to put libs in STORED mode (instead of DEFLATED) Key: MWAR-446 URL: https://issues.apache.org/jira/browse/MWAR-446 Project: Maven WAR Plugin Issue Type: New Feature Reporter: Gaël Lalire -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-shade-plugin] slachiewicz commented on pull request #51: [MSHADE-371] Update Shade Apache[Notice/LICENSE] ResourceTransformer to use [NOTICE/LICENSE].md
slachiewicz commented on pull request #51: URL: https://github.com/apache/maven-shade-plugin/pull/51#issuecomment-1001178462 It has been merged to master branch and will be part of next release. Why we should reopen PR? -- 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
[GitHub] [maven-shade-plugin] radio-rogal commented on pull request #51: [MSHADE-371] Update Shade Apache[Notice/LICENSE] ResourceTransformer to use [NOTICE/LICENSE].md
radio-rogal commented on pull request #51: URL: https://github.com/apache/maven-shade-plugin/pull/51#issuecomment-1001168329 Could you reopen this PR? -- 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
[GitHub] [maven-surefire] Tibor17 commented on pull request #415: [SUREFIRE-1955] Switch project to Java 8
Tibor17 commented on pull request #415: URL: https://github.com/apache/maven-surefire/pull/415#issuecomment-1001159989 Usually, we split this activity to multiple activities. 1. changing the Maven parent POM and Java Version 1.8 in POM. 2. Changing the Maven API version 3. changing the code towards Java 8 (there is one plugin which converts the code to java 8 features) -- 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] [Assigned] (SUREFIRE-1972) Use current version of surefire-shared-utils
[
https://issues.apache.org/jira/browse/SUREFIRE-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned SUREFIRE-1972:
-
Assignee: Slawomir Jaranowski
> Use current version of surefire-shared-utils
>
>
> Key: SUREFIRE-1972
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1972
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> surefire-shared-utils - contains dependencies to external shared utils.
> During build all dependencies are repacked under
> {{org.apache.maven.surefire.shared}} package by {{maven-shade-plugin}}.
> In this approach it is difficult to use in current version of module in
> project.
> We can delegate used shared classes and methods in open way and we can simply
> use it in project.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (SUREFIRE-1972) Use current version of surefire-shared-utils
Slawomir Jaranowski created SUREFIRE-1972:
-
Summary: Use current version of surefire-shared-utils
Key: SUREFIRE-1972
URL: https://issues.apache.org/jira/browse/SUREFIRE-1972
Project: Maven Surefire
Issue Type: Improvement
Reporter: Slawomir Jaranowski
surefire-shared-utils - contains dependencies to external shared utils.
During build all dependencies are repacked under
{{org.apache.maven.surefire.shared}} package by {{maven-shade-plugin}}.
In this approach it is difficult to use in current version of module in
project.
We can delegate used shared classes and methods in open way and we can simply
use it in project.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-surefire] slawekjaranowski commented on a change in pull request #400: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
slawekjaranowski commented on a change in pull request #400:
URL: https://github.com/apache/maven-surefire/pull/400#discussion_r775224480
##
File path:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
##
@@ -1839,7 +1841,7 @@ private PluginFailureReason getEffectiveFailIfNoTests()
{
if ( isSpecificTestSpecified() )
{
-return getFailIfNoSpecifiedTests() ? COULD_NOT_RUN_SPECIFIED_TESTS
: NONE;
+return getFailIfNoSpecifiedTests() ? COULD_NOT_RUN_SPECIFIED_TESTS
: NONE;
Review comment:
It will be ok for checkstyle?
--
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] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6829 #32 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6829/32/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MPOM-215 #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MPOM-215/31/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7270-maven-3.8.x #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7270-maven-3.8.x/2/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-5567 #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5567/31/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x_mavenProject_use_InheritableThreadLocal #6 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x_mavenProject_use_InheritableThreadLocal/6/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6889 #32 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6889/32/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6471 #18 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6471/18/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » mng-5668-poc #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/mng-5668-poc/31/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645 #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645/23/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x-resolver-1.7.x #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x-resolver-1.7.x/4/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build succeeded in Jenkins: Maven » Maven TLP » maven » MRESOLVER-94 #32 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MRESOLVER-94/32/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6846 #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6846/31/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » collapse-mvnDebug-into-mvn #12 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/collapse-mvnDebug-into-mvn/12/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7270 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7270/2/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7287 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7287/2/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7122 #17 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7122/17/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6727 #18 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6727/18/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » do-not-keep-parameters-map #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/do-not-keep-parameters-map/2/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7177 #11 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7177/11/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7273 #6 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7273/6/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645+MNG-6772 #19 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645+MNG-6772/19/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #33 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/33/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7166 #11 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7166/11/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6914) Align mvn and mvnw scripts
[ https://issues.apache.org/jira/browse/MNG-6914 ] Herve Boutemy deleted comment on MNG-6914: was (Author: hudson): Build unstable in Jenkins: Maven » Maven TLP » maven » mojo-logging #15 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/mojo-logging/15/ > Align mvn and mvnw scripts > -- > > Key: MNG-6914 > URL: https://issues.apache.org/jira/browse/MNG-6914 > Project: Maven > Issue Type: Improvement > Components: Maven Wrapper >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > With MNG-5937 the wrapper code becomes part of core. > The scripts are like 80% the same, 10% is wrapper specific and 10% are > differences due to improvements on one or the other side. > By aligning the scripts they both benefit from the improvements. > Some important changes that might but should not effect the build: > - CLASSWORLDS_LAUNCHER / WRAPPER_LAUNCHER will be renamed to LAUNCHER_CLASS > - CLASSWORLDS_JAR / WRAPPER_JAR will be renamed to LAUNCHER_JAR > - Introduce MAVENHOME_CONFIG. For the wrapper it will be empty (as the > wrapper must download Maven first), Maven will use it to set > classworlds.conf, maven.home and library.jansi.path -- This message was sent by Atlassian Jira (v8.20.1#820001)
