This is a follow up on
https://github.com/hibernate/hibernate-ogm/pull/307#issuecomment-38453092
We keep piling up new backends, new containers to test and new rules
checked at build time. A consequence is that it is becoming less and
less pleasant to work on OGM.
You can see that n version of Na
My vote goes to #1 as well for the short term.
There also is a third option, which requires some more work but
provides a very nice balance.
A great deal of the slowness of this complex matrix execution can be
addressed to the continuous startup and teardown of services like the
various databases
[11:50] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-03-25-15.49.html
[11:50] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-03-25-15.49.txt
[11:50] Log:
http://transcripts.jboss.
Hi there,
As part of my work for making Search OSGi ready [1], I am looking into
addressing HSEARCH-1560 [2] which is about
split packages which we have between some of our Search bundles (or modules to
use Maven lingo).
Basically a split package "is caused where two or more bundles export the
>From the test
org.hibernate.test.annotations.access.jpa.AccessMappingTest#testExplicitPropertyAccessAnnotationsWithHibernateStyleOverride
we have the following:
@Entity
@Access(AccessType.PROPERTY)
public class Course3 {
private long id;
...
@Id
@GeneratedValue
@Access(Acces
