Hi,
Given that we are moving to Search 5 and we made some recent adjustments, I am
wondering whether it would
not be time to remove the experimental status of the spatial Api now? Thoughts?
—Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jbo
Hi guys,
That sounds nice. Are association storage strategies already using this new
feature ?
Guillaume
2013/12/13 Emmanuel Bernard
> So currently in the pull request, we now have the following
>
> 1. property > entity > global
> 2. for each level in 1., programmatic API beats annotation
>
Well the discussion of disabling the tests completely grew from the
fact that the tests as they are are not stable. Inconsequential
changes would often cause them to fail. Thats why I qualified my
response with "Of course this means making these tests stable" ;)
In general I am not a fan of h
So currently in the pull request, we now have the following
1. property > entity > global
2. for each level in 1., programmatic API beats annotation
These are simple rules to understand and all it good.
Now Gunnar tried to handle class inheritance, ie superclasses and overridden
methods.
And we
Our current Arquillian-based test in hibernate-osgi demonstrates:
1.) the core/em/osgi and client bundles started
2.) SF/EMF can be created through the OSGi services
3.) basic CRUD
4.) our internal extension points registered themselves through OSGi blueprint
services and core discovered them (ex
I think it sounds great... in theory. But I believe you will hit the
matrix problem Emmanuel discusses.
However, I also want to make sure we are not removing "smoke tests" from
the projects themselves. I don't care what you call them: smoke tests,
integration tests, unit tests, regression tes
Exactly. And the matrix can become even more complicated if we attempt
multiple instances/versions of our bundles and client bundles.
Gunnar, what are your thoughts, since Validator already has a PAX EXAM test?
Brett Meyer
Red Hat, Hibernate ORM
- Original Message -
From: "Emmanuel Ber
Hi,
>>> The fix to include documentation would probably need to wait migration
>>> to asciidoc.
>>
>> I am not quite following? Which fix for documentation?
>
> I was referring to the fact that the documention is also not built by
> default. I'm seeing the light on your suggestions now,
ahh, mu
On 13 December 2013 09:50, Hardy Ferentschik wrote:
>
> On 12 Jan 2013, at 21:54, Sanne Grinovero wrote:
>
>> In Hibernate Search there is a Maven module responsible for running
>> performance tests, which takes several minutes to run.
>>
>> Since it's quite annoying for day to day development, a
On 12 Jan 2013, at 21:54, Sanne Grinovero wrote:
> In Hibernate Search there is a Maven module responsible for running
> performance tests, which takes several minutes to run.
>
> Since it's quite annoying for day to day development, and especially
> during a release process as the process runs
On 12 Jan 2013, at 21:54, Sanne Grinovero wrote:
> In Hibernate Search there is a Maven module responsible for running
> performance tests, which takes several minutes to run.
>
> Since it's quite annoying for day to day development, and especially
> during a release process as the process runs
I did not see that thread when I opened the constant naming unification.
I am a bit skeptical that option should be used for global settings like host
and co but let's try and see where that leads us.
On 11 déc. 2013, at 18:36, "Davide D'Alto" wrote:
>> Our question is, should now that we ha
12 matches
Mail list logo
