[hibernate-dev] hibernate-oracle10-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20061204231257 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:106: The following error occurred while executing this line: /home/cruisecontrol/work

[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061204223744 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:127: The following error occurred while executing this line: /home/cruisecontrol/work/sc

[hibernate-dev] hibernate-mysql50-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061204221023 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:134: The following error occurred while executing this line: /home/cruisecontrol/work/

[hibernate-dev] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061204220009 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/sc

[hibernate-dev] hibernate-mysql50-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061204144847 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:134: The following error occurred while executing this line: /home/cruisecontrol/work/

[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061204151821 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:127: The following error occurred while executing this line: /home/cruisecontrol/work/sc

Re: [hibernate-dev] overriding target through annotations

I agree with your analysis, but @MapKeyTarget vs @o.h.a.MapKey / @o.h.a.MapKeyManyToMany enhancement with target is not influenced by the @j.p.MapKey design flaws. Pros of each solution are 1. @MapKeyTarget SoC (Relational descriptions are split from Object descriptions in annotations) @Targe

Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

Steve Ebersole wrote: > Um, perhaps if you are going to ask me to do something you could can the > attitude? Seems like a basic requirement to me... Sorry if I put words in your mouth there or seem to be creating lots of work for somebody else. Is the cruise control configuration / testing

RE: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

Um, perhaps if you are going to ask me to do something you could can the attitude? Seems like a basic requirement to me... As far as the box hosting the runs, I did not realize I had presumed anything. The point was simply that it seems silly to me to invest a lot of effort to script this when

Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

Steve Ebersole wrote: I am not really familiar with CruiseControl, so what exactly do you mean by "emit"? emit in this case means make it clearly visible at first glance which JDK, Host, JDBC Driver and SQL Server version are being used for the test case run. That seems like a pretty basic r

RE: [hibernate-dev] FlushMode.NEVER deprecated

Thanks for highlighting exactly why FlushMode.NEVER was poorly named ;) I believe you are actually asking for FlushMode.NEVER to actually be migrated to a new semantic. That's not a good idea because it would be confusing for users on an upgrade... -Original Message- From: [EMAIL PROTE

RE: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

I am not really familiar with CruiseControl, so what exactly do you mean by "emit"? AFAIK, the same box hosts the various runs, correct? So unless there are plans to change that, a lot of effort here seems silly. As far as the extra JDBC metadata, the JDBC driver is *supposed* to make this info

Re: [hibernate-dev] FlushMode.NEVER deprecated

andresgr wrote: Hi. I can see in Hibernate 3.2 LockMode.NEVER is deprecated in favor of LockMode.MANUAL. Maybe this is a silly argument... but i think that FlushMode.NEVER has some "semantic" benefits. I mean, if i'm reading code and see session.setFlushMode(FlushMode.NEVER) i think "oh,

Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]

Darryl, For the information you wish, you could create a JIRA task (maybe a feature request). I will update the the JDBC driver to the latest. Tanks for the feedback. Aleksandar Darryl Miles wrote: > > Is it possible to emit some extra information with the testsuite > output summary. > > > > Th

Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]

Is it possible to emit some extra information with the testsuite output summary. The host running the testsuites JDK and Operating System (whichever values seems more useful across the major JDK) : java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition java.runtime.version=1.5

[hibernate-dev] FlushMode.NEVER deprecated

Hi. I can see in Hibernate 3.2 LockMode.NEVER is deprecated in favor of LockMode.MANUAL. Maybe this is a silly argument... but i think that FlushMode.NEVER has some "semantic" benefits. I mean, if i'm reading code and see session.setFlushMode(FlushMode.NEVER) i think "oh, this is going to b