[jboss-jira] [JBoss JIRA] (WFLY-13371) Clarify the MicroProfile subsystem dependency trees
Brian Stansberry (Jira)
issues at jboss.org
Sun Apr 12 13:34:25 EDT 2020
[ https://issues.redhat.com/browse/WFLY-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFLY-13371:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/13206
> Clarify the MicroProfile subsystem dependency trees
> ---------------------------------------------------
>
> Key: WFLY-13371
> URL: https://issues.redhat.com/browse/WFLY-13371
> Project: WildFly
> Issue Type: Task
> Components: Build System, MP Config, MP Fault Tolerance, MP Health, MP JWT, MP Metrics, MP OpenAPI, MP OpenTracing
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 20.0.0.Beta1
>
>
> The MP specs evolve at a different pace from the EE specs that make up the bulk of WildFly, so I want to maintain as much flexibility as possible in terms of how we package and distribute them. A small step in that direction is just being clear about the dependency trees for the various maven modules we use to provide these specs. IOWs, don't allow non-test-scope transitive dependencies to come through any dependencies on the artifacts coming from the WF build itself or from WF Core. Add global exclusions to any direct dependencies on those and add explicit dependencies for anything that was coming in transitively,
> Doing this would be good across the WF code base but here the focus is the MP maven modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list