On 12/16/2013 11:19 AM, Ales Justin wrote:
> Probably waiting on you or Sanne to add them. :-)
>
> We're already running whole CapeDwarf Testsuite on it,
> which means it's tested a lot -- 1300+ tests.
>
> But of course, that doesn't mean you shouldn't have basic / smoke tests in
> WF. ;-)
Do the
Probably waiting on you or Sanne to add them. :-)
We're already running whole CapeDwarf Testsuite on it,
which means it's tested a lot -- 1300+ tests.
But of course, that doesn't mean you shouldn't have basic / smoke tests in WF.
;-)
On 16 Dec 2013, at 16:24, Scott Marlow wrote:
> I didn't kn
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
I didn't know about this change either. Are there any WildFly unit
tests using HS?
On 12/16/2013 09:16 AM, Ales Justin 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
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 mor
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
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 Ju
> How does this relate to the "JBoss Modules" module provided by HSEARCH itself?
Afaik, Paul and me weren't aware you had anything supported in HS.
> From a quick look it seems that WF provides now its own module for
> hibernate-search-engine, the module.xml contents differ a bit from the one in
How does this relate to the "JBoss Modules" module provided by HSEARCH
itself?
>From a quick look it seems that WF provides now its own module for
hibernate-search-engine, the module.xml contents differ a bit from the one
in HSEARCH, though. Also the module paths are different, so a user putting
t
Hi Ales,
thanks for the heads up, I wasn't aware it was already included in
WildFly so quickly.
Could we please include at least a single smoke test in it? Hibernate
Search 4.4 is NOT compatible with the ORM version currently in WF8, so
I don't think this was ever tried (other than via the Infinis
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 wrote:
> Hello all,
> both releases where done specifically to address one bug, as explained
> on the traditional release blog post:
>
> http://in.relation.to/B
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
12 matches
Mail list logo
