commit | a0a042abeb7b1ad885e6277be1adbe1ea0cad76b | [log] [tgz] |
---|---|---|
author | Karl Heinz Marbaise <khmarbaise@apache.org> | Sun Sep 17 10:53:07 2017 +0000 |
committer | Karl Heinz Marbaise <khmarbaise@apache.org> | Sun Sep 17 10:53:07 2017 +0000 |
tree | 604849195ff2ed328ba2847548b32087421f804e | |
parent | efb34a0c70310424cf9f2e998a997ef2639839b8 [diff] |
[MJMOD-5] Usage of moduleName in describe/list goal / classpath usage in create goal o in describe/list goal change the moduleName into jmodFile using a default or can be given explicit by a property. Added IT's for direct call of the goals describe/list. o Removed the parameter classPath from the goal create. The command line will got the information from pathElements instead. git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1808613 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.