Note that there's already a thread on this. This one was in list
moderation and I approved it before seeing the other thread. So let's keep
the discussion on the other thread.
On Tue, Apr 27, 2021 at 1:47 PM Lin Gao <aoingl(a)gmail.com> wrote:
WildFly-core's root pom acting as BOM and getting imported into
WildFly's root pom via dependencyManagement
to be able to align the shared dependencies, it works good most of the
time but has problems on dependencies
which are used only for testing in wildfly-core but are used in production
in WildFly full. Please refer to the
Jira issue for more detail and context.
There is a PR open to address that problem by introducing a *testbom*
which contains such dependencies. Any
module depending on such dependencies can add the *testbom* with an
The PR tries to move the following dependencies from WildFly-core's root
pom to the new created *testbom*:
Once the PR gets approved, it needs any project depending on
wildfly-core's root pom to check, like adding
the commons-io:commons-io dependency in case of WildFly full.
Does anyone see problems with such a move? Thank you !
Senior Software Engineer
JBoss Sustaining Engineering Team
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Principal Architect, Red Hat JBoss EAP
If I am writing outside of normal office hours, it is my choice; you do not
need to do the same