View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060120182730Lbuild.1247
BUILD COMPLETE - build.1247Date of build: 01/20/2006 18:27:30Time to build: 22 minutes 31 secondsLast changed: 01/20/2006 17:51:21Last log entry: copy the
So all of the retroweavers to date rely on the java.util.concurrent
backport to jdk1.4 (http://www.mathcs.emory.edu/dcl/util/backport-util-concurrent/)
for mapping the jdk5 concurrent util classes. I guess we need to validate this
library and deprecate the current Oswego
concurrent package
Labs,Yesterday we upgraded Labs to release 1.0.8. I've included the release notes below, but I wanted to tell everyone about a few of the key updates. With the exception of myself, the Labs team is in the middle of finals (remember college?) in Poland, so, I'm really pleased with the work Adam, T
This is my fault.
compile-classes-only:
[mkdir] Created dir:
/services/cruisecontrol/checkout/jboss-head/testsuite/output/classes
[javac] Compiling 2773 source files to
/services/cruisecontrol/checkout/jboss-head/testsuite/output/classes
[javac]
/services/cruisecontrol/checkout/jbo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060120153250
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:180: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
It depended on JBAS-2547. I need to review the associated unit test and
see if its possible to implement this in 3.2. There is a different
run-as principal behavior in 3.2 and no notion of additional run-as
roles that would need to be backported as well to fully match the 4.x
behavior and I don't k
Since several builds timed out, I’m
going to rerun them. I found some hung test processes, so perhaps there was
some conflict.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 20, 2006
1:10 AM
To: Andy Oliver; Adrian Brock;
Alexey Loubyansky; Anil Saldh
Yes, just assigned it to myself. I'll test from the 3.2 branch.
-Original Message-
From: Dimitris Andreadis
Sent: Friday, January 20, 2006 11:52 AM
To: jboss-development@lists.sourceforge.net
Cc: Ryan Campbell
Subject: RE: [JBoss-dev] Push to finalizing 3.2.8
Ryan, are you taking this
Ryan, are you taking this task? I suppose testing this can be done in
either the 3.x or 4.x branch.
Cheers
/D
http://jira.jboss.com/jira/browse/JBAS-2503
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Ryan Campbell
> Sent: 20 January, 2006 02
Any hints what is required for solving
http://jira.jboss.com/jira/browse/JBAS-1493 by backporting stuff from
4.x?
Is http://jira.jboss.com/jira/browse/JBAS-1862?page=vcs the relevant
fix?
---
This SF.net email is sponsored by: Splunk Inc. Do y
On a second thought, considering the fat warning it now logs, there is
no chance to go unnoticed if activated; so there is probably no reason
to comment it out. :-)
http://wiki.jboss.org/wiki/Wiki.jsp?page=MetricsInterceptor
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAI
Just comment it out with an explanation.
e.g.
With the link explaning they should use JSR77/MEJB/WebConsole.
But if they do enable metrics, they have to configure the
JMS listener to process the metric events.
On Fri, 2006-01-20 at 07:47, Dimitris Andreadis wrote:
> As part of http://jira.jboss.
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060120073107
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
As part of http://jira.jboss.com/jira/browse/JBAS-2656
Do you mind if I remove references to
org.jboss.ejb.plugins.MetricsInterceptor from standardjboss.xml (and
some other tests/examples)
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor
org.jboss.ejb.plugins.LogInterceptor
org.j
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.2-testsuite?log=log20060120065223
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20060120064907
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/s
On Thu, 2006-01-19 at 19:07, Ryan Campbell wrote:
> I believe so.
>
> 1. Create datasource for thin driver pointed at oracle 9i
> 2. Deploy the OracleThinPersistenceManager
> 2. Run the jboss-all-config-tests target
>
Correct.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto
17 matches
Mail list logo