[
https://issues.redhat.com/browse/WFCORE-4915?page=com.atlassian.jira.plug...
]
Kabir Khan edited comment on WFCORE-4915 at 4/17/20 6:51 AM:
-------------------------------------------------------------
[~brian.stansberry] I think for the transformer tests (if we need those for MP) kind of
rely on transitive dependencies behind the scenes for the dependencies of the legacy
controller. But if I remember correctly (I've not looked) those are more added at
runtime stuff. So I think it is possible to trim the tree for what is on the main
dependency classpath.
was (Author: kabirkhan):
[~brian.stansberry] I think for the transformer tests (if we need those for) kind of rely
on transitive dependencies behind the scenes for the dependencies of the legacy
controller. But if I remember correctly (I've not looked) those are more added at
runtime stuff. So I think it is possible to trim the tree for what is on the main
dependency classpath.
Tighten up the dependency tree of subsystem-test
------------------------------------------------
Key: WFCORE-4915
URL:
https://issues.redhat.com/browse/WFCORE-4915
Project: WildFly Core
Issue Type: Task
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
In general I'd like to tighten (aka eliminate) up the use of transitive dependencies
when various WildFly and WildFly Core maven modules depend on each other. Things should be
explicit so unwanted coupling cannot creep in.
The subsystem-test module is important in this regard as pretty much all extension
modules depend on it's pom. So I want it and its children and its direct dependencies
to only depend on other wf core modules directly, no transitive deps allowed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)