commit | 1a1e2cc8eb42414ad41dbd61a601d476b1381421 | [log] [tgz] |
---|---|---|
author | Michael Osipov <michaelo@apache.org> | Sat Dec 26 22:04:21 2020 +0100 |
committer | Michael Osipov <michaelo@apache.org> | Sat Dec 26 22:08:08 2020 +0100 |
tree | 2a06d21e2fb132ff67c3377524e5564b1be4e473 | |
parent | 7dffabb00ab739258b8b4da215b4efea16a49ae5 [diff] |
[MNG-4963] Parent POM not downloaded when settings define global mirror and one snapshot repo but no other release repository This IT was written with implicit black magic in mind. A mirror simply exchanges a URL of repo with another one while retaining the entire config for releases/snapshots. Logically this IT should have failed because there is no release repo. But it works because Maven adds Maven Central internally which is a release repo. For MNG-4645 one has to add a release repo in the settings to mimic that behavior. This closes #96
https://maven.apache.org/core-its/
If you want to run the integration tests against a custom build of Maven use the following command:
export MAVENCODEBASE=<path-to-maven-codebase>
You can choose to build the maven project from here with:
mvn verify -P local-it -f "$MAVENCODEBASE"
Now run (don't forget to update the versions!)
mvn clean install -Prun-its,embedded -Dmaven.repo.local=`pwd`/repo -DmavenDistro="$MAVENCODEBASE/apache-maven/target/apache-maven-<VERSION>-bin.zip" -DwrapperDistroDir="$MAVENCODEBASE/apache-maven/target" -DmavenWrapper="$MAVENCODEBASE/maven-wrapper/target/maven-wrapper.jar"
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