[wildfly-dev] Re: Move some dependencies to a new testbom in wildfly-core
Hi Lin,
On 24 Apr 2021, at 11:32, Lin Gao <lgao(a)redhat.com> wrote:
Hi folks,
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[1] 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[1] for more detail and context.
I like the idea overall.
However, I want to better understand the maintenance of that new BOM.
It contains dependencies that are in "test for WildFly core and “runtime” for
WildFly.
Past the 3 dependencies that you have identified, how can be keep these dependencies up to
date?
Next time, we want to add a test dependency to WildFly Core, we will have to first check
if WildFly is already depending on it in ’runtime’ scope. If that’s the case, it will go
to that testbom module. Otherwise, it will be added as a regular “test” scope dependency
in WIldFly Core.
Is that correct?
Thanks,
Jeff
--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/