December 2018 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4155) jaxws-tools-maven-plugin handles windows paths in MANIFEST-MF incorrectly

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4155?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4155: ------------------------------ Git Pull Request: https://github.com/jbossws/jaxws-tools-maven-plugin/pull/7 Proposed fix at https://github.com/jbossws/jaxws-tools-maven-plugin/pull/7 > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4155) jaxws-tools-maven-plugin handles windows paths in MANIFEST-MF incorrectly

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4155: --------------------------------- Summary: 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 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} 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4151) Review dependency management in jbossws-cxf

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4151?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4151: ------------------------------ Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > Review dependency management in jbossws-cxf > ------------------------------------------- > > Key: JBWS-4151 > URL: https://issues.jboss.org/browse/JBWS-4151 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > As the project grows, some of the excludes in dependency management might become obsolete so we should review it: > # review excludes for current dependencies' versions > # properly use dependency management, ie. do not use exclusions on dependency when dependency management already manages them for that dependency (which overrides the predefined excludes) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4151) Review dependency management in jbossws-cxf

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4151?page=com.atlassian.jira.plugin.... ] Jan Blizňák edited comment on JBWS-4151 at 12/5/18 8:29 PM: ------------------------------------------------------------ For easier visual check what has changed with my changes please look at these comparisons: https://github.com/jbliznak/jbws-dependency-trees/compare/jdk8-before..jd... https://github.com/jbliznak/jbws-dependency-trees/compare/jdk11-before..j... https://github.com/jbliznak/jbws-dependency-trees/compare/jdk8-before..jd... https://github.com/jbliznak/jbws-dependency-trees/compare/jdk8-after..jdk... Namely, the generated trees are mostly identical with the bonus of less downloaded files to local repo during maven build; plus few fixes to be sure about what EE API is used. was (Author: jbliznak): For easier visual check what has changed with my changes please look at https://github.com/jbliznak/jbossws-cxf/commit/ed7960281a9c2e7abfb88b6591... Namely, the generated trees are mostly identical with the bonus of less downloaded files to local repo during maven build. > Review dependency management in jbossws-cxf > ------------------------------------------- > > Key: JBWS-4151 > URL: https://issues.jboss.org/browse/JBWS-4151 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > As the project grows, some of the excludes in dependency management might become obsolete so we should review it: > # review excludes for current dependencies' versions > # properly use dependency management, ie. do not use exclusions on dependency when dependency management already manages them for that dependency (which overrides the predefined excludes) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4154: --------------------------------- Summary: 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 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4153) Update target container to latest WF15

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4153?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4153: ----------------------------------- [~asoldano] I think it makes no sense merging it, you can close it (or reuse it - you should be able to add more commits to the PR) > Update target container to latest WF15 > -------------------------------------- > > Key: JBWS-4153 > URL: https://issues.jboss.org/browse/JBWS-4153 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Minor > > Move to latest WF15 version available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4153) Update target container to latest WF15

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/JBWS-4153?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-4153: --------------------------------------- [~jbliznak], do you still want the linked PR to be merged? > Update target container to latest WF15 > -------------------------------------- > > Key: JBWS-4153 > URL: https://issues.jboss.org/browse/JBWS-4153 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Minor > > Move to latest WF15 version available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4153) Update target container to latest WF15

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4153?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4153: ------------------------------ Assignee: Alessio Soldano (was: Jan Blizňák) > Update target container to latest WF15 > -------------------------------------- > > Key: JBWS-4153 > URL: https://issues.jboss.org/browse/JBWS-4153 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Minor > > Move to latest WF15 version available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4153) Update target container to latest WF15

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4153?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4153: ----------------------------------- WF15 Final was already released https://github.com/wildfly/wildfly/releases/tag/15.0.0.Final, so this jira can be used to remove support for WF12 and add support for released WF15 and developed WF16 Alpha1-SNAPSHOT > Update target container to latest WF15 > -------------------------------------- > > Key: JBWS-4153 > URL: https://issues.jboss.org/browse/JBWS-4153 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > > Move to latest WF15 version available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2018