Re: [wildfly-dev] Hibernate Search as a dependency
I remember that one and I must have read Brian's mail too fast as I did
not know we were going in that direction.
Note that another problem is that Hibernate Search had dependencies on
Hibernate ORM and Infinispan (optional but at the core of the feature
set).
Infinispan has dependencies on Hibernate Search (though optional).
Wildfly has dependencies on JPA and Hibernate ORM.
So adding Hibernate Search in the distro does remove a degree of
freedom.
Emmanuel
On Mon 2013-12-16 17:26, Tomaž Cerar wrote:
This was mostly discussed as part of added bloat debate:
http://lists.jboss.org/pipermail/wildfly-dev/2013-November/001125.html
I personally am not a fan!
On Mon, Dec 16, 2013 at 5:15 PM, Emmanuel Bernard <emmanuel(a)hibernate.org>wrote:
> So recently, Hibernate Search has been added as a dependency of Wildfly.
> I think for two reasons:
>
> - Infinispan when using <indexing/> requires it
> - CapeDwarf is a customer of Infinispan, its indexing and Hibernate
> Search
>
> I am a bit concerned about that move because Hibernate Search (depending
> on the options you choose) can bring a significant dependency graph and
> I don't want Wildfly to suffer from that.
>
> As part of Hibernate Search, we do work and offer a Wildfly module to
> ease the integration but it seems the work as been duplicated.
>
> So my question to all of you guys is the following. Isn't it enough to
> let Hibernate Search keep up with the module definition and let use add
> the module when they need either Hibernate Search, Infinispan indexing
> or CapeDwarf?
>
> Emmanuel
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>