| commit | b8afc98fc214c1eeab47356f27a153e2b2bbda30 | [log] [tgz] |
|---|---|---|
| author | Michael Osipov <michaelo@apache.org> | Sat Dec 26 19:08:32 2020 +0100 |
| committer | Michael Osipov <michaelo@apache.org> | Sun Jan 24 23:18:27 2021 +0100 |
| tree | f788bcc4afdeaf3bcd551aa81a4b051491b80a3b | |
| parent | 771b7385526211f57696fa57b3882e520aa88f1c [diff] |
[MNG-4991] LegacyRepositorySystem#injectProxy(repositories, proxies) doesn't evaluate non-proxy hosts Remove empty override of 'it-defaults' profile because it breaks MNG-4645. It is still reliable for both cases because: before MNG-4645) It relied on the fact that the override removes the global settings Maven Central definition of 'file:target/null' while Maven internally still added canonical Maven Central back. with MNG-4645) The empty profile override completely removes Maven Central definition which means that the mirror won't proxy a non-existing repository. This closes #95
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