[Hawkular-dev] Importing JBoss BoMs to Hawkular Parent

[Stefan Negrea]

----- Original Message -----
> From: "John Mazzitelli" <mazz at redhat.com>
> To: hawkular-dev at lists.jboss.org
> Sent: Monday, February 16, 2015 9:17:35 AM
> Subject: Re: [Hawkular-dev] Importing JBoss BoMs to Hawkular Parent
> 
> > First, I am not against including WildFly in some form. But I vote for
> > the least possible set. jboss-javaee-7.0-with-all [1] is unnecessarily
> > broad. Hibernate anyone?
> 
> I didn't think it mattered because this doesn't import the dependencies
> anyway. It only imports the dependency definitions (so yeah if someone wants
> to use hibernate, they can pull it in if they want - but it is not like we
> now have a dependency on Hibernate just because the parent pom has the WF
> BOM in it. It is just letting us know what version of Hibernate we CAN pull
> in if we want to).
> 
> But if we don't even want our sub-projects to even use EE/Wildfly
> dependencies, then I can see pulling it out (to avoid tempting them to use
> it?)

Almost all the subprojects have some Wildfly dependency. Until those dependencies go away, it is better to have the BOM at the parent level. That way individual sub-projects are forced to be on the same page when it comes to versions.

I would like to not speculate on the future. Right now we depend on Wildfly. When only one project (or none) has Wildfly dependencies, then we clean up the parent pom. 

I would focus on the positive of having the BOM in the parent pom, and focus less on the potential ways the Wildfly team would do something to break us. I want to be positive about things ...

Here are just a few pluses for having a BOM in the parent pom:
1) All the subprojects will be on the same version of Wildfly dependencies
2) If we need to change the version, it is done in a single place
3) A single place means special builds (such as productization) are easy to adjust
4) No configuration required at project level, other than inherit the parent pom
5) Dependencies do not get force imported, but if somebody adds a dependency in a sub-project, the version is well known


We need to keep this change in the parent pom until one or none of the projects dependent on Wildfly components. Also, we should expand this to any other commonly used dependencies.


Thank you,
Stefan


> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>