<div dir="ltr"><div>This was mostly discussed as part of added bloat debate: <br><br><a href="http://lists.jboss.org/pipermail/wildfly-dev/2013-November/001125.html">http://lists.jboss.org/pipermail/wildfly-dev/2013-November/001125.html</a><br>
<br></div>I personally am not a fan!<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 16, 2013 at 5:15 PM, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So recently, Hibernate Search has been added as a dependency of Wildfly.<br>
I think for two reasons:<br>
<br>
- Infinispan when using <indexing/> requires it<br>
- CapeDwarf is a customer of Infinispan, its indexing and Hibernate<br>
Search<br>
<br>
I am a bit concerned about that move because Hibernate Search (depending<br>
on the options you choose) can bring a significant dependency graph and<br>
I don't want Wildfly to suffer from that.<br>
<br>
As part of Hibernate Search, we do work and offer a Wildfly module to<br>
ease the integration but it seems the work as been duplicated.<br>
<br>
So my question to all of you guys is the following. Isn't it enough to<br>
let Hibernate Search keep up with the module definition and let use add<br>
the module when they need either Hibernate Search, Infinispan indexing<br>
or CapeDwarf?<br>
<br>
Emmanuel<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>