Hello all,
we released version 5.0.0.Alpha4 of Hibernate Search
All details on:
http://in.relation.to/Bloggers/HibernateSearchNowRequiresJava7BringsOSGiAndFieldBridgeDiscovery
Please note it requires Java7 at runtime!
Sanne
___
hibernate-dev mailing
Persisters are most certainly not generally considered APIs. We simply
have not yet done the packaging split there. APIs are things you use in
your application. Applications generally are not calling persisters in
normal usage.
On Mon, May 19, 2014 at 2:34 PM, Gail Badner wrote:
> Hi Gunnar,
We do strive to maintain backwards compatibility of SPIs. That being said,
there are times when fixing a bug requires a new SPI method. Which *seems*
to have been the case here.
First, I am not sure what you mean by OGM "naturally still override the old
signature". What "old signature"? This i
Gail, Steve,
Thanks for your replies.
2014-05-20 15:28 GMT+02:00 Steve Ebersole :
> We do strive to maintain backwards compatibility of SPIs. That being
> said, there are times when fixing a bug requires a new SPI method. Which
> *seems* to have been the case here.
>
That's good news.
In you
Discussed new header for source files, new ParameterRecognizer for OGM
integration, and "DynamicAttributeContributor" for OGM/Infinispan support
(to be fleshed out more).
[11:06] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-05-20-14.48.html
One of the modules of the HQL Parser project is now going to require
Java7 at runtime, which implies I have to compile that one with Java7
and use Java7 for testing.
Would it be ok to move the whole project to use Java7?
I don't stricly need all modules to drop Java6, but it would keep the
build
I'd prefer to not as we discussed on IRC
On Tue, May 20, 2014 at 1:14 PM, Sanne Grinovero wrote:
> One of the modules of the HQL Parser project is now going to require
> Java7 at runtime, which implies I have to compile that one with Java7
> and use Java7 for testing.
>
> Would it be ok to move
I've released both versions:
1.1.0.Alpha1 is compatible with Hibernate Search 5.0.0.Alpha1
1.1.0.Alpha2 is compatible with Hibernate Search 5.0.0.Alpha4
(I needed both as there are too many changes in Search to handle a single leap)
The target Java version is 1.6 as discussed with Steve; howeve
Because AbstractEntityPersister implements Queryable (but EntityPersister does
not), core does something like this to get access to Queryable interface
methods:
final Queryable queryable = (Queryable) sessionFactory.getEntityPersister(
entityName );
Is this an acceptable way for an applica
Sorry, no idea why I missed that email.
So the basic rule is:
- fields from a non-audited mapped superclass are never audited, unless an
@AuditOverride is specified
- if the mapped superclass is audited, then its fields are of course audited as
well
I don’t think we want to get into supporting
10 matches
Mail list logo
