[Hawkular-dev] Importing JBoss BoMs to Hawkular Parent

[Jay Shaughnessy]

What is the better alternative at the moment, to have each component's 
root pom import the bom?  Either way we sort of end up with the same 
thing.Perhaps we could have profiles for the different deployment envs, 
with WFly as our first one?  Not sure, but the benefit of all components 
layering on the same provided deps seems important.

On 2/16/2015 8:37 AM, Peter Palaga wrote:
> 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.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>