Google Git
Sign in
apache / maven-integration-testing / 99ede4e4d1a06bd67759017746fa169761f8ecc0
commit99ede4e4d1a06bd67759017746fa169761f8ecc0[log] [tgz]
authorTamas Cservenak <tamas@cservenak.net>Wed May 18 08:45:26 2022 +0200
committerGitHub <noreply@github.com>Wed May 18 08:45:26 2022 +0200
tree0b70479181470536c830923ce13c071b904b5052
parent84da51eb3bf7638aedac39e50daad8401f86cdbb [diff]
Mute Jetty (#159)

The HttpServer helper is used by two ITs:
* MavenITmng7470ResolverTransportTest
* MavenITmng5771CoreExtensionsTest

And it logs in case of MNG7470 for unknown reason. My bet would
be some static initing happening as side effect of OTHER ITs that
use Jetty directly, like MavenITmng5868NoDuplicateAttachedArtifacts.

Anyway, this sorts out Jetty logging.
1 file changed
tree: 0b70479181470536c830923ce13c071b904b5052
  1. core-it-suite/
  2. core-it-support/
  3. environments/
  4. src/
  5. .asf.yaml
  6. .gitattributes
  7. .gitignore
  8. pom.xml
  9. README.md
  10. run-its.bat
  11. 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