[Hawkular-dev] Parent POM and Wildfly BOM

[Jay Shaughnessy]

I'm inclined to support Thomas's suggestion. Because we typically deploy 
to Wildfly I can understand why it was natural to suck the BOM up to 
parent.  But to give components some flexibility to control their own 
imports without having to override the parent or possibly add 
exclusions, it doesn't seem too bad to get the version of the BOM from 
the parent and then import at the component level.  And certainly it 
makes sense if the BOM is just not needed by the Hawkular component.  
Thomas has done the homework here.  If someone is is absolutely 100% 
against the change then we'll have to put it to a vote (or a flat out 
decision from above), but I suggest we make the change and move 
forward.  If we learn downstream that it was better the other way then 
I'm sure there will be enough groundswell to change it back.

Although, I think we can wait until after the next Hawkular release and 
then a PR should be sent for all affected components that may need to 
add the BOM dependency.


On 7/21/2015 11:40 AM, Thomas Segismont wrote:
> Le 21/07/2015 15:12, Jay Shaughnessy a écrit :
>> Too much snark in this thread.
>>
>> Is there a way that it can remain in the parent pom yet be
>> overridden/excluded as desired/required by metrics?  Maven typically
>> prefers the locally decl over an inherited decl.
> The only way you can "ignore" a BOM import is to re-declare it in your
> component parent POM with a scope != import. Works until Maven team
> decides "type=pom" + "scope=<yourchoice>" means something.
>
> I was not inclined to do this given that the proper solution is easy to
> implement.
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20150721/ea201831/attachment-0001.html