2013/10/25 Hardy Ferentschik
>
> On 25 okt 2013, at 22:54, Gunnar Morling wrote:
>
> > When importing the ORM Gradle project into IntelliJ or Eclipse, I'm
> getting
> > the following error:
>
> Importing how? Did you create the IDE project files via 'gradle eclipse'
> resp. 'gradle idea' or are
On 25 okt 2013, at 22:54, Gunnar Morling wrote:
> When importing the ORM Gradle project into IntelliJ or Eclipse, I'm getting
> the following error:
Importing how? Did you create the IDE project files via 'gradle eclipse' resp.
'gradle idea' or are you any sorts of plugins.
Not sure about Ec
Hi,
When importing the ORM Gradle project into IntelliJ or Eclipse, I'm getting
the following error:
===
FAILURE: Build failed with an exception.
* Where:
Build file '[...]/hibernate-orm/hibernate-core/hibernate-core.gradle' line:
2
* What went wrong:
A problem occurred evaluating project ':h
On Fri 25 Oct 2013 12:42:15 PM CDT, Hardy Ferentschik wrote:
>>> * Should we move the docbook sources to the documentation module and create
>>> a new "book", next to devguide, manual
>>>and quickstart? I guess there are pro and cons for each approach. I
>>> would lean towards moving the meta
On 25 Jan 2013, at 6:16 PM, Steve Ebersole wrote:
>
> On Oct 25, 2013 10:26 AM, "Hardy Ferentschik" wrote:
>
> > * What should be the next version of the annotation processor? I guess it
> > could just use the main ORM version, so
> > we would make a version jump from 1.3.0.Final to 4.3.x
On Oct 25, 2013 10:26 AM, "Hardy Ferentschik" wrote:
> * What should be the next version of the annotation processor? I guess it
could just use the main ORM version, so
> we would make a version jump from 1.3.0.Final to 4.3.x
4.3.x
> * Should we move the docbook sources to the documentation m
Hi,
I pushed a branch [1] to my local ORM repo which integrates the metamodelgen
sources into ORM as per HHH-8483 [2].
The sources are under tooling/metamodel-generator and the commit history is
kept. I did, however, squash several commits.
This includes in particular the commits from the maven
2013/10/21 Emmanuel Bernard
> Gunnar has I had a long discussion and disagreement on the behavior of
> Option in Hibernate OGM that we could not resolve. We would like your
> feedback.
>
> I did design Option to represent three key concepts:
>
> - an option family - for example named query
> - an
2013/10/25 Davide D'Alto
> The isNeo4j() is just a trick so that the user does not have to set a
> property. I'm also not totally happy about it
>
Ok, I see. Good we agree :) I've created OGM-370 for this.
>
>
> > Neo4j seems to allow for this via the TransactionManagerProvider SPI.
> Unfortuna
The isNeo4j() is just a trick so that the user does not have to set a
property. I'm also not totally happy about it
> Neo4j seems to allow for this via the TransactionManagerProvider SPI.
Unfortunately one isn't in control of instantiating such providers, though.
So one would have to do some hacke
Hi Davide,
I'm wondering why instead of creating Neo4jJtaPlatform we don't provide the
TransactionManager as retrieved from ORM's JtaPlatform to Neo4j (as we e.g.
do for ISPN)? I find the isNeo4j() code in ogm-core a bit discomforting.
Neo4j seems to allow for this via the TransactionManagerProvi
11 matches
Mail list logo
