[Hawkular-dev] Importing JBoss BoMs to Hawkular Parent

Peter Palaga ppalaga at redhat.com
Mon Feb 16 08:37:40 EST 2015


Hi John,

was there any discussion (that I may have missed during my PTO) around 
importing the jboss-javaee-7.0-with-all to parent? Could you please 
justify the idea once again for me?

I must say I'd veto the change if I was at work. Here is why:

(1) Tying to WildFly only. The change might be understood like this. I 
am not sure this was your intention, but please consider that importing 
another similar BoM (say EAP BoM) in paralel would in fact be extremely 
impractical, because of version conflicts.

(2) Pulling in many artifacts we do not use, do not need, some of them 
maybe being implicitly unwanted ones. But having them in parent is 
actually legalizing them without any discussion. That is especially 
dangerous.

(3) "Political" dependence on WildFly. WildFly may do changes at any 
time in their BoMs that may have bad consequences in Hawkular.

The bottom line is that it would be much better to avoid situations this 
through discussing proposals prior to merging them in master. I have 
proposed explicit parent contribution rules in 
https://github.com/hawkular/hawkular-parent-pom/pull/13 Feel free to 
comment on them.


More information about the hawkular-dev mailing list