Google Git
Sign in
apache / maven-jmod-plugin / 10f6474b7dcc8eda9199d008c0f008836e3ce649
commit10f6474b7dcc8eda9199d008c0f008836e3ce649[log] [tgz]
authorJonathan Leitschuh <Jonathan.Leitschuh@gmail.com>Mon Feb 10 19:05:33 2020 -0500
committerSylwester Lachiewicz <slachiewicz@apache.org>Sun Dec 12 02:09:15 2021 +0100
tree0152a3a9006ac88d2f831cf745d13ac1a27454e6
parentfbe5b0c6ef5aa17be5ca523635685b832ec8303a [diff]
Use HTTPS instead of HTTP to resolve dependencies

This fixes a security vulnerability in this project where the `pom.xml`
files were configuring Maven to resolve dependencies over HTTP instead of
HTTPS.

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>
1 file changed
tree: 0152a3a9006ac88d2f831cf745d13ac1a27454e6
  1. src/
  2. .asf.yaml
  3. .gitignore
  4. deploySite.sh
  5. Jenkinsfile
  6. pom.xml
  7. README.md
README.md

How to run Integration Tests with JDK 9

If you running your Maven installation with a different JDK than JDK 9 you have give the JDK 9 path via the command line:

mvn clean verify -Prun-its -Dinvoker.javaHome=JDK9JAVAHOME

The reason behind this is simply cause Maven JMod Plugin will call jmod tool of the JDK which is needed to be found. Otherwise none of the integration tests can work.