| commit | 8c9cb886aa19022dc18d82582144befc3dc2e970 | [log] [tgz] |
|---|---|---|
| author | Tamas Cservenak <tamas@cservenak.net> | Wed May 11 22:59:02 2022 +0200 |
| committer | GitHub <noreply@github.com> | Wed May 11 22:59:02 2022 +0200 |
| tree | 28a391276f71db4c94a34d582e0e1bd9ae462b24 | |
| parent | cd63b2b385c12634d5448f45d28db008f2c3d6f2 [diff] |
[MNG-7470] mvn 3.9+ IT that uses wagon (default) and native transport (#158) An IT for Maven 3.9+ that "exercise" both resolver transport: wagon and native (so we have 2 tests both forcing transport with `-Dmaven.resolver.transport` one wagon (which is default, but setting is there to be explicit) and once native. It builds a project that needs a plugin (to pull it will use set transport), and that plugin will use resolver as well to resolve set artifact. If any of these fails, maven project fails. Related fix: https://github.com/apache/maven/pull/732 (jn maven-3.9.x and master)
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