I would say you can always make changes, since afaik, nothing currently directly depends on HS.
But having this in WF, is imo, good. As this makes it super trivial / easy to use it. And if there are multiple apps using it, you save on resources as well. On 16 Dec 2013, at 16:18, Sanne Grinovero <sa...@hibernate.org> wrote: > I've this feeling that this decision was rushed, there are several > implications for which we didn't prepare for. > I remember chatting with Paul Ferraro about the problem that the > Infinispan subsystem was needing to parse the "indexing" attribute > because of CapeDwarf's need to enable it, and that more recently an > improvement in Infinispan was going to eagerly validate that it > actually could enable indexing if this option was set. > > My understanding is now that the whole dependency set was included > just to accommodate for this attribute to be defined in the schema? > > I'm not against including it in WildFly, but I'd prefer to see > stronger reasons as I'd hate it for our users to "adjust" to the idea > that its included in the app server, to have it removed in the next > season because it was possible to introduce more flexibility in the > configuration parsing: > if we decide it's going to be there, let's make sure it's going to be > there for a long time. > > What's the deadline to get fixes - and possibly significant > refactorings - in the shape of the module before WF hits Final? > > > On 16 December 2013 14:16, Ales Justin <ales.jus...@gmail.com> wrote: >> Infinispan Subsystem supported Indexing element. >> This then needed Query on the classpath to work properly. >> (it could be hacked, ignored, but we opted not to do this) >> >> Then with a "little" help from CapeDwarf team, >> all "needed" libraries / modules were added. >> >> Current module config (module.xml files) is what works for our CapeDwarf. >> I'm open for any valid patch. >> >> -Ales >> >> On 16 Dec 2013, at 14:48, Emmanuel Bernard <emman...@hibernate.org> wrote: >> >>> Hum, what drove this? >>> Last time I chatted with Jason, the idea was to not have WF integrate >>> Hibernate Search in the base distro. >>> What is the consumer of the base technology? Infinispan in WF does not >>> require HSearch for the base clustering features right? >>> >>> Emmanuel >>> >>> On Mon 2013-12-16 11:19, Ales Justin wrote: >>>> Did you create a PR in WildFly, with the upgrade. >>>> As HS is now part of upstream master. ;-) >>>> >>>> On 16 Dec 2013, at 00:14, Sanne Grinovero <sa...@hibernate.org> wrote: >>>> >>>>> Hello all, >>>>> both releases where done specifically to address one bug, as explained >>>>> on the traditional release blog post: >>>>> http://in.relation.to/Bloggers/HibernateSearchWeekendReleasesFromBothMaintenanceBranches >>>>> >>>>> Best, >>>>> Sanne >>>>> _______________________________________________ >>>>> hibernate-dev mailing list >>>>> hibernate-dev@lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >>>> >>>> >>>> _______________________________________________ >>>> hibernate-dev mailing list >>>> hibernate-dev@lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
