[jboss-jira] [JBoss JIRA] (WFLY-10961) MP-OpenTracing Jaeger's can't see a concrete sender

[Juraci Paixão Kröhling (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paixão Kröhling updated WFLY-10961:
------------------------------------------
    Description: One of the last changes made to WF 14 was to split the MP-OpenTracing dependencies into smaller modules. This introduced a bug where the Jaeger Core module can't see a Sender from Jaeger Thrift. This is loaded via the Service Loader, so, Jaeger Core has to be shipped with Jaeger Thrift on the same module, to avoid a circular dependency (as Jaeger Thrift depends on classes defined on Jaeger Core).  (was: One of the last changes made to WF 14 was to split the dependencies into smaller modules. This introduced a bug where the Jaeger Core module can't see a Sender from Jaeger Thrift. This is loaded via the Service Loader, so, Jaeger Core has to be shipped with Jaeger Thrift on the same module, to avoid a circular dependency (as Jaeger Thrift depends on classes defined on Jaeger Core).)


> MP-OpenTracing Jaeger's can't see a concrete sender
> ---------------------------------------------------
>
>                 Key: WFLY-10961
>                 URL: https://issues.jboss.org/browse/WFLY-10961
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 14.0.0.Final
>            Reporter: Juraci Paixão Kröhling
>            Assignee: Juraci Paixão Kröhling
>
> One of the last changes made to WF 14 was to split the MP-OpenTracing dependencies into smaller modules. This introduced a bug where the Jaeger Core module can't see a Sender from Jaeger Thrift. This is loaded via the Service Loader, so, Jaeger Core has to be shipped with Jaeger Thrift on the same module, to avoid a circular dependency (as Jaeger Thrift depends on classes defined on Jaeger Core).



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)