FYI : https://hibernate.atlassian.net/browse/HHH-9803
Its not super high on my priority list, but I want to get to a point where
we can start to fail the build on "serious checkstyle regressions". Part
of that is being more realistic with what is considered serious, and part
of that is fixing up
The problem is legacy databases and how to help users migrate the id
generation strategies. Or are you thinking that existing users would have
to disable this on upgrade?
On Fri, May 15, 2015 at 3:14 PM, Sanne Grinovero
wrote:
> I just noticed that the ORM testsuite seems to consistently set th
I just noticed that the ORM testsuite seems to consistently set this
option to "true".
The default being false, the "new" kind is available since ORM 3.2
according to javadoc.
Would this be a good time to switch the default?
___
hibernate-dev mailing li
Yes, we should.
There is already an issue for this:
https://hibernate.atlassian.net/browse/OGM-798 ("Extract base class from
DocumentStoreConfiguration").
2015-05-15 18:44 GMT+02:00 Sanne Grinovero :
> +1
>
> On 15 May 2015 at 16:32, Emmanuel Bernard wrote:
> > So far DocumentStoreConfiguration
+1
On 15 May 2015 at 16:32, Emmanuel Bernard wrote:
> So far DocumentStoreConfiguration is very generic and only deals with
> remote datastore with reasonable expectations (hosts, ports, usernames.
>
> Cassandra makes use of that class.
> Should we rename it and create a subclass for document sto
Hey Jonathan,
I investigated a bit the Cassandra failure I am seeing.
The logs based on a code change I did are here
https://gist.github.com/emmanuelbernard/13d22d15dc983a83a7e2
My understanding is that the failing type is the TrueFalseType used on
Bookmark.isPrivate. This type returns a F char
So far DocumentStoreConfiguration is very generic and only deals with
remote datastore with reasonable expectations (hosts, ports, usernames.
Cassandra makes use of that class.
Should we rename it and create a subclass for document stores that would
be empty today?
Emmanuel
__
On 05/15/2015 01:41 AM, Gail Badner wrote:
> Following Steve's suggestion using resolutionStrategy, I was able to build
> the hibernate-infinispan jar with Infinispan 6.0.0.Final and run the unit
> tests with 7.2.1.Final.
>
> I'm sure there's a more elegant way to do this, so I've created a new j
Hi Sanne,
Thanks for your feedback. My answers below:
On Thu, May 14, 2015 at 11:05 PM, Sanne Grinovero
wrote:
> - ignoreAnalyzer() I agree with your comment, it doesn't seem to make
> much sense. But what about not having the method rather than making it
> throw an exception?
> I'm assuming t
thanks Steve,
this works fine, as you suggested:
./gradlew clean generateKarafFeatures publishToMavenLocal
-DJAVA6_HOME=/opt/jdk-6/
On 15 May 2015 at 13:18, Steve Ebersole wrote:
> Oh that's right. This is something I wanted to look at changing in that
> karaf plugin I contribute to. Normally
Oh that's right. This is something I wanted to look at changing in that
karaf plugin I contribute to. Normally you define artifacts for publishing
via the task that produces them; Gradle will then automatically add that
task as a dep to the publishing related tasks. But Gradle expects the task
t
Hmm I might not have set up the task deps properly for the task that
generates that file. It should depend on the hibernate-osgi jar task. You
can try setting the deps or you can try running the task directly. It's
called something like generateKarafFeatures
On May 15, 2015 6:52 AM, "Sanne Grino
I need to build local snapshots of ORM to test things with Hibernate
Search, but invoking "publishToMavenLocal" produces an error on the
OSGi module:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task
':hibernate-osgi:publishMavenJavaPublicationToMavenLocal'.
Fa
I'm not sure how to call it, I'm referring to this source file:
hibernate-core/src/test/java/org/hibernate/test/common/JdbcConnectionAccessImpl.java
That, along with other files in the same package, seems useful to
create tests. I've temporarily copied into the Hibernate Search
sources.
On 15
2015-05-13 15:08 GMT+02:00 Scott Marlow :
> I remember seeing this before but don't remember why. Years ago, I
> blogged [1] about using OGM on JBoss AS (before the rename to WildFly). I
> didn't name the entity classes in the blog (or git [2]), so not sure if
> that was because OGM worked bette
I think it is closely related (if not the same) to this one:
https://hibernate.atlassian.net/browse/HHH-9788
2015-05-15 5:20 GMT+03:00 Steve Ebersole :
> Actually that cannot be it. JPA does not define schema update capability.
> On May 14, 2015 4:27 PM, "Steve Ebersole" wrote:
>
>> So you're
On Thu 2015-05-07 17:51, Gunnar Morling wrote:
> > But I could still use session.getTransaction() and get the “wrong”
> > behavior?
> >
>
> I think it's the general question should we have an API which offers
> "everything", i.e. the sum of all functionality of all backends, meaning
> that some pa
17 matches
Mail list logo
