Re: [Hawkular-dev] Importing JBoss BoMs to Hawkular Parent

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter, Some questions inline: On 02/16/2015 02:37 PM, Peter Palaga wrote: Aren't we targeting Wildfly? If so, then it makes sense to tie it to Wildfly, at least for this bootstrap phase. Tying to a specific application server at the beginning removes the need to solve problems that we would have if we were targeting multiple application servers. In other words, we can concentrate better on the business when we don't need to make decisions about the integration/environment. About EAP and similar derivatives: it should be close enough to Wildfly to provide a mostly smooth transition. A possible solution would be to use profiles, so that we import the appropriate BOMs depending on the build type. But I'd suggest to worry about it once it becomes a real problem. Unless we know already that we *need* to also be able to run on other application servers not compatible with Wildfly and that a refactoring later is too expensive to be done at this later point. I might have missed your point here, but when you import a BOM, aren't you just importing the dependency definitions? In such case, you can always override on our parent if there's a unwanted dependency (with an excludes). For the consumer of the dependency, it's usually easier to just import a dependency without specifying the version, as there's usually no reason why I would use a very specific version of a library. And in such unusual cases, we can, again, override it on our parent. Shouldn't matter if we stick with an already released version of Wildfly and its BOM, right? All in all, I completely agree with your points. I just do not think it's the right time to be concerned about those points *yet*. All the platforms we intend to run on do support Wildfly, which is "good enough" for a first phase. - - Juca.