[
https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin...
]
Eduardo Martins commented on WFLY-12287:
----------------------------------------
Don't think there is anything wrong:
* org.slf4j:jcl-over-slf4j:jar is a WildFly's managed dependency, thus not banned, and
it's not excluded from org.apache.cxf:cxf-rt-transports-http-hc, see
https://github.com/wildfly/wildfly/blob/master/pom.xml#L3006
We could enforce an exclusion on BOMs side but unless it's presence in dependency tree
introduces any harm I would prefer to don't introduce a manually maintained exclusion
* org.slf4j:slf4j-log4j12:jar is a banned dependency on WildFly's dependency
management, see
https://github.com/wildfly/wildfly/blob/master/pom.xml#L8099
The two bottom dependencies in the BOM builder (see
https://github.com/wildfly/boms/blob/master/client/jaxws-client/pom.xml#L99 ) are
replacements for the banned dependency
[~jim.ma] can you please confirm ^^ is ok
Remove transitive org.slf4j:jcl-over-slf4j:jar from dependency tree
and include org.slf4j:slf4j-log4j12:jar when using org.wildfly:wildfly-jaxws-client-bom as
direct a dependency
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-12287
URL:
https://issues.jboss.org/browse/WFLY-12287
Project: WildFly
Issue Type: Bug
Components: Quickstarts, Web Services
Affects Versions: 17.0.1.Final
Reporter: Fabio Burzigotti
Assignee: Eduardo Martins
Priority: Major
When using Wildfly JAXWS Client BOM an unwanted reference to org.slf4j:jcl-over-slf4j:jar
appears in the dependency tree even it is explicitly excluded by
org.jboss.ws.cxf:jbossws-cxf POM. Instead there's no reference to
org.slf4j:slf4j-log4j12:jar while it seems it's needed by
org.jboss.ws.cxf:jbossws-cxf-client:jar
--
This message was sent by Atlassian Jira
(v7.12.1#712002)