[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec
by Alessio Soldano (Jira)
[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-4154:
----------------------------------
Assignee: Jim Ma
> jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec
> ----------------------------------------------------------------------------------------
>
> Key: JBWS-4154
> URL: https://issues.jboss.org/browse/JBWS-4154
> Project: JBoss Web Services
> Issue Type: Bug
> Affects Versions: jbossws-cxf-5.2.4.Final
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Priority: Major
>
> dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API:
> org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile
> org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile
> The former is brought in by:
> {code:java}
> +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile
> | \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile
> | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile
> {code}
> I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this)
> Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossw...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
- 1
- 0
[JBoss JIRA] (JBWS-4155) jaxws-tools-maven-plugin handles windows paths in MANIFEST-MF incorrectly
by Alessio Soldano (Jira)
[ https://issues.jboss.org/browse/JBWS-4155?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on JBWS-4155:
---------------------------------------
[~jim.ma], we should tag/release a new version of jaxws-tools-maven-plugin because of this
> jaxws-tools-maven-plugin handles windows paths in MANIFEST-MF incorrectly
> -------------------------------------------------------------------------
>
> Key: JBWS-4155
> URL: https://issues.jboss.org/browse/JBWS-4155
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxws-tools-maven-plugin
> Affects Versions: jbossws-jaxws-tools-maven.plugin-1.2.2.Final
> Reporter: Jan Blizňák
> Assignee: Jan Blizňák
> Priority: Critical
>
> There is a problem with fix https://github.com/jbossws/jaxws-tools-maven-plugin/commit/e166dab2b80f56... .
> On Windows, this results in MANIFEST.MF containing paths for these additonal plugin dependencies like:
> {code:java}
> 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
> {code}
> 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#class... the class-path entries are URLs, so above jars should be linked as:
> {code:java}
> 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
> {code}
> or {code:java}
> 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
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
- 1
- 0