[JBoss JIRA] (WFLY-12287) 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
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin... ]
Eduardo Martins edited comment on WFLY-12287 at 7/16/19 11:10 AM:
------------------------------------------------------------------
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts, of user interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same, for many reasons WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
was (Author: emmartins):
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts, of user interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
> 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)
7 years
[JBoss JIRA] (WFLY-12287) 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
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin... ]
Eduardo Martins edited comment on WFLY-12287 at 7/16/19 11:10 AM:
------------------------------------------------------------------
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts, of user interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same. For many reasons WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
was (Author: emmartins):
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts, of user interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same, for many reasons WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
> 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)
7 years
[JBoss JIRA] (WFLY-12287) 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
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin... ]
Eduardo Martins edited comment on WFLY-12287 at 7/16/19 11:09 AM:
------------------------------------------------------------------
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts of interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees instead of the ones managed at WildFly.
was (Author: emmartins):
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts of interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus expected and should not be changed towards matching original artifacts dependency trees instead of the ones managed at WildFly.
> 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)
7 years
[JBoss JIRA] (WFLY-12287) 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
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin... ]
Eduardo Martins edited comment on WFLY-12287 at 7/16/19 11:09 AM:
------------------------------------------------------------------
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts of interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
was (Author: emmartins):
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts of interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees instead of the ones managed at WildFly.
> 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)
7 years
[JBoss JIRA] (WFLY-12287) 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
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin... ]
Eduardo Martins edited comment on WFLY-12287 at 7/16/19 11:09 AM:
------------------------------------------------------------------
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts, of user interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
was (Author: emmartins):
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts of interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus intended, and should not be changed towards matching original artifacts dependency trees, instead of the ones managed at WildFly.
> 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)
7 years
[JBoss JIRA] (WFLY-12287) 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
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12287?page=com.atlassian.jira.plugin... ]
Eduardo Martins commented on WFLY-12287:
----------------------------------------
[~jbliznak][~fburzigo] the WildFly BOMs should provide WildFly's dependency management parts of interest to:
- build apps ensuring compatibility
- debug apps with correct sources
- remotely test apps
Such use cases requires that BOMs are in sync with WildFly's dependency management, not original artifacts, which are not necessarly the same (for many reasons) since WildFly dependency management overrides (and sometimes breaks) original artifacts dependency trees.
The current behaviour is thus expected and should not be changed towards matching original artifacts dependency trees instead of the ones managed at WildFly.
> 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)
7 years
[JBoss JIRA] (WFCORE-4569) Default AuthenticationContext is not installed as the JVM wide default.
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-4569:
----------------------------------------
Summary: Default AuthenticationContext is not installed as the JVM wide default.
Key: WFCORE-4569
URL: https://issues.jboss.org/browse/WFCORE-4569
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 10.0.0.Beta2
Presently it is only installed on a deployment class loader basis but it should also be installed as a JVM wide default as some connections such as XA recovery don't use the deployment classloader.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years