View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060407221812
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407193805
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407185832
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407163521
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
Thanks to everyone that responded. I understand now.
On Fri, 2006-04-07 at 08:07 -0500, Steve Ebersole wrote:
> Just so it is perfectly clear:
>
> Hibernate does not use its cache providers in any way, shape or form for
> implementing the "first level cache". As Max mentioned, the "first
> leve
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407134808
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407125847
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
Hi
Jason/Scott,
the new catalog support in jboss-head
does not work for remote clients. I
need to look into it on monday.
Have a good
weekend
-thomas
That's what I was afraid of.
Dimitris Andreadis wrote:
It's not planned. Some do individual TCK testing (e.g. WS).
-Original Message-
From: Alexey Loubyansky
Sent: 07 April, 2006 15:42
To: Dimitris Andreadis
Cc: jboss-development
Subject: Re: Toward JBoss v4.0.4.GA - Part 1 - JIRA ta
Coincidence.
> -Original Message-
> From: Steve Ebersole
> Sent: 07 April, 2006 16:00
> To: Dimitris Andreadis; 'jboss-development'
> Cc: The Core
> Subject: RE: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues
>
> Hibernate will stay at a CR; it will not go final until the
>
It's not planned. Some do individual TCK testing (e.g. WS).
> -Original Message-
> From: Alexey Loubyansky
> Sent: 07 April, 2006 15:42
> To: Dimitris Andreadis
> Cc: jboss-development
> Subject: Re: Toward JBoss v4.0.4.GA - Part 1 - JIRA tasks
>
> Are the J2EE TCK tests part of the QA
Just so it is perfectly clear:
Hibernate does not use its cache providers in any way, shape or form for
implementing the "first level cache". As Max mentioned, the "first
level cache" is really just a particular aspect of the role fulfilled by
the org.hibernate.engine.PersistenceContext implement
Hibernate will stay at a CR; it will not go final until the EBJ3 spec is
final...
BTW, what is with Javassist being at the same exact version? Is that just
coincidence?
-Original Message-
From: Dimitris Andreadis
Sent: Wednesday, April 05, 2006 5:33 AM
To: jboss-development
Cc: The C
Are the J2EE TCK tests part of the QA procedure before the release?
Dimitris Andreadis wrote:
When we started work on 4.0.4 we had 300+ issues ahead of us, now after
2 candidate releases we are down to around 80, which is quite an
achievement, but still a significant amount of work is left for t
I have created a new release in JIRA - 1.3.0.SP1Could you pls mark these JIRA tasks as targets for fixing in both 1.4.0 and 1.3.0.SP1 - makes it easy for me to create release notes for 1.3.0.SP1. Please do so even if you've already fixed and closed the JIRA tasks.Thanks!--Manik Surtani[EMAIL PROTE
Is this related to http://jira.jboss.com/jira/browse/JBAS-1888 ?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Ben Wang
> Sent: 07 April, 2006 10:35
> To: jboss-development@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: RE: [JBoss-d
I agree with Manik here. If it is user-specified, we mandate them to escape it
themselves for Windows. But we need to do the same for our own AS path variable
like ${jboss.server.data.dir}.
I'd say let's open a Jira and fix this in jboss-head only since we are moving
to 5.0, AFAIK.
-Ben
17 matches
Mail list logo
