I'm seeing a bunch of core unit test failures on metamodel branch. Is anyone
looking into these?
org.hibernate.test.ops.SaveOrUpdateTest > testEvictThenSaveOrUpdate FAILED
java.lang.AssertionError at SaveOrUpdateTest.java:467
org.hibernate.test.discriminator.DiscriminatorTest >
testAccessAs
To be honest, the fact that it is still defined on
hibernate-entitymanager anymore is just an oversight. All the
annotation handling is done in hibernate-core classes
On Mon 08 Oct 2012 12:48:36 PM CDT, Guillaume Smet wrote:
> On Mon, Oct 8, 2012 at 7:43 PM, Steve Ebersole wrote:
>> http://se
On Mon, Oct 8, 2012 at 7:03 PM, Steve Ebersole
wrote:
> We are not going to get into the business of releasing projects just for new
> releases of dependencies. Thats not manageable.
Totally agree on this point. That's why I suggested to add an exclusion.
That said, I'm not sure the problem is
On Mon, Oct 8, 2012 at 7:43 PM, Steve Ebersole wrote:
> http://search.maven.org/remotecontent?filepath=org/hibernate/hibernate-core/4.1.7.Final/hibernate-core-4.1.7.Final.pom
Argh, stupid Firefox search.
So the hibernate-commons-annotations dependency is in
hibernate-entitymanager *and* hibernat
http://search.maven.org/remotecontent?filepath=org/hibernate/hibernate-core/4.1.7.Final/hibernate-core-4.1.7.Final.pom
On Mon 08 Oct 2012 12:40:09 PM CDT, Guillaume Smet wrote:
> On Mon, Oct 8, 2012 at 7:05 PM, Steve Ebersole wrote:
>> That's not exactly how the deps work here. It is in fact hi
On Mon, Oct 8, 2012 at 7:05 PM, Steve Ebersole wrote:
> That's not exactly how the deps work here. It is in fact hibernate-core
> that introduces the dep on hibernate-commons-annotations, not
> hibernate-entitymanager.
AFAICS, nope.
The dependency for hibernate-commons-annotations is in
hiberna
That's not exactly how the deps work here. It is in fact
hibernate-core that introduces the dep on
hibernate-commons-annotations, not hibernate-entitymanager.
On Mon 08 Oct 2012 11:33:40 AM CDT, Sanne Grinovero wrote:
> On 8 October 2012 15:44, Steve Ebersole wrote:
>> Nothing Gradle specific
On 8 October 2012 15:44, Steve Ebersole wrote:
> Nothing Gradle specific here. Not following why you say that. He is
> talking about projects including hibernate-entitymanager, which I assume is
> using Maven since I believe every Hibernate sub-project is still using Maven
> to build (correct me
On 8 October 2012 17:07, Guillaume Smet wrote:
> Hi Sanne,
>
> On Mon, Oct 8, 2012 at 3:34 PM, Sanne Grinovero wrote:
>> I'll leave it to the gradle gurus on the team to say how to fix that,
>> but I'm surprised that Maven suggests both dependencies, that should
>> never be the case.
>
> It doesn
Hi Sanne,
On Mon, Oct 8, 2012 at 3:34 PM, Sanne Grinovero wrote:
> I'll leave it to the gradle gurus on the team to say how to fix that,
> but I'm surprised that Maven suggests both dependencies, that should
> never be the case.
It doesn't include both, of course. But both dependencies are prese
Nothing Gradle specific here. Not following why you say that. He is
talking about projects including hibernate-entitymanager, which I assume
is using Maven since I believe every Hibernate sub-project is still
using Maven to build (correct me if I am wrong there).
That said, this is in fact ex
Hi Guillaume,
I'll leave it to the gradle gurus on the team to say how to fix that,
but I'm surprised that Maven suggests both dependencies, that should
never be the case.
As a workaround, if you define an explicit dependency on jboss-logging
in your section you should be able to avoid any
ambigu
The easiest solution is to align both dependencies and release a new
version of Hibernate Commons Annotations to fix the issue.
Emmanuel
On Mon 2012-10-08 14:49, Guillaume Smet wrote:
> Hi,
>
> I don't know what is your policy about the dependency management but,
> currently, when you include hi
I'm not sure it's a bug but that is definitely is worth a few thoughts.
The way we implement embeddable names using the dot strategy is via a
custom naming strategy. But when you use an explicit column name, we
simply discard that and pass the real column name.
We probably can improve the naming s
Hi,
I don't know what is your policy about the dependency management but,
currently, when you include hibernate-entity-manager in the pom of an
application, it comes with dependencies to 3.1.0.Final and 3.1.0.CR2.
The problem is that hibernate-commons-annotations-4.0.1.Final requires
3.1.0.CR2 of
15 matches
Mail list logo
