[jboss-jira] [JBoss JIRA] (WFLY-10846) OpenTracing modules need jboss-api=private in module.xml
Brian Stansberry (JIRA)
issues at jboss.org
Wed Aug 15 11:31:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved WFWIP-108 to WFLY-10846:
-----------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-10846 (was: WFWIP-108)
Component/s: MP OpenTracing
(was: MP Request Tracing)
> OpenTracing modules need jboss-api=private in module.xml
> --------------------------------------------------------
>
> Key: WFLY-10846
> URL: https://issues.jboss.org/browse/WFLY-10846
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Reporter: Brian Stansberry
> Assignee: Juraci Paixão Kröhling
> Priority: Blocker
>
> The 3 modules added in https://github.com/wildfly/wildfly/pull/11454 need this in their module.xml:
> {code}
> <properties>
> <property name="jboss.api" value="private"/>
> </properties>
> {code}
> This ensures that we log a WARN if the user tries to _directly_ use these modules as application dependencies. (Directly == via their own deployment configuration, not via our subsystem wiring them in as a dependency. See [1] for the impl.)
> These log WARNs and the setting in the file itself are important both to prevent the user making mistakes and as the formal the mechanism by which we control how we support use of the various libraries we ship in the appserver. Marking modules private, deprecated etc gives us the freedom to rework implementations without worrying about breaking unexpected uses of things.
> [1] https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/org/jboss/as/server/moduleservice/ModuleLoadService.java#L69
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list