We may have to go right to m8...
http://forums.gradle.org/gradle/topics/plugins_and_classloader_isolation
On Wed 18 Jan 2012 08:04:02 AM CST, Steve Ebersole wrote:
> I am in that process. The problem is upgrading all the plugins. Stay
> tuned
>
> On Wed 18 Jan 2012 06:16:31 AM CST, Hardy Ferent
I agree its not the best outcome. But according to the spec it is
unfortunately (imo) exactly what should happen, given its current
wording, in a case where you have not cleaned up references to the
thing.
On Wed 18 Jan 2012 11:39:24 AM CST, Guillaume Smet wrote:
> On Wed, Jan 18, 2012 at 6:31
On Wed, Jan 18, 2012 at 6:31 PM, Steve Ebersole wrote:
> Well really the trouble is that you are not managing the associations in
> memory. I understand the behavior is surprising, but had you simply cleaned
> up the Person reference from all its associations (as the JPA spec says you
> have to a
No JIRA yet. Want to decide on general plan of action first.
Well really the trouble is that you are not managing the associations
in memory. I understand the behavior is surprising, but had you simply
cleaned up the Person reference from all its associations (as the JPA
spec says you have to
Hi Steve,
On Wed, Jan 18, 2012 at 5:42 PM, Steve Ebersole wrote:
> This is unexpected and obviously unintended, but it is also clearly what the
> spec says should happen. I have asked the spec lead about some possible
> options that would probably still meet the intent of the spec (even if they
Sounds like you are experiencing the issue where flush cascades PERSIST
back to an entity that was removed.
This was "introduced" by HHH-5124. Previously, Hibernate was really in
violation of the JPA spec, specifically section 3.2.2 which says that
the PERSIST operation applied to some entity
Hi,
In our test cases, we have a test which checks a lot of cascade
configuration (it's more to document all the cascade behaviors than to
really test an application).
After the upgrade from Hibernate 4.0 to Hibernate 4.0.1, we have a test failing:
- a person is linked to a company
- if we delete
I am in that process. The problem is upgrading all the plugins. Stay
tuned
On Wed 18 Jan 2012 06:16:31 AM CST, Hardy Ferentschik wrote:
> Sanne is right, atm you need 1.0-milestone-3. Best always to use gradlew to
> build instead of
> an installed version of gradle.
>
> That said, I was playin
Sanne is right, atm you need 1.0-milestone-3. Best always to use gradlew to
build instead of
an installed version of gradle.
That said, I was playing around with milestone 7 and it seems to be a fair bit
faster. Unfortunately,
the Hibernate Core build would need some adjustments to be able to
Hi Galder,
use version 1.0-milestone-3
personally I always build with the included Gradle version:
./gradlew clean install
Cheers,
Sanne
On 18 January 2012 11:28, Galder Zamarreño wrote:
> Hi all,
>
> Hibernate ORM fails to build with latest Gradle 1.0 Milestone 7, see:
> https://gist.github.co
Hi all,
Hibernate ORM fails to build with latest Gradle 1.0 Milestone 7, see:
https://gist.github.com/1632550
Any idea?
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
___
hibernate-dev mailing list
hibernate-dev@lists.jbos
Hi All.
4.1.0.Alpha1 of Hibernate Search was just released:
http://in.relation.to/Bloggers/HibernateSearch41IsComing
Regards,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
12 matches
Mail list logo
