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 be
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
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.
The host
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,
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
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
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
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:
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:
