Re: [Hawkular-dev] Parent POM and Wildfly BOM
Le 20/07/2015 16:15, Peter Palaga a écrit :
Yes, I agree there exist maven modules inside HK componets projects
that
do not consume anything from WF BoM. ptrans is a good example of such
one. But I am still failing to see what your proposal is going to
improve in ptrans. WF BoM, regardless if it is imported in parent or
not, has no influence on ptrans as long as you do not add a dependency
on something from the WF BoM. ptrans does not depend on anything managed
"as long as" is the key. When we upgraded from Wildfly BOM version 8 to
9.CR1, I spent half a day getting down to a build issue in Metrics,
where the rest-tests module suddenly stopped working, just because the
new BOM broke dependency resolution.
in WF BoM, hence there is no impact. The compile class path of
ptrans
and the resulting jar stay the same regardless if WF BoM is imported in
HK parent or not. I see no impact at all.
I think I understand now how your proposal is supposed to work, but I
fail to see why it is better than the present state.
It boils down to control of dependency management. With the BOM auto
imported by the parent, we have to adapt to the Wildfly BOM choices. It
should not be like this.