I am a big fan of Hibernate technologies and the search capabilities. I
am concerned though that we are deferring how to untangle the Hibernate
Search/Infinispan/WildFly dependencies.
I raised a few questions on the wildfly-dev mailing list, some that got
answered but one important issue didn'
> Unfortunately, this comes at a non optimal point in time. Not only will it
> take time from the
> Lucene 4 migration (aka Search 5), but if Search 4.x gets included now we
> probably will get very
> quickly people asking on how to use Search 5 with Wildfly. If nothing else a
> lot of dependen
On 14 Jan 2014, at 12:25, Sanne Grinovero wrote:
>> +1 Does this really need a separate module?
>
> It's probably not strictly needed, but I think it's preferable so that
> people can use a different version of it.
> Also, it's our tested configuration.
ok
>> Is there some info about “optiona
On 14 January 2014 11:23, Hardy Ferentschik wrote:
>
> On 14 Jan 2014, at 00:06, Sanne Grinovero wrote:
>
>> as you might already know by following the WildFly developer's mailing
>> list, most of the Hibernate Search jars and dependencies (Lucene) are
>> now included in the application server as
On 14 Jan 2014, at 00:06, Sanne Grinovero wrote:
> as you might already know by following the WildFly developer's mailing
> list, most of the Hibernate Search jars and dependencies (Lucene) are
> now included in the application server as modules.
Right. Still not sure whether this is such a gre
On Tue, Jan 14, 2014 at 12:11 AM, Sanne Grinovero wrote:
> Of course I'm ok with that. If any I was under the impression you
> needed a solution urgently; if that's the case, be aware I suspect
> this could be a trivial change.
It's for a sort on a table (but an important one) so I can make the
c
