[wildfly-dev] Hibernate Search as a dependency

[Jason Greene]

Yes I agree that we want to remove it from at least our primary distro. The solution
I would have preferred, but never got sent to the ML (was in my drafts folder - oops)
was that we only pull in hibernate search to test <indexing/> but not ship it by default.

On Dec 16, 2013, at 10:15 AM, Emmanuel Bernard <emmanuel at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat