[GitHub] [maven-gh-actions-shared] slawekjaranowski merged pull request #38: Site build improvement
slawekjaranowski merged pull request #38: URL: https://github.com/apache/maven-gh-actions-shared/pull/38 -- 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-doxia-site] slachiewicz merged pull request #16: Bump maven-parent from 35-SNAPSHOT to 35
slachiewicz merged pull request #16: URL: https://github.com/apache/maven-doxia-site/pull/16 -- 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-clean-plugin] dependabot[bot] opened a new pull request #15: Bump maven-plugins from 34 to 35
dependabot[bot] opened a new pull request #15: URL: https://github.com/apache/maven-clean-plugin/pull/15 Bumps [maven-plugins](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-install-plugin] dependabot[bot] opened a new pull request #23: Bump maven-plugins from 34 to 35
dependabot[bot] opened a new pull request #23: URL: https://github.com/apache/maven-install-plugin/pull/23 Bumps [maven-plugins](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-reporting-api] dependabot[bot] opened a new pull request #6: Bump maven-shared-components from 34 to 35
dependabot[bot] opened a new pull request #6: URL: https://github.com/apache/maven-reporting-api/pull/6 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-invoker] dependabot[bot] opened a new pull request #46: Bump maven-shared-components from 34 to 35
dependabot[bot] opened a new pull request #46: URL: https://github.com/apache/maven-invoker/pull/46 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-dependency-analyzer] dependabot[bot] opened a new pull request #57: Bump maven-shared-components from 34 to 35
dependabot[bot] opened a new pull request #57: URL: https://github.com/apache/maven-dependency-analyzer/pull/57 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-doxia-site] dependabot[bot] opened a new pull request #16: Bump maven-parent from 35-SNAPSHOT to 35
dependabot[bot] opened a new pull request #16: URL: https://github.com/apache/maven-doxia-site/pull/16 Bumps [maven-parent](https://github.com/apache/maven-parent) from 35-SNAPSHOT to 35. Commits See full diff in https://github.com/apache/maven-parent/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-surefire] olamy merged pull request #480: Test only with 2 last Maven core 3.6.x and 3.8.x, avoid deep scanning to find jacoco files
olamy merged pull request #480: URL: https://github.com/apache/maven-surefire/pull/480 -- 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] olamy merged pull request #481: Add release-drafter to create gh releases
olamy merged pull request #481: URL: https://github.com/apache/maven-surefire/pull/481 -- 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] olamy commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
olamy commented on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058792456 > @imonteroperez It's the same. I used both commits [499dc83](https://github.com/apache/maven-surefire/commit/499dc8315e379cb2e3373bc40a9f8b23acbd04f0) and [1b721a9](https://github.com/apache/maven-surefire/commit/1b721a9ee9d35997fe62376257577d92ddbd968a) I have cherry picked the commits, shifted to the common module into the right test class where is mock already and finally squashed together in one. **I have only shifted the changes to the right module.** The work from @imonteroperez is here, nothing is lost, really! The Javadoc, both unit tests from @imonteroperez. I added third. yes but the problem is you didn't preserve the author id and so @imonteroperez doesn't get the credit he deserve! -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a I have cherry picked the commits, shifted to the common module into the right test class where is mock already and finally squashed together in one. **I have only shifted the changes to the right module.** The work from @imonteroperez is here, nothing is lost, really! The Javadoc, both unit tests from @imonteroperez. I added third. -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a I have cherry picked the commits, shifted to the common module into the right test class where is mock already and finally squashed in one. **I have only shifted the changes to the right module.** The work from @imonteroperez is here, nothing is lost, really! The Javadoc, both unit tests from @imonteroperez. I added third. -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a I have cherry picked the commits, shifted to the common module into the right test class where is mock already. **I have only shifted the changes to the right module.** The work from @imonteroperez is here, nothing is lost, really! The Javadoc, both unit tests from @imonteroperez. I added third. -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a **I have only shifted the changes to the right module.** The work from @imonteroperez is here, nothing is lost, really! The Javadoc, both unit tests from @imonteroperez. I added third. -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a I have only shifted the changes to the right module. The work from @imonteroperez is here, nothing is lost, really! The Javadoc, both unit tests from @imonteroperez. I added third. -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 edited a comment on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a I have only shifted the changes to the right module. The work from @imonteroperez is here, nothing is lost. The Javadoc, both unit tests. -- 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 #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
Tibor17 commented on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1058745846 @imonteroperez It's the same. I used both commits https://github.com/apache/maven-surefire/pull/460/commits/499dc8315e379cb2e3373bc40a9f8b23acbd04f0 and https://github.com/apache/maven-surefire/pull/460/commits/1b721a9ee9d35997fe62376257577d92ddbd968a I have only shifted the changes to the right module. -- 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] (MDEP-795) Update Jetty to 9.4.45.v20220203
[ https://issues.apache.org/jira/browse/MDEP-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501065#comment-17501065 ] Hudson commented on MDEP-795: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » PR-203 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/PR-203/2/ > Update Jetty to 9.4.45.v20220203 > > > Key: MDEP-795 > URL: https://issues.apache.org/jira/browse/MDEP-795 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.3.0 > > > New release of Jetty -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-dependency-tree] dependabot[bot] opened a new pull request #15: Bump maven-shared-components from 34 to 35
dependabot[bot] opened a new pull request #15: URL: https://github.com/apache/maven-dependency-tree/pull/15 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-gh-actions-shared] slawekjaranowski opened a new pull request #38: Site build improvement
slawekjaranowski opened a new pull request #38: URL: https://github.com/apache/maven-gh-actions-shared/pull/38 - build site only in ff - upload site as GH artifact - parent pom 35 - example java code -- 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] jglick opened a new issue #607: `mvnd.exe` gives error about DLL
jglick opened a new issue #607: URL: https://github.com/apache/maven-mvnd/issues/607 I tried downloading https://github.com/apache/maven-mvnd/releases/download/0.7.1/mvnd-0.7.1-windows-amd64.zip and running the contained `mvnd.exe`. This reports an error in a dialog box: > The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem. (same from Chocolatey: #160) Whereas `mvnd.cmd` does not get this error, and `-version` works. Other commands do not: ``` mvnd JVM client 0.7.1-windows-amd64 (97c587c11383a67b5bd0ff8388bd94c694b91c1e) Terminal: org.jline.terminal.impl.jansi.win.JansiWinSysTerminal Exception in thread "main" java.lang.ExceptionInInitializerError at org.mvndaemon.mvnd.client.DefaultClient.execute(DefaultClient.java:196) at org.mvndaemon.mvnd.client.DefaultClient.main(DefaultClient.java:118) Caused by: java.lang.NumberFormatException: For input string: "self" at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.base/java.lang.Integer.parseInt(Integer.java:652) at java.base/java.lang.Integer.parseInt(Integer.java:770) at org.mvndaemon.mvnd.common.DaemonRegistry.getProcessId0(DaemonRegistry.java:290) at org.mvndaemon.mvnd.common.DaemonRegistry.(DaemonRegistry.java:271) ... 2 more ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501021#comment-17501021 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-509 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-509/4/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6960) Use RuntimeInformation instead of reading properties
[ https://issues.apache.org/jira/browse/MNG-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501020#comment-17501020 ] Hudson commented on MNG-6960: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-509 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-509/4/ > Use RuntimeInformation instead of reading properties > > > Key: MNG-6960 > URL: https://issues.apache.org/jira/browse/MNG-6960 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-gh-actions-shared] slawekjaranowski merged pull request #36: Bump actions/checkout from 2.4.0 to 3
slawekjaranowski merged pull request #36: URL: https://github.com/apache/maven-gh-actions-shared/pull/36 -- 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-gh-actions-shared] slawekjaranowski merged pull request #34: Bump actions/setup-java from 2.5.0 to 3
slawekjaranowski merged pull request #34: URL: https://github.com/apache/maven-gh-actions-shared/pull/34 -- 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-gh-actions-shared] slawekjaranowski merged pull request #37: Bump actions/upload-artifact from 2.3.1 to 3
slawekjaranowski merged pull request #37: URL: https://github.com/apache/maven-gh-actions-shared/pull/37 -- 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-gh-actions-shared] slawekjaranowski commented on pull request #34: Bump actions/setup-java from 2.5.0 to 3
slawekjaranowski commented on pull request #34: URL: https://github.com/apache/maven-gh-actions-shared/pull/34#issuecomment-1058394015 @dependabot reopen -- 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-gh-actions-shared] slawekjaranowski commented on pull request #36: Bump actions/checkout from 2.4.0 to 3
slawekjaranowski commented on pull request #36: URL: https://github.com/apache/maven-gh-actions-shared/pull/36#issuecomment-1058393386 @dependabot reopen -- 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-gh-actions-shared] dependabot[bot] opened a new pull request #37: Bump actions/upload-artifact from 2.3.1 to 3
dependabot[bot] opened a new pull request #37: URL: https://github.com/apache/maven-gh-actions-shared/pull/37 Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 2.3.1 to 3. Release notes Sourced from https://github.com/actions/upload-artifact/releases";>actions/upload-artifact's releases. v3.0.0 What's Changed Update default runtime to node16 (https://github-redirect.dependabot.com/actions/upload-artifact/issues/293";>#293) Update package-lock.json file version to 2 (https://github-redirect.dependabot.com/actions/upload-artifact/issues/302";>#302) Breaking Changes With the update to Node 16, all scripts will now be run with Node 16 rather than Node 12. Commits https://github.com/actions/upload-artifact/commit/6673cd052c4cd6fcf4b4e6e60ea986c889389535";>6673cd0 Update lockfileVersion in package-lock.json (https://github-redirect.dependabot.com/actions/upload-artifact/issues/302";>#302) https://github.com/actions/upload-artifact/commit/2244c8200304ec9588bf9399eac622d9fadc28c4";>2244c82 Update to node16 (https://github-redirect.dependabot.com/actions/upload-artifact/issues/293";>#293) https://github.com/actions/upload-artifact/commit/87348cee5fefa95e42e9b4804b4d68e130304158";>87348ce Add 503 warning when uploading to the same artifact See full diff in https://github.com/actions/upload-artifact/compare/v2.3.1...v3";>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-gh-actions-shared] dependabot[bot] commented on pull request #32: Bump actions/setup-java from 2.5.0 to 3.0.0
dependabot[bot] commented on pull request #32: URL: https://github.com/apache/maven-gh-actions-shared/pull/32#issuecomment-1058386268 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-gh-actions-shared] slawekjaranowski closed pull request #32: Bump actions/setup-java from 2.5.0 to 3.0.0
slawekjaranowski closed pull request #32: URL: https://github.com/apache/maven-gh-actions-shared/pull/32 -- 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-gh-actions-shared] slawekjaranowski closed pull request #36: Bump actions/checkout from 2.4.0 to 3
slawekjaranowski closed pull request #36: URL: https://github.com/apache/maven-gh-actions-shared/pull/36 -- 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-gh-actions-shared] dependabot[bot] commented on pull request #36: Bump actions/checkout from 2.4.0 to 3
dependabot[bot] commented on pull request #36: URL: https://github.com/apache/maven-gh-actions-shared/pull/36#issuecomment-1058378343 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-gh-actions-shared] slawekjaranowski commented on pull request #32: Bump actions/setup-java from 2.5.0 to 3.0.0
slawekjaranowski commented on pull request #32: URL: https://github.com/apache/maven-gh-actions-shared/pull/32#issuecomment-1058377951 @dependabot reopen -- 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-gh-actions-shared] slawekjaranowski closed pull request #34: Bump actions/setup-java from 2.5.0 to 3
slawekjaranowski closed pull request #34: URL: https://github.com/apache/maven-gh-actions-shared/pull/34 -- 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-gh-actions-shared] dependabot[bot] commented on pull request #34: Bump actions/setup-java from 2.5.0 to 3
dependabot[bot] commented on pull request #34: URL: https://github.com/apache/maven-gh-actions-shared/pull/34#issuecomment-1058377699 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-gh-actions-shared] slawekjaranowski merged pull request #35: Bump actions/checkout from 2.4.0 to 3
slawekjaranowski merged pull request #35: URL: https://github.com/apache/maven-gh-actions-shared/pull/35 -- 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-gh-actions-shared] slawekjaranowski merged pull request #33: Bump actions/setup-java from 2.5.0 to 3
slawekjaranowski merged pull request #33: URL: https://github.com/apache/maven-gh-actions-shared/pull/33 -- 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-filtering] dependabot[bot] opened a new pull request #28: Bump maven-shared-components from 34 to 35
dependabot[bot] opened a new pull request #28: URL: https://github.com/apache/maven-filtering/pull/28 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 34 to 35. Commits See full diff in https://github.com/apache/maven-parent/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-dependency-plugin] slawekjaranowski opened a new pull request #204: [MDEP-796] Upgrade Maven Parent to 35
slawekjaranowski opened a new pull request #204: URL: https://github.com/apache/maven-dependency-plugin/pull/204 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEP) 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. - [x] Format the pull request title like `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MDEP-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. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500948#comment-17500948 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-638 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-638/4/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6960) Use RuntimeInformation instead of reading properties
[ https://issues.apache.org/jira/browse/MNG-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500947#comment-17500947 ] Hudson commented on MNG-6960: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-638 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-638/4/ > Use RuntimeInformation instead of reading properties > > > Key: MNG-6960 > URL: https://issues.apache.org/jira/browse/MNG-6960 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MDEP-798) Upgrade maven-dependency-tree from 3.0.1 to 3.1.0
[ https://issues.apache.org/jira/browse/MDEP-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MDEP-798: - Description: Release Notes - Maven Shared Components - Version maven-dependency-tree-3.1.0 h1. Improvement * [MSHARED-339] - DependencyGraphBuilder does not provide verbose tree * [MSHARED-491] - DependencyGraphBuilders shouldn't need reactorProjects for resolving dependencies * [MSHARED-519] - Maven31DependencyGraphBuilder (and others?) should not download dependencies other than the pom * [MSHARED-657] - plexus-component-annotation in line with plexus-component-metadata * [MSHARED-691] - Upgrade parent to 31 * [MSHARED-788] - Add functionality to collect raw dependencies in Maven 3+ * [MSHARED-816] - Annotate DependencyNodes with dependency management metadata * [MSHARED-825] - Require Java 8 * [MSHARED-850] - Upgrade org.eclipse.aether:aether-util dependency in org.apache.maven.shared:maven-dependency-tree * [MSHARED-852] - Add Exclusions to DependencyNode * [MSHARED-853] - make build Reproducible h1. Dependency upgrade * [MSHARED-771] - Upgrade shared-component to version 33 > Upgrade maven-dependency-tree from 3.0.1 to 3.1.0 > - > > Key: MDEP-798 > URL: https://issues.apache.org/jira/browse/MDEP-798 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.3.0 > > > Release Notes - Maven Shared Components - Version maven-dependency-tree-3.1.0 > h1. Improvement > * [MSHARED-339] - DependencyGraphBuilder does not provide verbose tree > * [MSHARED-491] - DependencyGraphBuilders shouldn't need reactorProjects > for resolving dependencies > * [MSHARED-519] - Maven31DependencyGraphBuilder (and others?) should not > download dependencies other than the pom > * [MSHARED-657] - plexus-component-annotation in line with > plexus-component-metadata > * [MSHARED-691] - Upgrade parent to 31 > * [MSHARED-788] - Add functionality to collect raw dependencies in Maven > 3+ > * [MSHARED-816] - Annotate DependencyNodes with dependency management > metadata > * [MSHARED-825] - Require Java 8 > * [MSHARED-850] - Upgrade org.eclipse.aether:aether-util dependency in > org.apache.maven.shared:maven-dependency-tree > * [MSHARED-852] - Add Exclusions to DependencyNode > * [MSHARED-853] - make build Reproducible > h1. Dependency upgrade > * [MSHARED-771] - Upgrade shared-component to version 33 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MDEP-798) Upgrade maven-dependency-tree from 3.0.1 to 3.1.0
[ https://issues.apache.org/jira/browse/MDEP-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500925#comment-17500925 ] Slawomir Jaranowski commented on MDEP-798: -- https://github.com/apache/maven-dependency-plugin/commit/3ed0f503f4935191e6e6eeb2be498c96a05222f2 > Upgrade maven-dependency-tree from 3.0.1 to 3.1.0 > - > > Key: MDEP-798 > URL: https://issues.apache.org/jira/browse/MDEP-798 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MDEP-798) Upgrade maven-dependency-tree from 3.0.1 to 3.1.0
[ https://issues.apache.org/jira/browse/MDEP-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-798. Resolution: Fixed > Upgrade maven-dependency-tree from 3.0.1 to 3.1.0 > - > > Key: MDEP-798 > URL: https://issues.apache.org/jira/browse/MDEP-798 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MDEP-798) Upgrade maven-dependency-tree from 3.0.1 to 3.1.0
Slawomir Jaranowski created MDEP-798: Summary: Upgrade maven-dependency-tree from 3.0.1 to 3.1.0 Key: MDEP-798 URL: https://issues.apache.org/jira/browse/MDEP-798 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500920#comment-17500920 ] Hudson commented on MNG-7428: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-661 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-661/4/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6960) Use RuntimeInformation instead of reading properties
[ https://issues.apache.org/jira/browse/MNG-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500919#comment-17500919 ] Hudson commented on MNG-6960: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-661 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-661/4/ > Use RuntimeInformation instead of reading properties > > > Key: MNG-6960 > URL: https://issues.apache.org/jira/browse/MNG-6960 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MDEP-797) Update transitive dependency commons-beanutils to 1.9.4
[ https://issues.apache.org/jira/browse/MDEP-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-797. Resolution: Fixed > Update transitive dependency commons-beanutils to 1.9.4 > --- > > Key: MDEP-797 > URL: https://issues.apache.org/jira/browse/MDEP-797 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MDEP-797) Update transitive dependency commons-beanutils to 1.9.4
Slawomir Jaranowski created MDEP-797: Summary: Update transitive dependency commons-beanutils to 1.9.4 Key: MDEP-797 URL: https://issues.apache.org/jira/browse/MDEP-797 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MDEP-796) Upgrade Maven Parent to 35
Slawomir Jaranowski created MDEP-796: Summary: Upgrade Maven Parent to 35 Key: MDEP-796 URL: https://issues.apache.org/jira/browse/MDEP-796 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500827#comment-17500827 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » master #7 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/7/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500820#comment-17500820 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-660 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-660/4/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6960) Use RuntimeInformation instead of reading properties
[ https://issues.apache.org/jira/browse/MNG-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500819#comment-17500819 ] Hudson commented on MNG-6960: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-660 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-660/4/ > Use RuntimeInformation instead of reading properties > > > Key: MNG-6960 > URL: https://issues.apache.org/jira/browse/MNG-6960 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6960) Use RuntimeInformation instead of reading properties
[ https://issues.apache.org/jira/browse/MNG-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500817#comment-17500817 ] Hudson commented on MNG-6960: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-676 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-676/4/ > Use RuntimeInformation instead of reading properties > > > Key: MNG-6960 > URL: https://issues.apache.org/jira/browse/MNG-6960 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500818#comment-17500818 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » PR-676 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-676/4/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500780#comment-17500780 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #5 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/5/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-7428. --- Resolution: Fixed Fixed with [48be53abbc7b44b045fe5039e6a5200a93f21b60|https://gitbox.apache.org/repos/asf?p=maven.git&a=commit&h=48be53abbc7b44b045fe5039e6a5200a93f21b60] in master and with [572d5260b9040bd063b3dc84ce51684b8379df10|https://gitbox.apache.org/repos/asf?p=maven.git&a=commit&h=572d5260b9040bd063b3dc84ce51684b8379df10] in 3.8.x. > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-mvnd] gnodet merged pull request #598: Bump xstream from 1.4.18 to 1.4.19
gnodet merged pull request #598: URL: https://github.com/apache/maven-mvnd/pull/598 -- 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] gnodet merged pull request #599: Adding note on removing quarantine flag on macOS
gnodet merged pull request #599: URL: https://github.com/apache/maven-mvnd/pull/599 -- 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] gnodet closed issue #594: Avoid caching parent with a version containing a property
gnodet closed issue #594: URL: https://github.com/apache/maven-mvnd/issues/594 -- 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] gnodet merged pull request #602: Avoid caching parent with a version containing a property, fixes #594
gnodet merged pull request #602: URL: https://github.com/apache/maven-mvnd/pull/602 -- 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] gnodet merged pull request #603: Remove unused logback-client.xml file
gnodet merged pull request #603: URL: https://github.com/apache/maven-mvnd/pull/603 -- 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] gnodet merged pull request #605: Add missing mvnDebug scripts
gnodet merged pull request #605: URL: https://github.com/apache/maven-mvnd/pull/605 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-7428) Upgrade Maven Parent to 35
Michael Osipov created MNG-7428: --- Summary: Upgrade Maven Parent to 35 Key: MNG-7428 URL: https://issues.apache.org/jira/browse/MNG-7428 Project: Maven Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-site] bmarwell commented on a change in pull request #291: Example alignment for methods arguments
bmarwell commented on a change in pull request #291: URL: https://github.com/apache/maven-site/pull/291#discussion_r818545891 ## File path: content/apt/developers/conventions/code.apt ## @@ -126,11 +126,26 @@ public class MyMojo // -- ... +// multiline arguments should be aligned for method declaration +protected void methodOne( String arg1, String arg2, + String arg3, String arg4 ) Review comment: No that is not what I meant. My idea was: EITHER chop down (one argument per line) OR everything in one line. This is example mixed. You have both more than one line and more than one argument per line. -- 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-build-cache-extension] mobiuscog opened a new pull request #7: Broken Link: Usage of .md causes apache.org documentation 404
mobiuscog opened a new pull request #7: URL: https://github.com/apache/maven-build-cache-extension/pull/7 The last link to "Remote Cache Setup" is correct for viewing in github, but means that the auto-generated webpage (https://maven.apache.org/extensions/maven-build-cache-extension/getting-started.html) on apache.org give a 404 due to a .md extension. Altering the extension to .html means that the apache.org webpage should work, but navigation within github will be broken. Therefore, I'm suggesting an absolute link. Perhaps there is a way to have these links automatically fixed up during webpage creation instead, such that navigation can work both on apache.org and within github.com. Following this checklist to help us incorporate your contribution quickly and easily: - [X] 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. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] 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. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [X] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
[
https://issues.apache.org/jira/browse/SUREFIRE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500625#comment-17500625
]
Slawomir Jaranowski commented on SUREFIRE-2033:
---
It is proper behavior in M5
If you have on dependencies list {{junit-platform-runner}}, surefire assume
that you want to run {{Junit5}} test by {{Junit4}} framework.
https://junit.org/junit5/docs/current/user-guide/#running-tests-junit-platform-runner
> Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
> ---
>
> Key: SUREFIRE-2033
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2033
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 3.0.0-M5
>Reporter: Robert James Oxspring
>Priority: Major
> Attachments: example.zip
>
>
> 3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
> using JUnit 4.
> In particular the attached project only has JUnit 5 dependencies:
> {code:java}
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.6.2
> test
>
>
> org.junit.platform
> junit-platform-runner
> 1.6.2
> test
>
> {code}
> and a JUnit 5 test:
> {code:java}
> package pkg;
> import org.junit.jupiter.api.Test;
> class JUnit5Test {
> @Test
> public void test() {
> }
> }{code}
> When the project is run with with older version (as far back as 2.22.0) the
> test is found and run, but 3.0.0-M5 fails to run any test:
> {code:java}
> % mvn test -Dsurefire.version=2.22.0 | tail
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.337 s
> [INFO] Finished at: 2022-03-03T09:42:27Z
> [INFO]
>
> {code}
>
> {code:java}
> % mvn test -Dsurefire.version=3.0.0-M1 | tail
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.708 s
> [INFO] Finished at: 2022-03-03T09:34:58Z
> [INFO]
>
> % mvn test -Dsurefire.version=3.0.0-M2 | tail
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.701 s
> [INFO] Finished at: 2022-03-03T09:36:26Z
> [INFO]
>
> % mvn test -Dsurefire.version=3.0.0-M3 | tail
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.612 s
> [INFO] Finished at: 2022-03-03T09:37:02Z
> [INFO]
>
> % mvn test -Dsurefire.version=3.0.0-M4 | tail
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.619 s
> [INFO] Finished at: 2022-03-03T09:37:37Z
> [INFO]
>
> % mvn test -Dsurefire.version=3.0.0-M5 | tail
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.344 s
> [INFO] Finished at: 2022-03-03T09:38:01Z
> [INFO]
> {code}
> Note the final run above using 3.0.0-M5 and logging: {{Tests run: 0}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
[
https://issues.apache.org/jira/browse/SUREFIRE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert James Oxspring updated SUREFIRE-2033:
Description:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies:
{code:java}
org.junit.jupiter
junit-jupiter-engine
5.6.2
test
org.junit.platform
junit-platform-runner
1.6.2
test
{code}
and a JUnit 5 test:
{code:java}
package pkg;
import org.junit.jupiter.api.Test;
class JUnit5Test {
@Test
public void test() {
}
}{code}
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.701 s
[INFO] Finished at: 2022-03-03T09:36:26Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M3 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.612 s
[INFO] Finished at: 2022-03-03T09:37:02Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M4 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.619 s
[INFO] Finished at: 2022-03-03T09:37:37Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M5 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.344 s
[INFO] Finished at: 2022-03-03T09:38:01Z
[INFO]
{code}
Note the final run above using 3.0.0-M5 and logging: {{Tests run: 0}}
was:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies:
{code:java}
org.junit.jupiter
junit-jupiter-engine
5.6.2
test
org.junit.platform
junit-platform-runner
1.6.2
test
{code}
and a JUnit 5 test:
{code:java}
package pkg;
import org.junit.jupiter.api.Test;
class JUnit5Test {
@Test
public void test() {
}
}{code}
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO
[jira] [Updated] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
[
https://issues.apache.org/jira/browse/SUREFIRE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert James Oxspring updated SUREFIRE-2033:
Description:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies:
{code:java}
org.junit.jupiter
junit-jupiter-engine
5.6.2
test
org.junit.platform
junit-platform-runner
1.6.2
test
{code}
and a JUnit 5 test:
{code:java}
package pkg;
import org.junit.jupiter.api.Test;
class JUnit5Test {
@Test
public void test() {
}
}{code}
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.701 s
[INFO] Finished at: 2022-03-03T09:36:26Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M3 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.612 s
[INFO] Finished at: 2022-03-03T09:37:02Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M4 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.619 s
[INFO] Finished at: 2022-03-03T09:37:37Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M5 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.344 s
[INFO] Finished at: 2022-03-03T09:38:01Z
[INFO]
{code}
Note the final run above using 3.0.0-M5 and logging: {{Tests run: 0}}
was:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies
(org.junit.jupiter:junit-jupiter-engine,
org.junit.platform:junit-platform-runner) and a JUnit 5 test (JUnit5Test.java):
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[jira] [Updated] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
[
https://issues.apache.org/jira/browse/SUREFIRE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert James Oxspring updated SUREFIRE-2033:
Description:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies
(org.junit.jupiter:junit-jupiter-engine,
org.junit.platform:junit-platform-runner) and a JUnit 5 test (JUnit5Test.java):
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.701 s
[INFO] Finished at: 2022-03-03T09:36:26Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M3 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.612 s
[INFO] Finished at: 2022-03-03T09:37:02Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M4 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.619 s
[INFO] Finished at: 2022-03-03T09:37:37Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M5 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.344 s
[INFO] Finished at: 2022-03-03T09:38:01Z
[INFO]
{code}
Note the final run above using 3.0.0-M5 and logging: {{Tests run: 0}}
was:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies
(org.junit.jupiter:junit-jupiter-engine,
org.junit.platform:junit-platform-runner) and a JUnit 5 test (JUnit5Test.java).
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] R
[jira] [Updated] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
[
https://issues.apache.org/jira/browse/SUREFIRE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert James Oxspring updated SUREFIRE-2033:
Description:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies
(org.junit.jupiter:junit-jupiter-engine,
org.junit.platform:junit-platform-runner) and a JUnit 5 test (JUnit5Test.java).
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.701 s
[INFO] Finished at: 2022-03-03T09:36:26Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M3 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.612 s
[INFO] Finished at: 2022-03-03T09:37:02Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M4 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.619 s
[INFO] Finished at: 2022-03-03T09:37:37Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M5 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.344 s
[INFO] Finished at: 2022-03-03T09:38:01Z
[INFO]
{code}
Note the final run above using 3.0.0-M5 and logging: {{Tests run: 0}}
was:
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies
(org.junit.jupiter:junit-jupiter-engine,
org.junit.platform:junit-platform-runner) and a JUnit 5 test (JUnit5Test.java).
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] Resu
[jira] [Created] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4
Robert James Oxspring created SUREFIRE-2033:
---
Summary: Regression: 3.0.0-M5 misidentifies JUnit 5 configuration
as JUnit 4
Key: SUREFIRE-2033
URL: https://issues.apache.org/jira/browse/SUREFIRE-2033
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support
Affects Versions: 3.0.0-M5
Reporter: Robert James Oxspring
Attachments: example.zip
3.0.0-M5 misidentifies a clearly JUnit 5 configuration and attempts to run
using JUnit 4.
In particular the attached project only has JUnit 5 dependencies
(org.junit.jupiter:junit-jupiter-engine,
org.junit.platform:junit-platform-runner) and a JUnit 5 test (JUnit5Test.java).
When the project is run with with older version (as far back as 2.22.0) the
test is found and run, but 3.0.0-M5 fails to run any test:
{code:java}
% mvn test -Dsurefire.version=2.22.0 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.337 s
[INFO] Finished at: 2022-03-03T09:42:27Z
[INFO]
{code}
{code:java}
% mvn test -Dsurefire.version=3.0.0-M1 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.708 s
[INFO] Finished at: 2022-03-03T09:34:58Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M2 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.701 s
[INFO] Finished at: 2022-03-03T09:36:26Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M3 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.612 s
[INFO] Finished at: 2022-03-03T09:37:02Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M4 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.619 s
[INFO] Finished at: 2022-03-03T09:37:37Z
[INFO]
% mvn test -Dsurefire.version=3.0.0-M5 | tail
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.344 s
[INFO] Finished at: 2022-03-03T09:38:01Z
[INFO]
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same
[
https://issues.apache.org/jira/browse/SUREFIRE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500615#comment-17500615
]
Nathan McDonald commented on SUREFIRE-2029:
---
Ah thanks forgot to include that, it's version 3.8.2. added to description of
issue
> Parallel execution but surefire.forkNumber is the same
> --
>
> Key: SUREFIRE-2029
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2029
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.22.2
>Reporter: Nathan McDonald
>Priority: Minor
>
> We have a multi module maven project, and due to our legacy architecture
> different modules are using the same underlying database.
> We are using the one db per fork strategy mentioned, and each test clears the
> database before running its test.
> This seems to work fine. But when running the full build on azure with:
> {noformat}
> mvn ... -T 1C -pl {modulesToBuild} -amd{noformat}
>
> See output kicking off build like:
> {noformat}
> [INFO] Using the MultiThreadedBuilder implementation with a thread count of
> 8{noformat}
>
> We occasionally see one long running test fail, and have traced cause that
> another test is running in parallel and clearing the database before long
> running test completes . This would only seem to be possible if parallel
> forks running but same surefire.forkNumber being set for multiple forks.
> Outputting logs of when tests start and end, with log outputting
> "Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7,
> where surefire.forkNumber is 3
> Looking at logs we can see test starts on thread/fork 1, clears db as
> expected, and 30 seconds later logs that it completes (with error that is
> shown later).
> But we can see just moments later, another test starts up and also clears the
> database, but is using same thread/fork:
> {noformat}
> 2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO
> e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
> 2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO
> e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1{1} - running
> setup for
> AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
> …
> {noformat}
> 2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO
> e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
> 2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0,
> Skipped: 0, Time elapsed: 24.715 s - in
> e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
> 2022-03-01T16:31:01.6124965Z [INFO] Running
> e.t.b.h.w.c.KeyInformationRestControllerIT{noformat}
> …
> {noformat}
> 2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO
> e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1{1} - complete
> test
> AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
> This isn't consistent though. Can see other cases where this works, but the
> logs found where it is working can see long running test running on separate
> fork:
> Thread#1\{3}
> Obviously there are separate threads/forks running here, so seems like
> somewhere between maven multi module and -T 1C, there is not always
> assigning unique forkNumber to each fork.
> I figure best practice is probably having separate modules not use same db,
> so possibly this issue is existing but not being hit by people as would only
> cause issue if same fork number used for separate modules on different
> databases.
> Still looking into issue our side will update if find workaround or more
> detailed information.
> Our surefire/failsafe config is in the root inherited by all other sub
> modules:
> {code:java}
>
>org.apache.maven.plugins
>maven-surefire-plugin
>
> 2
> @{argLine} -DforkNumber=${surefire.forkNumber}
> false
>
>
>
>org.apache.maven.plugins
>maven-failsafe-plugin
>
> 1
> @{argLine} -DforkNumber=${surefire.forkNumber}
> false
>
> ${project.build.directory}/surefire-reports
>
>
>
>
> integration-test
> verify
>
>
>
> {code}
> mvn version info:
> {noformat}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/apache-maven
> Java version: 11.0.13, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-11-openjdk-11.0.13.0.8-1.el7_9.x86_64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.53.1.el7.x86_64", arch: "amd64",
> family: "unix"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#82000
[jira] [Updated] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same
[
https://issues.apache.org/jira/browse/SUREFIRE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan McDonald updated SUREFIRE-2029:
--
Description:
We have a multi module maven project, and due to our legacy architecture
different modules are using the same underlying database.
We are using the one db per fork strategy mentioned, and each test clears the
database before running its test.
This seems to work fine. But when running the full build on azure with:
{noformat}
mvn ... -T 1C -pl {modulesToBuild} -amd{noformat}
See output kicking off build like:
{noformat}
[INFO] Using the MultiThreadedBuilder implementation with a thread count of
8{noformat}
We occasionally see one long running test fail, and have traced cause that
another test is running in parallel and clearing the database before long
running test completes . This would only seem to be possible if parallel forks
running but same surefire.forkNumber being set for multiple forks.
Outputting logs of when tests start and end, with log outputting
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where
surefire.forkNumber is 3
Looking at logs we can see test starts on thread/fork 1, clears db as expected,
and 30 seconds later logs that it completes (with error that is shown later).
But we can see just moments later, another test starts up and also clears the
database, but is using same thread/fork:
{noformat}
2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO
e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1{1} - running setup
for
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
…
{noformat}
2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO
e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0,
Skipped: 0, Time elapsed: 24.715 s - in
e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
2022-03-01T16:31:01.6124965Z [INFO] Running
e.t.b.h.w.c.KeyInformationRestControllerIT{noformat}
…
{noformat}
2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1{1} - complete test
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
This isn't consistent though. Can see other cases where this works, but the
logs found where it is working can see long running test running on separate
fork:
Thread#1\{3}
Obviously there are separate threads/forks running here, so seems like
somewhere between maven multi module and -T 1C, there is not always assigning
unique forkNumber to each fork.
I figure best practice is probably having separate modules not use same db, so
possibly this issue is existing but not being hit by people as would only cause
issue if same fork number used for separate modules on different databases.
Still looking into issue our side will update if find workaround or more
detailed information.
Our surefire/failsafe config is in the root inherited by all other sub modules:
{code:java}
org.apache.maven.plugins
maven-surefire-plugin
2
@{argLine} -DforkNumber=${surefire.forkNumber}
false
org.apache.maven.plugins
maven-failsafe-plugin
1
@{argLine} -DforkNumber=${surefire.forkNumber}
false
${project.build.directory}/surefire-reports
integration-test
verify
{code}
mvn version info:
{noformat}
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /usr/local/apache-maven
Java version: 11.0.13, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-11-openjdk-11.0.13.0.8-1.el7_9.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.53.1.el7.x86_64", arch: "amd64",
family: "unix"
{noformat}
was:
We have a multi module maven project, and due to our legacy architecture
different modules are using the same underlying database.
We are using the one db per fork strategy mentioned, and each test clears the
database before running its test.
This seems to work fine. But when running the full build on azure with:
{noformat}
mvn ... -T 1C -pl {modulesToBuild} -amd{noformat}
See output kicking off build like:
{noformat}
[INFO] Using the MultiThreadedBuilder implementation with a thread count of
8{noformat}
We occasionally see one long running test fail, and have traced cause that
another test is running in parallel and clearing the database before long
running test completes . This would only seem to be possible if parallel forks
running but same surefire.forkNumber being set for multip
[GitHub] [maven-surefire] olamy commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
olamy commented on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1057842967 > > > > does this include the commits from #460? > > > > > > > > > Yes @olamy, the content from #460 has been included here > > > > > > ok good know I was a bit confused as I could not see any reference to you in the commit. > > Yes, I got confused also, seems all the content from my PR was force-pushed and my mention as a contributor get lost 😞 Agree you deserve some credits for the work you did. @Tibor17 can you please fix that as @imonteroperez did a fair amount of work here and deserve to have some credits. Thanks -- 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] imonteroperez commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
imonteroperez commented on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1057839316 > > > does this include the commits from #460? > > > > > > Yes @olamy, the content from #460 has been included here > > ok good know I was a bit confused as I could not see any reference to you in the commit. Yes, I got confused also, seems all the content from my PR was force-pushed and my mention as a contributor get lost :disappointed: -- 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] olamy commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
olamy commented on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1057832226 > > does this include the commits from #460? > > Yes @olamy, the content from #460 has been included here ok good know I was a bit confused as I could not see any reference to you in the commit. -- 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] (MDEP-795) Update Jetty to 9.4.45.v20220203
[ https://issues.apache.org/jira/browse/MDEP-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-795. Fix Version/s: 3.3.0 Resolution: Fixed > Update Jetty to 9.4.45.v20220203 > > > Key: MDEP-795 > URL: https://issues.apache.org/jira/browse/MDEP-795 > Project: Maven Dependency Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.3.0 > > > New release of Jetty -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSHARED-1040) Require Java 8
[ https://issues.apache.org/jira/browse/MSHARED-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500603#comment-17500603 ] Hudson commented on MSHARED-1040: - Build failed in Jenkins: Maven » Maven TLP » maven-invoker » master #9 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-invoker/job/master/9/ > Require Java 8 > -- > > Key: MSHARED-1040 > URL: https://issues.apache.org/jira/browse/MSHARED-1040 > Project: Maven Shared Components > Issue Type: Task > Components: maven-invoker >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-invoker-3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MDEP-787) Allow ignoring non-test-scoped dependencies
[
https://issues.apache.org/jira/browse/MDEP-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MDEP-787:
-
Issue Type: New Feature (was: Bug)
> Allow ignoring non-test-scoped dependencies
> ---
>
> Key: MDEP-787
> URL: https://issues.apache.org/jira/browse/MDEP-787
> Project: Maven Dependency Plugin
> Issue Type: New Feature
>Affects Versions: 3.2.0, 3.3.0
>Reporter: Thorsten Glaser
>Assignee: Slawomir Jaranowski
>Priority: Blocker
> Fix For: 3.3.0
>
>
> This was found due to testing whether 3.3.0-SNAPSHOT fixes the regressions of
> 3.2.0 against 3.1.2 (it doesn’t, yet).
> After finding
> [https://maven.apache.org/guides/development/guide-testing-development-plugins.html]
> I was able to test the snapshot on the
> [https://github.com/tarent/extract-tool/tree/mdep753-snapshot] branch as well.
> This problem shows up:
> {quote}{{$ mvn dependency:analyze-only@analyse-dependency-usage}}
> {{[…]}}
> {{[WARNING] Non-test scoped test only dependencies found:}}
> {{[WARNING]
> com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:jar:2.13.1:compile}}
> {quote}
> This is “correct”: {{com.fasterxml.jackson.dataformat.yaml.YAMLFactory}} is
> {{{}import{}}}ed in the tests but only used via reflection in prod because
> it’s an optional (but not marked as optional so it’s included by default, but
> users can {{}} it and that’s supported and documented) dependency.
> This means it’s a false positive that cannot be expected to be handled by the
> test correctly and must be overridden in the POM.
> However, adding it as {{}} does not work ☹
> it’s probably the wrong overriding element, but
> [https://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html]
> does not have anything on how to override this particular warning.
> This is a *must-have* for, I hope, obvious reasons…
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-surefire] imonteroperez commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile
imonteroperez commented on pull request #440: URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1057827332 > does this include the commits from #460? Yes @olamy, the content from https://github.com/apache/maven-surefire/pull/460 has been included here -- 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] (MDEP-795) Update Jetty to 9.4.45.v20220203
[ https://issues.apache.org/jira/browse/MDEP-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MDEP-795: - Issue Type: Dependency upgrade (was: Task) > Update Jetty to 9.4.45.v20220203 > > > Key: MDEP-795 > URL: https://issues.apache.org/jira/browse/MDEP-795 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.3.0 > > > New release of Jetty -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSHARED-1040) Require Java 8
[ https://issues.apache.org/jira/browse/MSHARED-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1040. Fix Version/s: maven-invoker-3.2.0 Resolution: Fixed > Require Java 8 > -- > > Key: MSHARED-1040 > URL: https://issues.apache.org/jira/browse/MSHARED-1040 > Project: Maven Shared Components > Issue Type: Task > Components: maven-invoker >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-invoker-3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-invoker] slawekjaranowski merged pull request #45: [MSHARED-1040] Require Java 8
slawekjaranowski merged pull request #45: URL: https://github.com/apache/maven-invoker/pull/45 -- 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] (MDEP-795) Update Jetty to 9.4.45.v20220203
[ https://issues.apache.org/jira/browse/MDEP-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500573#comment-17500573 ] Hudson commented on MDEP-795: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » master #14 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/14/ > Update Jetty to 9.4.45.v20220203 > > > Key: MDEP-795 > URL: https://issues.apache.org/jira/browse/MDEP-795 > Project: Maven Dependency Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Trivial > > New release of Jetty -- This message was sent by Atlassian Jira (v8.20.1#820001)
