Hi Adam,
there is an compile error in envers in 3.6 branch, which causes our internal
hudson job fail, would you please take a look, thanks
---
Strong Liu
http://hibernate.org
http://github.com/stliu
___
hibernate-dev mailing list
hibernate-
[05/23/11 11:10] Meeting ended Mon May 23 16:10:03 2011 UTC.
Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[05/23/11 11:10] Minutes:
http://people.redhat.com/~manderse/irc.freenode.org/meetings/hibernate-dev/2011/hibernate-dev.2011-05-23-14.59.html
[05/23/11 11:10] Mi
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6246
by working on mocking orm xml into jpa annotations, i found the most
complicated logic is how to determine access (where mocked annotations, i.e.
@Column, go, on property or on field) for an attribute.
by reading jpa spec, i'd t
2011/5/23 Steve Ebersole :
> Actually Hibernate Core has the same exact thing and I have never had a
> problem importing it via Maven into IntelliJ (do not use Eclipse, so no
> idea there).
>
> In Hibernate Core we have:
>
> hibernate-core/
> hibernate-core/
> hibernate-entitymanager/
>
> Hi Davide,
>
>
>> today I've downloaded the hibernate-search sources and my eclipse has
>> a problem importing the maven projects because the parent folder has
>> the same name as one of the sub-folders:
>
> what was the problem? I personally never had any problems importing the
> Hibernate Searc
On Mon, 23 May 2011 16:58:12 +0200, Sanne Grinovero
wrote:
> It would be fine for me to rename it, assuming it doesn't create a
> mess when backporting patches?
Given our experience w/ Core I would in this case do the rename also on
the 3.6 branch.
At least directory wise. We can always conf
Hi Davide,
> today I've downloaded the hibernate-search sources and my eclipse has
> a problem importing the maven projects because the parent folder has
> the same name as one of the sub-folders:
what was the problem? I personally never had any problems importing the
Hibernate Search
project.
Actually Hibernate Core has the same exact thing and I have never had a
problem importing it via Maven into IntelliJ (do not use Eclipse, so no
idea there).
In Hibernate Core we have:
hibernate-core/
hibernate-core/
hibernate-entitymanager/
...
On 05/23/2011 09:39 AM, Davide D'
Hi,
today I've downloaded the hibernate-search sources and my eclipse has
a problem importing the maven projects because the parent folder has
the same name as one of the sub-folders:
hibernate-search
|-- hibernate-search
|-- ...
I was a bit surprised because others Hibernate and JBoss projects I
I am a bit confused as to the why as well. Not sure what it is we gain.
Let's discuss at the meeting if you believe there is something gained that
we are just missing.
On May 23, 2011 3:58 AM, "Gail Badner" wrote:
> To be absolutely clear, I'm suggesting this as a way to put the new
metamodel API
To be absolutely clear, I'm suggesting this as a way to put the new metamodel
API in place for beta1, not for "a way out".
The Configuration would simply supply the data that would go into the new
metamodel.
- Original Message -
From: "Hardy Ferentschik"
To: hibernate-dev@lists.jboss.o
Hi,
I don't see what we would gain by this. In fact I don't know how you want
to
do this. The way forward is the new metamodel.
Given the current state I don't believe into a beta1 either (at least not
w/ the functionality we discussed), but if we are looking for a way out,
I don't think this i
I've been thinking about how we can have the metamodel API in place in time for
the 4.0.0.beta1.
One alternative is to use a fully built o.h.cfg.Configuration to provide the
data for generating the new metamodel.
This is obviously not what we would want in the end, but in the near term it
woul
13 matches
Mail list logo
