tag | f3d6b817fae39e75fcfe09dd5424983f2066032a | |
---|---|---|
tagger | Karl Heinz Marbaise <khmarbaise@apache.org> | Sun Sep 17 11:29:24 2017 +0000 |
object | 0a984f151f9320ce612bfc0d43b4d577ab5f1a68 |
maven-jmod-plugin-3.0.0-alpha-1
commit | 0a984f151f9320ce612bfc0d43b4d577ab5f1a68 | [log] [tgz] |
---|---|---|
author | Karl Heinz Marbaise <khmarbaise@apache.org> | Sun Sep 17 11:29:24 2017 +0000 |
committer | Karl Heinz Marbaise <khmarbaise@apache.org> | Sun Sep 17 11:29:24 2017 +0000 |
tree | b069f2cdaf4bee490855f1add6db87e51a55cdc7 | |
parent | fb8baba28b671642aad0b21289d17a3ba9b3b9b7 [diff] | |
parent | 1de07ffef4042da453d23ad3e8e27fc552de8c1b [diff] |
[maven-release-plugin] copy for tag maven-jmod-plugin-3.0.0-alpha-1 git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/tags/maven-jmod-plugin-3.0.0-alpha-1@1808624 13f79535-47bb-0310-9956-ffa450edef68
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.