On 12/16/2013 11:26 AM, Tomaž Cerar wrote:
This was mostly discussed as part of added bloat debate:
There is more to it then adding additional jars. We also need more than
zero unit tests and possibly more time in the schedule (WF 8/9).
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 <mailto:emmanuel@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 <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev