-
Bug
-
Resolution: Done
-
Critical
-
jbossws-jaxws-tools-maven.plugin-1.2.2.Final
-
None
There is a problem with fix https://github.com/jbossws/jaxws-tools-maven-plugin/commit/e166dab2b80f56990b965c25f8ba49e7ffd64bca#diff-c9758dd4ad22f24c99f55a716071ad9bR204 .
On Windows, this results in MANIFEST.MF containing paths for these additonal plugin dependencies like:
C:\Users\Administrator\.m2\repository\org\jboss\ws\jbossws-common-tools\1.2.4.Final\jbossws-common-tools-1.2.4.Final.jar C:\Users\Administrator\.m2\repository\log4j\log4j\1.2.14\log4j-1.2.14.jar C:\Users\Administrator\.m2\repository\gnu\getopt\java-getopt\1.0.13\java-getopt-1.0.13.jar
This eventually leads to misleading error Error: Could not find or load main class org.jboss.ws.tools.cmd.WSConsume. The real problem is that java is unable to load log4j and getopt libraries.
According to https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath the class-path entries are URLs, so above jars should be linked as:
file:/C:/Users/Administrator/.m2/repository/org/jboss/ws/jbossws-common-tools/1.2.4.Final/jbossws-common-tools-1.2.4.Final.jar file:/C:/Users/Administrator/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar file:/C:/Users/Administrator/.m2/repository/gnu/getopt/java-getopt/1.0.13/java-getopt-1.0.13.jar
or
file:///C:/Users/Administrator/.m2/repository/org/jboss/ws/jbossws-common-tools/1.2.4.Final/jbossws-common-tools-1.2.4.Final.jar file:///C:/Users/Administrator/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar file:///C:/Users/Administrator/.m2/repository/gnu/getopt/java-getopt/1.0.13/java-getopt-1.0.13.jar
- causes
-
JBEAP-16076 jaxws-tools-maven-plugin:1.2.2.Final fails on Windows machines while building a quickstart
- Closed