[GitHub] [maven-surefire] chalmagr closed pull request #544: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4
chalmagr closed pull request #544: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4 URL: https://github.com/apache/maven-surefire/pull/544 -- 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] chalmagr opened a new pull request, #516: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4
chalmagr opened a new pull request, #516: URL: https://github.com/apache/maven-surefire/pull/516 Changing the run listener to use the nameText value (for parameterized scenarios) to prevent invalid flake test reports (see https://github.com/chalmagr/surefire-flaky-report) 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/SUREFIRE) 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 `[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `SUREFIRE-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 install` 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 install`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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] chalmagr commented on pull request #516: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4
chalmagr commented on PR #516: URL: https://github.com/apache/maven-surefire/pull/516#issuecomment-1147062010 Please look at [Pull request 544](https://github.com/apache/maven-surefire/pull/544) since this one was closed after pushing master branch too early :) - will try to re-use now that I see the 'Reopen and comment' ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] chalmagr opened a new pull request, #544: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4
chalmagr opened a new pull request, #544: URL: https://github.com/apache/maven-surefire/pull/544 -- This PR resumes [516](https://github.com/apache/maven-surefire/pull/516) - while re-doing some changes had to do this on a separate branch instead for cleaner approach Changing the run listener to use the nameText value (for parameterized scenarios) to prevent invalid flake test reports (see https://github.com/chalmagr/surefire-flaky-report) 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/SUREFIRE) 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 `[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `SUREFIRE-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 install` 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 install`). 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 licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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-2091) Surefire ITs require install: verify should be sufficient
[
https://issues.apache.org/jira/browse/SUREFIRE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550299#comment-17550299
]
Olivier Lamy commented on SUREFIRE-2091:
duplicate of https://issues.apache.org/jira/browse/SUREFIRE-1956
> Surefire ITs require install: verify should be sufficient
> -
>
> Key: SUREFIRE-2091
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2091
> Project: Maven Surefire
> Issue Type: Wish
>Affects Versions: 3.0.0-M7
>Reporter: Herve Boutemy
>Priority: Major
>
> found during 3.0.0-M7 vote, when rebuilding
> then tested with 3.0.0-M8-SNAPSHOT before doing any install:
> {noformat}$ mvn -Prun-its clean verify
> ...
> [INFO] --- maven-invoker-plugin:3.2.2:run (integration-test) @
> maven-failsafe-plugin ---
> [INFO] Building: jetty-war-test-passing/pom.xml
> [INFO] run post-build script verify.bsh
> [INFO] The post-build script returned false.
> [INFO] jetty-war-test-passing/pom.xml ... FAILED
> (5.0 s)
> [INFO] Building: multiple-summaries-failing/pom.xml
> [INFO] multiple-summaries-failing/pom.xml ... SUCCESS
> (1.9 s)
> [INFO] Building: jetty-war-test-failing/pom.xml
> [INFO] run post-build script verify.bsh
> [INFO] The post-build script returned false.
> [INFO] jetty-war-test-failing/pom.xml ... FAILED
> (5.0 s)
> [INFO] Building: working-directory/pom.xml
> [INFO] The build exited with code 1. See
> /home/herve/projets/maven/sources/plugins/core/surefire/maven-failsafe-plugin/target/it/working-directory/build.log
> for details.
> [INFO] working-directory/pom.xml FAILED
> (2.0 s)
> [INFO] Building: multiple-summaries/pom.xml
> [INFO] The build exited with code 1. See
> /home/herve/projets/maven/sources/plugins/core/surefire/maven-failsafe-plugin/target/it/multiple-summaries/build.log
> for details.
> [INFO] multiple-summaries/pom.xml ... FAILED
> (2.0 s)
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 1, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * jetty-war-test-passing/pom.xml
> [ERROR] * jetty-war-test-failing/pom.xml
> [ERROR] * working-directory/pom.xml
> [ERROR] * multiple-summaries/pom.xml
> [INFO] -
> ...
> Caused by:
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> Missing:
> --
> 1) org.apache.maven.surefire:surefire-junit3:jar:3.0.0-M8-SNAPSHOT
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.surefire
> -DartifactId=surefire-junit3 -Dversion=3.0.0-M8-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.maven.surefire
> -DartifactId=surefire-junit3 -Dversion=3.0.0-M8-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> --
> 1 required artifact is missing.
> for artifact:
> org.apache.maven.surefire:surefire-junit3:jar:3.0.0-M8-SNAPSHOT
> from the specified remote repositories:
> central (https://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-surefire] olamy commented on pull request #543: [SUREFIRE-2091] don't require install to run ITs
olamy commented on PR #543: URL: https://github.com/apache/maven-surefire/pull/543#issuecomment-1147057536 there are some work here https://github.com/apache/maven-surefire/pull/479 -- 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] chalmagr closed pull request #516: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4
chalmagr closed pull request #516: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4 URL: https://github.com/apache/maven-surefire/pull/516 -- 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, #50: Bump maven-pmd-plugin from 3.16.0 to 3.17.0
dependabot[bot] opened a new pull request, #50: URL: https://github.com/apache/maven-invoker/pull/50 Bumps [maven-pmd-plugin](https://github.com/apache/maven-pmd-plugin) from 3.16.0 to 3.17.0. Release notes Sourced from https://github.com/apache/maven-pmd-plugin/releases;>maven-pmd-plugin's releases. 3.17.0 New features and improvements https://issues.apache.org/jira/browse/MPMD-309;>MPMD-309 - Add configuration option to show suppressed violations (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/59;>#59) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-332;>MPMD-332 - Support Java 18 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/63;>#63) https://github.com/adangel;>@adangel Bug Fixes https://issues.apache.org/jira/browse/MPMD-334;>MPMD-334 - Source Encoding parameter is ignored (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/64;>#64) https://github.com/laoseth;>@laoseth https://issues.apache.org/jira/browse/MPMD-342;>MPMD-342 - No debug log message issued when empty report shall be ski… (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/69;>#69) https://github.com/michael-o;>@michael-o Documentation updates https://issues.apache.org/jira/browse/MPMD-333;>MPMD-333 - Add release notes documentation (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/61;>#61) https://github.com/adangel;>@adangel Maintenance https://issues.apache.org/jira/browse/MPMD-336;>MPMD-336 - Replace deprecated calls to PMD (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/66;>#66) https://github.com/adangel;>@adangel Dependency updates https://issues.apache.org/jira/browse/MPMD-329;>MPMD-329 - Upgrade to PMD 6.45.0 https://issues.apache.org/jira/browse/MPMD-330;>MPMD-330 - Upgrade Maven Parent to 35 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/60;>#60) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-331;>MPMD-331 - Require Maven 3.2.5+ (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/60;>#60) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-337;>MPMD-337 - Upgrade Maven Parent to 36 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/67;>#67) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-338;>MPMD-338 - Upgrade to Doxia/Doxia Sitetools to 1.11.1 https://issues.apache.org/jira/browse/MPMD-339;>MPMD-339 - Upgrade plugins in ITs https://issues.apache.org/jira/browse/MPMD-340;>MPMD-340 - Upgrade Maven Reporting API/Impl to 3.1.0 https://issues.apache.org/jira/browse/MPMD-341;>MPMD-341 - Upgrade Maven Plugin Test Harness to 3.3.0 https://issues.apache.org/jira/browse/MPMD-343;>MPMD-343 - Upgrade to PMD 6.46.0 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/71;>#71) https://github.com/adangel;>@adangel Bump release-drafter/release-drafter from 5.19.0 to 5.20.0 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/68;>#68) https://github.com/dependabot;>@dependabot Bump release-drafter/release-drafter from 5.18.1 to 5.19.0 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/58;>#58) https://github.com/dependabot;>@dependabot Bump commons-io from 2.6 to 2.7 in /src/it/MPMD-318-auxclasspath-includeTests/module-a (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/65;>#65) https://github.com/dependabot;>@dependabot Bump slf4jVersion from 1.7.25 to 1.7.36 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/53;>#53) https://github.com/dependabot;>@dependabot Commits https://github.com/apache/maven-pmd-plugin/commit/a3add82e87bdeb3d0d99b0212452461db9986583;>a3add82 [maven-release-plugin] prepare release maven-pmd-plugin-3.17.0 https://github.com/apache/maven-pmd-plugin/commit/cf353c6b9cb14724ad677bcb60ac5e3c5ba6d92b;>cf353c6 (doc) Update release notes https://github.com/apache/maven-pmd-plugin/commit/027bf252a306a95b5ef2f42bd55430dfdd74ea0e;>027bf25 [MPMD-343] - Upgrade to PMD 6.46.0 https://github.com/apache/maven-pmd-plugin/commit/3585936ec00378cb4947947578c34eadb28e2b6a;>3585936 (doc) Update release notes https://github.com/apache/maven-pmd-plugin/commit/f26bec9283e0e0857f48deb8f2945bb807129407;>f26bec9 [MPMD-336] Replace deprecated calls to PMD https://github.com/apache/maven-pmd-plugin/commit/e82e92b3815fccf44ecd864c95518b5760b7436b;>e82e92b [MPMD-342] No debug log message issued when empty report shall be skipped and... https://github.com/apache/maven-pmd-plugin/commit/746779862fb4c4684dc275c382fcbac0b4a84b44;>7467798 [MPMD-337] Upgrade Maven Parent to 36
[GitHub] [maven-script-interpreter] dependabot[bot] opened a new pull request, #71: Bump groovy from 4.0.2 to 4.0.3
dependabot[bot] opened a new pull request, #71: URL: https://github.com/apache/maven-script-interpreter/pull/71 Bumps [groovy](https://github.com/apache/groovy) from 4.0.2 to 4.0.3. Commits See full diff in https://github.com/apache/groovy/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-parent] dependabot[bot] opened a new pull request, #64: Bump maven-pmd-plugin from 3.16.0 to 3.17.0
dependabot[bot] opened a new pull request, #64: URL: https://github.com/apache/maven-parent/pull/64 Bumps [maven-pmd-plugin](https://github.com/apache/maven-pmd-plugin) from 3.16.0 to 3.17.0. Release notes Sourced from https://github.com/apache/maven-pmd-plugin/releases;>maven-pmd-plugin's releases. 3.17.0 New features and improvements https://issues.apache.org/jira/browse/MPMD-309;>MPMD-309 - Add configuration option to show suppressed violations (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/59;>#59) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-332;>MPMD-332 - Support Java 18 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/63;>#63) https://github.com/adangel;>@adangel Bug Fixes https://issues.apache.org/jira/browse/MPMD-334;>MPMD-334 - Source Encoding parameter is ignored (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/64;>#64) https://github.com/laoseth;>@laoseth https://issues.apache.org/jira/browse/MPMD-342;>MPMD-342 - No debug log message issued when empty report shall be ski… (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/69;>#69) https://github.com/michael-o;>@michael-o Documentation updates https://issues.apache.org/jira/browse/MPMD-333;>MPMD-333 - Add release notes documentation (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/61;>#61) https://github.com/adangel;>@adangel Maintenance https://issues.apache.org/jira/browse/MPMD-336;>MPMD-336 - Replace deprecated calls to PMD (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/66;>#66) https://github.com/adangel;>@adangel Dependency updates https://issues.apache.org/jira/browse/MPMD-329;>MPMD-329 - Upgrade to PMD 6.45.0 https://issues.apache.org/jira/browse/MPMD-330;>MPMD-330 - Upgrade Maven Parent to 35 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/60;>#60) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-331;>MPMD-331 - Require Maven 3.2.5+ (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/60;>#60) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-337;>MPMD-337 - Upgrade Maven Parent to 36 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/67;>#67) https://github.com/adangel;>@adangel https://issues.apache.org/jira/browse/MPMD-338;>MPMD-338 - Upgrade to Doxia/Doxia Sitetools to 1.11.1 https://issues.apache.org/jira/browse/MPMD-339;>MPMD-339 - Upgrade plugins in ITs https://issues.apache.org/jira/browse/MPMD-340;>MPMD-340 - Upgrade Maven Reporting API/Impl to 3.1.0 https://issues.apache.org/jira/browse/MPMD-341;>MPMD-341 - Upgrade Maven Plugin Test Harness to 3.3.0 https://issues.apache.org/jira/browse/MPMD-343;>MPMD-343 - Upgrade to PMD 6.46.0 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/71;>#71) https://github.com/adangel;>@adangel Bump release-drafter/release-drafter from 5.19.0 to 5.20.0 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/68;>#68) https://github.com/dependabot;>@dependabot Bump release-drafter/release-drafter from 5.18.1 to 5.19.0 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/58;>#58) https://github.com/dependabot;>@dependabot Bump commons-io from 2.6 to 2.7 in /src/it/MPMD-318-auxclasspath-includeTests/module-a (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/65;>#65) https://github.com/dependabot;>@dependabot Bump slf4jVersion from 1.7.25 to 1.7.36 (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/53;>#53) https://github.com/dependabot;>@dependabot Commits https://github.com/apache/maven-pmd-plugin/commit/a3add82e87bdeb3d0d99b0212452461db9986583;>a3add82 [maven-release-plugin] prepare release maven-pmd-plugin-3.17.0 https://github.com/apache/maven-pmd-plugin/commit/cf353c6b9cb14724ad677bcb60ac5e3c5ba6d92b;>cf353c6 (doc) Update release notes https://github.com/apache/maven-pmd-plugin/commit/027bf252a306a95b5ef2f42bd55430dfdd74ea0e;>027bf25 [MPMD-343] - Upgrade to PMD 6.46.0 https://github.com/apache/maven-pmd-plugin/commit/3585936ec00378cb4947947578c34eadb28e2b6a;>3585936 (doc) Update release notes https://github.com/apache/maven-pmd-plugin/commit/f26bec9283e0e0857f48deb8f2945bb807129407;>f26bec9 [MPMD-336] Replace deprecated calls to PMD https://github.com/apache/maven-pmd-plugin/commit/e82e92b3815fccf44ecd864c95518b5760b7436b;>e82e92b [MPMD-342] No debug log message issued when empty report shall be skipped and... https://github.com/apache/maven-pmd-plugin/commit/746779862fb4c4684dc275c382fcbac0b4a84b44;>7467798 [MPMD-337] Upgrade Maven Parent to 36
[jira] [Updated] (SUREFIRE-2093) --enable-preview is not recognized
[
https://issues.apache.org/jira/browse/SUREFIRE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nir Lisker updated SUREFIRE-2093:
-
Description:
pom:
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.my.example
Testing
0.0.1-SNAPSHOT
3.10.1
3.0.0-M6
18
5.8.2
org.junit
junit-bom
${junit-version}
pom
import
org.junit.jupiter
junit-jupiter
test
Testing
org.apache.maven.plugins
maven-compiler-plugin
${maven-compiler-plugin-version}
${java-version}
--enable-preview
--add-modules=jdk.incubator.foreign
org.apache.maven.plugins
maven-surefire-plugin
${maven-surefire-plugin-version}
--enable-preview
--add-modules=jdk.incubator.foreign
--enable-native-access=ALL-UNNAMED
{code}
Under src/test/java add this class:
{code:java}
package com.my.example.simple;
import org.junit.jupiter.api.Test;
import jdk.incubator.foreign.ResourceScope;
public class ExampleTest {
@Test
public void test1() {
try (ResourceScope scope = ResourceScope.newConfinedScope()) {
} catch (Throwable e) {
e.printStackTrace();
throw e;
}
}
}{code}
Run Maven test.
The project compiles fine. The tests fail with:
Preview features are not enabled for com/my/example/simple/ExampleTest (class
file version 62.65535). Try running with '--enable-preview'
--enable-preview is already specified.
was:
pom:
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.my.example
Testing
0.0.1-SNAPSHOT
3.10.1
3.0.0-M6
18
5.8.2
org.junit
junit-bom
${junit-version}
pom
import
org.junit.jupiter
junit-jupiter
test
Testing
org.apache.maven.plugins
maven-compiler-plugin
${maven-compiler-plugin-version}
${java-version}
--enable-preview
--add-modules=jdk.incubator.foreign
org.apache.maven.plugins
maven-surefire-plugin
${maven-surefire-plugin-version}
--enable-preview
--add-modules=jdk.incubator.foreign
--enable-native-access=ALL-UNNAMED
{code}
Under src/test/java add this class:
{code:java}
package com.my.example.simple;
import org.junit.jupiter.api.Test;
import jdk.incubator.foreign.ResourceScope;
public class ExampleTest {
@Test
public void test1() {
try (ResourceScope scope = ResourceScope.newConfinedScope()) {
} catch (Throwable e) {
e.printStackTrace();
throw e;
}
}
}{code}
Run Maven test.
The project compiles fine. The tests fail with:
Preview features are not enabled for com/my/example/simple/ExampleTest (class
file version 62.65535). Try running with '--enable-preview'
--enable-preview is already specified.
> --enable-preview is not recognized
> --
>
> Key: SUREFIRE-2093
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2093
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6
>Reporter: Nir Lisker
>Priority: Major
>
> pom:
> {code:java}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> com.my.example
> Testing
> 0.0.1-SNAPSHOT
>
> 3.10.1
>
>
[jira] [Created] (SUREFIRE-2093) --enable-preview is not recognized
Nir Lisker created SUREFIRE-2093:
Summary: --enable-preview is not recognized
Key: SUREFIRE-2093
URL: https://issues.apache.org/jira/browse/SUREFIRE-2093
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 3.0.0-M6
Reporter: Nir Lisker
pom:
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.my.example
Testing
0.0.1-SNAPSHOT
3.10.1
3.0.0-M6
18
5.8.2
org.junit
junit-bom
${junit-version}
pom
import
org.junit.jupiter
junit-jupiter
test
Testing
org.apache.maven.plugins
maven-compiler-plugin
${maven-compiler-plugin-version}
${java-version}
--enable-preview
--add-modules=jdk.incubator.foreign
org.apache.maven.plugins
maven-surefire-plugin
${maven-surefire-plugin-version}
--enable-preview
--add-modules=jdk.incubator.foreign
--enable-native-access=ALL-UNNAMED
{code}
Under src/test/java add this class:
{code:java}
package com.my.example.simple;import org.junit.jupiter.api.Test;import
jdk.incubator.foreign.ResourceScope;public class ExampleTest { @Test
public void test1() {
try (ResourceScope scope = ResourceScope.newConfinedScope()) {
} catch (Throwable e) {
e.printStackTrace();
throw e;
}
}
}{code}
Run Maven test.
The project compiles fine. The tests fail with:
Preview features are not enabled for com/my/example/simple/ExampleTest (class
file version 62.65535). Try running with '--enable-preview'
--enable-preview is already specified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (SUREFIRE-2093) --enable-preview is not recognized
[
https://issues.apache.org/jira/browse/SUREFIRE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nir Lisker updated SUREFIRE-2093:
-
Description:
pom:
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.my.example
Testing
0.0.1-SNAPSHOT
3.10.1
3.0.0-M6
18
5.8.2
org.junit
junit-bom
${junit-version}
pom
import
org.junit.jupiter
junit-jupiter
test
Testing
org.apache.maven.plugins
maven-compiler-plugin
${maven-compiler-plugin-version}
${java-version}
--enable-preview
--add-modules=jdk.incubator.foreign
org.apache.maven.plugins
maven-surefire-plugin
${maven-surefire-plugin-version}
--enable-preview
--add-modules=jdk.incubator.foreign
--enable-native-access=ALL-UNNAMED
{code}
Under src/test/java add this class:
{code:java}
package com.my.example.simple;
import org.junit.jupiter.api.Test;
import jdk.incubator.foreign.ResourceScope;
public class ExampleTest {
@Test
public void test1() {
try (ResourceScope scope = ResourceScope.newConfinedScope()) {
} catch (Throwable e) {
e.printStackTrace();
throw e;
}
}
}{code}
Run Maven test.
The project compiles fine. The tests fail with:
Preview features are not enabled for com/my/example/simple/ExampleTest (class
file version 62.65535). Try running with '--enable-preview'
--enable-preview is already specified.
was:
pom:
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.my.example
Testing
0.0.1-SNAPSHOT
3.10.1
3.0.0-M6
18
5.8.2
org.junit
junit-bom
${junit-version}
pom
import
org.junit.jupiter
junit-jupiter
test
Testing
org.apache.maven.plugins
maven-compiler-plugin
${maven-compiler-plugin-version}
${java-version}
--enable-preview
--add-modules=jdk.incubator.foreign
org.apache.maven.plugins
maven-surefire-plugin
${maven-surefire-plugin-version}
--enable-preview
--add-modules=jdk.incubator.foreign
--enable-native-access=ALL-UNNAMED
{code}
Under src/test/java add this class:
{code:java}
package com.my.example.simple;import org.junit.jupiter.api.Test;import
jdk.incubator.foreign.ResourceScope;public class ExampleTest { @Test
public void test1() {
try (ResourceScope scope = ResourceScope.newConfinedScope()) {
} catch (Throwable e) {
e.printStackTrace();
throw e;
}
}
}{code}
Run Maven test.
The project compiles fine. The tests fail with:
Preview features are not enabled for com/my/example/simple/ExampleTest (class
file version 62.65535). Try running with '--enable-preview'
--enable-preview is already specified.
> --enable-preview is not recognized
> --
>
> Key: SUREFIRE-2093
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2093
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6
>Reporter: Nir Lisker
>Priority: Major
>
> pom:
> {code:java}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> com.my.example
> Testing
> 0.0.1-SNAPSHOT
>
> 3.10.1
>
> 3.0.0-M6
>
[jira] [Created] (MJAVADOC-717) Support Maven-Site approach
Stephen Crocker created MJAVADOC-717: Summary: Support Maven-Site approach Key: MJAVADOC-717 URL: https://issues.apache.org/jira/browse/MJAVADOC-717 Project: Maven Javadoc Plugin Issue Type: New Feature Reporter: Stephen Crocker The maven-javadoc-plugin currently creates its own independent website using Jquery, etc.. This means javadoc always looks separate from a site produced file. I would like to rewrite the plug-in so it uses the same Apache Velocity based template approach as the maven-site-plugin (and can be pointed at a maven-site-directory), the javadoc design should then sit within the same format as that generated output. I've noticed there is the 'java' and 'maven' style, I purpose the new approach is only taken for 'maven' projects with the existing code used for the 'java' type. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (MSKINS-97) Upgrade to Bootstrap 5.x
[ https://issues.apache.org/jira/browse/MSKINS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550249#comment-17550249 ] Stephen Crocker edited comment on MSKINS-97 at 6/5/22 8:50 PM: --- I would like to change the macro file layout to support the upgrade, things like the Navbar and footer sections have undergone quite a lot of modification. So I want to break them out into the following sections: * Header * Footer * Sidebar * Analytics * Social Media This then lets me raise a PR to change each file and helps group the templating we want to create. was (Author: JIRAUSER290518): I would like to change the macro file layout to support the upgrade, things like the Navbar and footer sections have undergone quite a lot of modification. So I want to break them out into the following sections: * Apache headers * Navbars * Sidebar * Analytics * Social Media This then lets me raise a PR to change each file and helps group the templating we want to create. > Upgrade to Bootstrap 5.x > > > Key: MSKINS-97 > URL: https://issues.apache.org/jira/browse/MSKINS-97 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Reporter: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0 > > > Next major of Fluido should be upgraded to Bootstrap 5.x which is *not* > backwards compatible to 2.x. See http://getbootstrap.com/migration/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (MSKINS-97) Upgrade to Bootstrap 5.x
[ https://issues.apache.org/jira/browse/MSKINS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550249#comment-17550249 ] Stephen Crocker edited comment on MSKINS-97 at 6/5/22 8:45 PM: --- I would like to change the macro file layout to support the upgrade, things like the Navbar and footer sections have undergone quite a lot of modification. So I want to break them out into the following sections: * Apache headers * Navbars * Sidebar * Analytics * Social Media This then lets me raise a PR to change each file and helps group the templating we want to create. was (Author: JIRAUSER290518): I would like to change the macro file layout to support the upgrade, things like the Navbar and footer sections have undergone quite a lot of modification. So I want to break them out into the following sections: * Apache headers * Navbars * Sidebar * Social Media This then lets me raise a PR to change each file and helps group the templating we want to create. > Upgrade to Bootstrap 5.x > > > Key: MSKINS-97 > URL: https://issues.apache.org/jira/browse/MSKINS-97 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Reporter: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0 > > > Next major of Fluido should be upgraded to Bootstrap 5.x which is *not* > backwards compatible to 2.x. See http://getbootstrap.com/migration/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-97) Upgrade to Bootstrap 5.x
[ https://issues.apache.org/jira/browse/MSKINS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550249#comment-17550249 ] Stephen Crocker commented on MSKINS-97: --- I would like to change the macro file layout to support the upgrade, things like the Navbar and footer sections have undergone quite a lot of modification. So I want to break them out into the following sections: * Apache headers * Navbars * Sidebar * Social Media This then lets me raise a PR to change each file and helps group the templating we want to create. > Upgrade to Bootstrap 5.x > > > Key: MSKINS-97 > URL: https://issues.apache.org/jira/browse/MSKINS-97 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Reporter: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0 > > > Next major of Fluido should be upgraded to Bootstrap 5.x which is *not* > backwards compatible to 2.x. See http://getbootstrap.com/migration/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-191) Update how project retreives bootstrap libraries
[ https://issues.apache.org/jira/browse/MSKINS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550248#comment-17550248 ] Stephen Crocker commented on MSKINS-191: I have submitted PR: [https://github.com/apache/maven-fluido-skin/pull/32] My goal by this change is to help enable future bootstrap upgrades, by simplifying version upgrades to the property values. This means we can focus on changes to the HTML generated by the system when new releases are performed. > Update how project retreives bootstrap libraries > > > Key: MSKINS-191 > URL: https://issues.apache.org/jira/browse/MSKINS-191 > Project: Maven Skins > Issue Type: New Feature >Reporter: Stephen Crocker >Priority: Major > > Currently the Bootstrap library is included within the project itself, > Bootstrap builds and deploys into the NPM repository. We can use the > com.github.eirslett:frontend-maven-plugin plugin to pull down the boostrap > plugins and setting the project up for packaging. This should simplify > updates to the boostrap library. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-fluido-skin] stevecrox opened a new pull request, #32: Mskins 191 dynamic library retrieval
stevecrox opened a new pull request, #32: URL: https://github.com/apache/maven-fluido-skin/pull/32 I have modified this branch so the repository no longer contains the JS files used, instead we make use of the com.github.eirslett:frontrend-plugin. This plug-in will pull down a copy of Node.JS into the build directory, this in turn allows us to call 'npm' and install bootstrap and anchor-js via NPM (since NPM Regsitry is how front end developers "release" libraries). This is performed in the 'generate-resources' phase. I had to bump the bootstrap version from 2.8.3 to 3.1.1, the classes uses dont appear to have changed, the big change was the removal of jQuery so this was removed from the project. I then added several executions to the maven-resources-plugin, these run in the 'process-resources' (phase after 'generate-resources'). The com.samaxes.maven:minify-maven-plugin plugin expects all the CSS/JS files to be in the same root directory, they are obviously now in different directories (e.g. src/main/resources and target/node_modules). So we use maven-resources-plugin to move them into a single directory (e.g. target/interim-minify). This lets the minify plug-in create the same build artefacts as before. -- 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] (MSKINS-191) Update how project retreives bootstrap libraries
Stephen Crocker created MSKINS-191: -- Summary: Update how project retreives bootstrap libraries Key: MSKINS-191 URL: https://issues.apache.org/jira/browse/MSKINS-191 Project: Maven Skins Issue Type: New Feature Reporter: Stephen Crocker Currently the Bootstrap library is included within the project itself, Bootstrap builds and deploys into the NPM repository. We can use the com.github.eirslett:frontend-maven-plugin plugin to pull down the boostrap plugins and setting the project up for packaging. This should simplify updates to the boostrap library. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SUREFIRE-2092) Show Passed/Failed Tests Count Summary of Multimodule Project in Console output
[ https://issues.apache.org/jira/browse/SUREFIRE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akshay pandey updated SUREFIRE-2092: Attachment: surefire-per-module-test result-summary-in-console.png surefire-multi-module-aggregate-summary-in-html-report.png > Show Passed/Failed Tests Count Summary of Multimodule Project in Console > output > --- > > Key: SUREFIRE-2092 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2092 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin, Maven Surefire Report Plugin >Reporter: akshay pandey >Priority: Minor > Attachments: > surefire-multi-module-aggregate-summary-in-html-report.png, > surefire-per-module-test result-summary-in-console.png > > > In the HTML report generated by the plugin with aggregate flag, a table is > generated in the report mentioning the count of total tests present in all > modules of the project, the number of tests passed, the number of tests > failed and the number of tests skipped. This is a single row table which > should be present in console output as well. > This expected behavior is similar to the existing behavior in case of module > wise test execution. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SUREFIRE-2092) Show Passed/Failed Tests Count Summary of Multimodule Project in Console output
akshay pandey created SUREFIRE-2092: --- Summary: Show Passed/Failed Tests Count Summary of Multimodule Project in Console output Key: SUREFIRE-2092 URL: https://issues.apache.org/jira/browse/SUREFIRE-2092 Project: Maven Surefire Issue Type: Improvement Components: Maven Surefire Plugin, Maven Surefire Report Plugin Reporter: akshay pandey In the HTML report generated by the plugin with aggregate flag, a table is generated in the report mentioning the count of total tests present in all modules of the project, the number of tests passed, the number of tests failed and the number of tests skipped. This is a single row table which should be present in console output as well. This expected behavior is similar to the existing behavior in case of module wise test execution. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MENFORCER-401) DependencyConvergence ignores exclusions
[
https://issues.apache.org/jira/browse/MENFORCER-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550224#comment-17550224
]
T. Mohme commented on MENFORCER-401:
Unfortunately I no longer have access to the project were I found the behavior
in question.
> DependencyConvergence ignores exclusions
>
>
> Key: MENFORCER-401
> URL: https://issues.apache.org/jira/browse/MENFORCER-401
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin, Standard Rules
>Affects Versions: 3.0.0
>Reporter: T. Mohme
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> In my project there is a transitive dependency on an artifact ("idlj-idl")
> with scope=provided that cannot be resolved (this probably is a different
> problem) - so far, so good (bad).
> {noformat}
> ...
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at com.acme:my-project:jar:1.0.0 ->
> io.quarkus:quarkus-flyway:jar:2.2.3.Final ->
> io.quarkus:quarkus-agroal:jar:2.2.3.Final ->
> io.quarkus:quarkus-narayana-jta:jar:2.2.3.Final ->
> org.jboss.narayana.jts:narayana-jts-integration:jar:5.12.0.Final ->
> org.jboss.narayana.jts:idlj-idl:jar:5.12.0.Final
> ...{noformat}
> Interestingly, `./mvnw dependency:tree` doesn't show this dependency.
> The tree descends only down to "narayana-jts-integration".
> When I exclude the unresolvable dependency ("idle-idl") from an artifact
> before it in the chain shown by the exception cause, this has no impact:
> {noformat}
>
> io.quarkus
> quarkus-agroal
>
>
> org.jboss.narayana.jts
> idlj-idl
>
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-jar-plugin] dependabot[bot] commented on pull request #41: Bump mavenVersion from 3.1.0 to 3.8.5
dependabot[bot] commented on PR #41: URL: https://github.com/apache/maven-jar-plugin/pull/41#issuecomment-1146808187 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] hboutemy closed pull request #41: Bump mavenVersion from 3.1.0 to 3.8.5
hboutemy closed pull request #41: Bump mavenVersion from 3.1.0 to 3.8.5 URL: https://github.com/apache/maven-jar-plugin/pull/41 -- 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] hboutemy opened a new pull request, #543: [SUREFIRE-2091] don't require install to run ITs
hboutemy opened a new pull request, #543: URL: https://github.com/apache/maven-surefire/pull/543 first commit fixes maven-failsafe-plugin ITs that run invoker surefire its that invoke Maven by hand still need to have an equivalent fix -- 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] (SUREFIRE-2091) Surefire ITs require install: verify should be sufficient
Herve Boutemy created SUREFIRE-2091:
---
Summary: Surefire ITs require install: verify should be sufficient
Key: SUREFIRE-2091
URL: https://issues.apache.org/jira/browse/SUREFIRE-2091
Project: Maven Surefire
Issue Type: Wish
Affects Versions: 3.0.0-M7
Reporter: Herve Boutemy
found during 3.0.0-M7 vote, when rebuilding
then tested with 3.0.0-M8-SNAPSHOT before doing any install:
{noformat}$ mvn -Prun-its clean verify
...
[INFO] --- maven-invoker-plugin:3.2.2:run (integration-test) @
maven-failsafe-plugin ---
[INFO] Building: jetty-war-test-passing/pom.xml
[INFO] run post-build script verify.bsh
[INFO] The post-build script returned false.
[INFO] jetty-war-test-passing/pom.xml ... FAILED (5.0
s)
[INFO] Building: multiple-summaries-failing/pom.xml
[INFO] multiple-summaries-failing/pom.xml ... SUCCESS
(1.9 s)
[INFO] Building: jetty-war-test-failing/pom.xml
[INFO] run post-build script verify.bsh
[INFO] The post-build script returned false.
[INFO] jetty-war-test-failing/pom.xml ... FAILED (5.0
s)
[INFO] Building: working-directory/pom.xml
[INFO] The build exited with code 1. See
/home/herve/projets/maven/sources/plugins/core/surefire/maven-failsafe-plugin/target/it/working-directory/build.log
for details.
[INFO] working-directory/pom.xml FAILED (2.0
s)
[INFO] Building: multiple-summaries/pom.xml
[INFO] The build exited with code 1. See
/home/herve/projets/maven/sources/plugins/core/surefire/maven-failsafe-plugin/target/it/multiple-summaries/build.log
for details.
[INFO] multiple-summaries/pom.xml ... FAILED (2.0
s)
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 1, Failed: 4, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * jetty-war-test-passing/pom.xml
[ERROR] * jetty-war-test-failing/pom.xml
[ERROR] * working-directory/pom.xml
[ERROR] * multiple-summaries/pom.xml
[INFO] -
...
Caused by:
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.maven.surefire:surefire-junit3:jar:3.0.0-M8-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.surefire
-DartifactId=surefire-junit3 -Dversion=3.0.0-M8-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.surefire
-DartifactId=surefire-junit3 -Dversion=3.0.0-M8-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
--
1 required artifact is missing.
for artifact:
org.apache.maven.surefire:surefire-junit3:jar:3.0.0-M8-SNAPSHOT
from the specified remote repositories:
central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MSHARED-955) Make MavenArchiver.parseOutputTimestamp static
[ https://issues.apache.org/jira/browse/MSHARED-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-955: -- Fix Version/s: maven-archiver-3.6.0 > Make MavenArchiver.parseOutputTimestamp static > -- > > Key: MSHARED-955 > URL: https://issues.apache.org/jira/browse/MSHARED-955 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Fix For: maven-archiver-3.6.0 > > > see > [https://github.com/apache/maven-ear-plugin/pull/10#discussion_r481152669] > where a new MavenArchiver object is being created (incorrectly) simply to > call this method. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MSHARED-1067) Improve the Reproducible Builds methods in Maven-Archiver
[
https://issues.apache.org/jira/browse/MSHARED-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSHARED-1067:
---
Fix Version/s: maven-archiver-3.6.0
> Improve the Reproducible Builds methods in Maven-Archiver
> -
>
> Key: MSHARED-1067
> URL: https://issues.apache.org/jira/browse/MSHARED-1067
> Project: Maven Shared Components
> Issue Type: Dependency upgrade
> Components: maven-archiver
>Affects Versions: maven-archiver-3.5.2
>Reporter: Jorge Solórzano
>Priority: Major
> Fix For: maven-archiver-3.6.0
>
>
> Maven Archiver 3.5.0 introduces some methods to parse the timestamp and
> configure the reproducible builds in plexus-archiver.
> The proposal for improvement is to leverage Java 8 APIs and deprecate older
> methods.
> # Deprecate the method
> {code:java}
> public Date parseOutputTimestamp( String outputTimestamp )
> {code}
> and introduce a new static method:
> {code:java}
> public static Optional parseBuildOutputTimestamp( String
> outputTimestamp )
> {code}
> # Deprecate the method
> {code:java}
> public Date configureReproducible( String outputTimestamp )
> {code}
> and introduce the method
> {code:java}
> public void configureReproducibleBuild( String outputTimestamp )
> {code}
> The new API return an Optional parsing the timestamp using
> java.time.format.DateTimeFormatter#ISO_INSTANT.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MSHARED-1066) Upgrade Plexus Archiver to 4.3.0
[ https://issues.apache.org/jira/browse/MSHARED-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-1066: --- Fix Version/s: maven-archiver-3.6.0 > Upgrade Plexus Archiver to 4.3.0 > > > Key: MSHARED-1066 > URL: https://issues.apache.org/jira/browse/MSHARED-1066 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Affects Versions: maven-archiver-3.5.2 >Reporter: Jorge Solórzano >Priority: Major > Fix For: maven-archiver-3.6.0 > > > Maven Archiver 3.6.0 should update to Plexus Archiver 4.3.0 (once it's > released), it contains fixes to reproducible modular jars and also target > Java 8. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MJAR-275) outputTimestamp not applied to module-info; breaks reproducible builds
[
https://issues.apache.org/jira/browse/MJAR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MJAR-275:
---
Fix Version/s: 3.3.0
> outputTimestamp not applied to module-info; breaks reproducible builds
> --
>
> Key: MJAR-275
> URL: https://issues.apache.org/jira/browse/MJAR-275
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: Mac OS X 10.14.6
> JDK 15 (build 15+36)
> JDK 11 (build 11.0.8+10)
>Reporter: Anand Beh
>Priority: Minor
> Fix For: 3.3.0
>
> Attachments: MCOMPILER-439.zip, Screenshot 2020-10-25 at 2.35.59
> PM.png
>
>
> Setting {{project.build.outputTimestamp}} to a fixed value allows creating
> reproducible builds per this guide:
> [https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> |https://maven.apache.org/guides/mini/guide-reproducible-builds.html]However,
> if one adds a module-info file to the project, reproducible builds break.
> This is caused by module-info.class using the latest timestamp and not
> {{project.build.outputTimestamp}}. I was able to identify the problem using
> diffoscope: [https://diffoscope.org/.|https://diffoscope.org/] With it I
> determined the timestamp across 2 builds was constant for all but the
> module-info.class:
>
> {code:java}
> -rw 2.0 fat 862 bl defN 20-Oct-17 00:40
> space/arim/libertybans/api/select/SelectionOrder.class
> │ -rw 2.0 fat 1113 bl defN 20-Oct-17 00:40
> space/arim/libertybans/api/select/SelectionOrderBuilder.class
> │ -rw 2.0 fat 2285 bl defN 20-Oct-17 00:40
> META-INF/maven/space.arim.libertybans/bans-api/pom.xml
> │ -rw 2.0 fat 74 bl defN 20-Oct-17 00:40
> META-INF/maven/space.arim.libertybans/bans-api/pom.properties
> │ --rw 2.0 fat 557 bl defN 20-Oct-25 12:39 module-info.class
> │ +-rw 2.0 fat 557 bl defN 20-Oct-25 12:41 module-info.class
> {code}
>
> Note the + and - which are diffoscope's way of indicating the difference
> between the .jar files. Here the {{project.build.outputTimestamp}} is on 17
> October. As shown, module-info has a "rebellious" timestamp.
>
> *EDIT:*
> Example project to reproduce the bug:
> [https://github.com/A248/MJAR-275|https://github.com/A248/MCOMPILER-439]
> (Renamed from [https://github.com/A248/MCOMPILER-439])
> Source code is also provided as an attachment below
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Closed] (MNGSITE-485) Expired signature in provided KEYS file on the download page
[ https://issues.apache.org/jira/browse/MNGSITE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNGSITE-485. -- Resolution: Fixed Key updated: http://pgp.mit.edu/pks/lookup?op=vindex=0x1A2A1C94BDE89688 > Expired signature in provided KEYS file on the download page > > > Key: MNGSITE-485 > URL: https://issues.apache.org/jira/browse/MNGSITE-485 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Baiyang Li >Assignee: Michael Osipov >Priority: Major > > Hey, > I met the same expired signature issue described in this close > [issue|https://issues.apache.org/jira/browse/MNGSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17410236#comment-17410236]. > When i follow the procedure to verify the signature using the KEYS file, both > provided on the maven's download page:: > * KEYS file import: gpg --import KEYS > * signature verification; gpg --verify .\apache-maven-3.8.2-bin.tar.gz.asc > .\apache-maven-3.8.2-bin.tar.gz > I've got the following message at the second step: > gpg: Good signature from "Michael Osipov (Java developer) > <1983-01...@gmx.net>" [expired] > gpg: aka "Michael Osipov " [expired] > gpg: Note: This key has expired! > According to the same procedure: "A signature is valid, if gpg verifies the > .asc as a good signature, and doesn't complain about expired or revoked > keys", so, technically, the signature is not valid. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MJAR-275) outputTimestamp not applied to module-info; breaks reproducible builds
[
https://issues.apache.org/jira/browse/MJAR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550177#comment-17550177
]
Herve Boutemy commented on MJAR-275:
https://github.com/codehaus-plexus/plexus-archiver/pull/205 backports the fix
for Java before 18
we need to release plexus-archiver 4.3.0 then update maven-jar-plugin to have a
situation where the reproducibility issue will be fixed with any JDK release
> outputTimestamp not applied to module-info; breaks reproducible builds
> --
>
> Key: MJAR-275
> URL: https://issues.apache.org/jira/browse/MJAR-275
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: Mac OS X 10.14.6
> JDK 15 (build 15+36)
> JDK 11 (build 11.0.8+10)
>Reporter: Anand Beh
>Priority: Minor
> Attachments: MCOMPILER-439.zip, Screenshot 2020-10-25 at 2.35.59
> PM.png
>
>
> Setting {{project.build.outputTimestamp}} to a fixed value allows creating
> reproducible builds per this guide:
> [https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> |https://maven.apache.org/guides/mini/guide-reproducible-builds.html]However,
> if one adds a module-info file to the project, reproducible builds break.
> This is caused by module-info.class using the latest timestamp and not
> {{project.build.outputTimestamp}}. I was able to identify the problem using
> diffoscope: [https://diffoscope.org/.|https://diffoscope.org/] With it I
> determined the timestamp across 2 builds was constant for all but the
> module-info.class:
>
> {code:java}
> -rw 2.0 fat 862 bl defN 20-Oct-17 00:40
> space/arim/libertybans/api/select/SelectionOrder.class
> │ -rw 2.0 fat 1113 bl defN 20-Oct-17 00:40
> space/arim/libertybans/api/select/SelectionOrderBuilder.class
> │ -rw 2.0 fat 2285 bl defN 20-Oct-17 00:40
> META-INF/maven/space.arim.libertybans/bans-api/pom.xml
> │ -rw 2.0 fat 74 bl defN 20-Oct-17 00:40
> META-INF/maven/space.arim.libertybans/bans-api/pom.properties
> │ --rw 2.0 fat 557 bl defN 20-Oct-25 12:39 module-info.class
> │ +-rw 2.0 fat 557 bl defN 20-Oct-25 12:41 module-info.class
> {code}
>
> Note the + and - which are diffoscope's way of indicating the difference
> between the .jar files. Here the {{project.build.outputTimestamp}} is on 17
> October. As shown, module-info has a "rebellious" timestamp.
>
> *EDIT:*
> Example project to reproduce the bug:
> [https://github.com/A248/MJAR-275|https://github.com/A248/MCOMPILER-439]
> (Renamed from [https://github.com/A248/MCOMPILER-439])
> Source code is also provided as an attachment below
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
