commit | cc824ba8b42a10682e6683b0a36444e5a2be1bcc | [log] [tgz] |
---|---|---|
author | Michael Osipov <michaelo@apache.org> | Wed Jun 10 10:45:16 2020 +0200 |
committer | Michael Osipov <michaelo@apache.org> | Wed Jun 10 10:45:16 2020 +0200 |
tree | abeb9d6d3a8cab4b8e289d02388df8f96273d520 | |
parent | 96416e787d73a50eb27d4f5cf5ccb41b49458026 [diff] |
Fix ugly labels caused by 96416e787d73a50eb27d4f5cf5ccb41b49458026 When the test method name is solely 'test()' the output is: <issue> <className>.() Consistently modified a few tests to use the generic name 'testit()'.
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