Re: [jdf-dev] [new organization] BOMs repository split

Sorry for taking so long to think about this issue. If that's still relevant, here is what I think. We should indeed have a BOM including ORM and a different one including Hibernate Search with the second having a dependency on the first. The reasons that lead to this are: - JDG and WFK use Hibernate Search - EAP uses ORM - HSearch depends on ORM - HSearch life cycle is faster than ORM's Emmanuel On Fri 2013-07-05 18:50, Pete Muir wrote: > Both mixins and inheritance are supported. > > On 5 Jul 2013, at 17:31, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > >> I don't know. Can you mixin BOMs or are they rigidly hierarchical? >> >> On 5 juil. 2013, at 18:09, Pete Muir <pmuir(a)redhat.com&gt; wrote: >> >>> So, do we have a -with-hibernate-orm and -with-hibernate-search BOM? >>> >>> On 5 Jul 2013, at 16:40, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: >>> >>>> On Fri 2013-07-05 11:47, Rafael Benevides wrote: >>>>> As part of the plan, the BOMs will be splited according to its product: >>>>> EAP or WFK >>>>> >>>>> Today there are some BOMs that is distributed in both products. My >>>>> question is what we should do about them? Move it to EAP or move it to WFK? >>>>> >>>>> The worst if keeping it in both repos. >>>>> >>>>> These are the boms that have release on eap 6.1 and wfk 2.2 >>>>> >>>>> - with-deltaspike >>>>> - with-errai >>>>> - with-hibernate >>>> >>>> With Hibernate ORM being at the center of EAP's persistence >>>> implementation, ORM should be in a BOM shared by anyone seeding off EAP. >>>> >>>> Hibernate Search being used by WFK, Data Services and JBoss Data Grid >>>> it's quite more complicated but again some "common libs" used by a >>>> common set of versions of EAP, WFK and SOA. >>>> But I'm sure, at least initially that we will need to have some >>>> exceptions esp until the search support for JDG matures enough. >>>> >>>> It's somehow tied ot the layered architecture and the idea of a core >>>> shared by compatible platforms. >>>> >>>> That's a general view but we should discuss on email (or if we have to >>>> on a call) the exact requirements and needs of these BOMs to come to the >>>> proper solution. >>>> >>>> Emmanuel >>>> _______________________________________________ >>>> jdf-dev mailing list >>>> jdf-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>> >