Google Git
Sign in
apache / maven-integration-testing / dd92c36164cb013a6c3111bf8e6b47b5ea064526
commitdd92c36164cb013a6c3111bf8e6b47b5ea064526[log] [tgz]
authorTamas Cservenak <tamas@cservenak.net>Fri May 19 20:33:57 2023 +0200
committerGitHub <noreply@github.com>Fri May 19 20:33:57 2023 +0200
tree1728593cb3706cc4be4d4e7a90f50692757aff39
parent367b2101f4c49e6b807f16260a78fdb1da02f608 [diff]
[MNG-7788] Fix for IT MavenITmng6562WarnDefaultBindings (#261)

The MavenITmng6562WarnDefaultBindings IT tests new Maven4 feature "fail on severity" (for WARN level).

The stub core plugin maven-resources-plugin depends on maven-compat, and it emits plugin validation warning.

BEFORE MNG-7788 was merged, the warnings were logged AFTER build summary and was not picked up by "fail on severity".

AFTER MNG-7788 merged, it causes that warnings breaks the build, as "fail on severity" is set to WARN level.

Fix:
The stub maven-resources-plugin does NOT need to depend on maven-compat, what it really needs is maven-core (for MavenProject).
1 file changed
tree: 1728593cb3706cc4be4d4e7a90f50692757aff39
  1. .github/
  2. core-it-suite/
  3. core-it-support/
  4. environments/
  5. src/
  6. .asf.yaml
  7. .gitattributes
  8. .gitignore
  9. Jenkinsfile
  10. pom.xml
  11. README.md
  12. run-its.bat
  13. run-its.sh
README.md

Maven Core Integration Tests

https://maven.apache.org/core-its/

If you want to run the integration tests against a custom build of Maven use the following command:

mvn clean install -Prun-its -Dmaven.repo.local=`pwd`/repo -DmavenDistro=/path/to/apache-maven-dist.zip

or if behind a proxy

mvn clean install -Prun-its -Dmaven.repo.local=`pwd`/repo -DmavenDistro=/path/to/apache-maven-dist.zip -Dproxy.active=true -Dproxy.type=http -Dproxy.host=... -Dproxy.port=... -Dproxy.user=... -Dproxy.pass=...

Using the script

Build Maven core with the profile -PversionlessMavenDist

Now Run the script: sh ./run-its.sh

Maven Developers List: dev@maven.apache.org