| commit | b730d3372bba97de5f86748a248c5e2abab34d04 | [log] [tgz] |
|---|---|---|
| author | Tamas Cservenak <tamas@cservenak.net> | Thu Jan 12 22:34:16 2023 +0100 |
| committer | GitHub <noreply@github.com> | Thu Jan 12 22:34:16 2023 +0100 |
| tree | 2d16d42af256e5eedff0837a38e6ec3e18934032 | |
| parent | a00a1c36d536684ad5b1ad5fbdc8196cde9178fb [diff] |
[MNG-7667] Fix Bootstrap IT (#230) This change extends Bootstrap IT (1st IT that fills in local repo) to hunt down some plugins that are bound in lifecycles provided by Maven under test. Changes: * the Bootstrap IT invokes only the phase where DownloadMojo is bound * DownloadMojo (the "bootstrap") changed to do "this or that": it either resolves all artifacts from provided file OR collects plugins for given project packaging plugin versions provided by tested Maven default lifecycle. * Split more Bootstrap project POMs, now we have 4 modules, we can add more (even extension if needed) --- https://issues.apache.org/jira/browse/MNG-7667
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