[Hawkular-dev] Parent POM and Wildfly BOM

Thomas Segismont tsegismo at redhat.com
Tue Jul 21 11:40:31 EDT 2015


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.



More information about the hawkular-dev mailing list