[
https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin...
]
Fabio Burzigotti commented on WFLY-12287:
-----------------------------------------
[~jamezp], agree on slf4j-api just representing a facade, but in this very case the
slf4j-log4j12 artifact is a dependency of jbossws-cxf-client which in turn is pulled in by
the client BOM definition. So, basically, the BOM generation seems to be overriding a
(clientside) artifact level inclusion.
[~emmartins], regarding the jcl-over-slf4j dependency, that is as well a BOM generation
side effect: it is not banned from the server definition but it is excluded at component
level (jbossws-cxf).
[~emmartins], what you state about introducing manually maintained BOM configuration makes
sense too, so agreeing with [~jbliznak] here, and probably we also need to document that
existing projects POMs could need some kind of adjustment as dep tree is going to change
when using the Wildfly JAXWS Client BOM.
WDYT?
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)