View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060201014338
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060131223828
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of build: 01/31
How can the scanClasspath() step be optimized/skipped in say an embedded
ejb3 project in jbosside where the data obtained during the scan was
written out in an optimized metadata store as part of the project say?
I don't really follow adding aspects like clustering to deployments
based on the loca
Yes, this is Branch_4_0. Thanks, Tom.
-Original Message-
From: Tom Elrod
Sent: Tuesday, January 31, 2006 1:28 PM
To: Tom Elrod
Cc: Ryan Campbell; Tom Elrod; Kabir Khan; Bill Burke;
jboss-development@lists.sourceforge.net
Subject: Re: ejb3-4.0-testsuite Build Failed
I think I get the mis
I think I get the mis-match now. This is being build out of JBoss 4.x
branch, right? If so, then the code for jbossas-remoting.jar is not
there. There is an issue for this (JBAS-2698), which I will work on today.
Tom Elrod wrote:
The class that is not being found is within jbossas-remoting.j
The class that is not being found is within jbossas-remoting.jar. This
is part of JBossAS code base and not remoting. Only way this would be
called to be loaded is if was configured to use the JBossAS security
domain via configuration. So am guessing the jar was excluded from the
build?
Ry
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache?log=log20060131141912Lbuild.136
BUILD COMPLETE - build.136Date of build: 01/31/2006 14:19:12Time to build: 16 secondsLast changed: 01/31/2006 13:58:17Last log entry: Removed JDBCCacheLoaderMySQLDSTe
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache?log=log20060131133622
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:41: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 01/31/2006 13:36:2
The ejb3-ssl-advanced test server is
broken:
2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jboss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/org.jb
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060131102532Lbuild.1323
BUILD COMPLETE - build.1323Date of build: 01/31/2006 10:25:32Time to build: 30 minutes 17 secondsLast changed: 01/31/2006 09:47:24Last log entry: Remove a
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060131083804
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:216: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
I think going the E-EJB3 route to start is a good idea as it will force
us to implement bare-bones implementations that do not have the idea of
a classloader or j2ee deployment schemes within them. Once we have
e-ejb3 (really e-jboss) in place, it will force us to be careful about
adding thing
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060131072127
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
I browsed through the EJB3StandaloneBootstrap and embedded ejb3 usage of the mc to see what extent the mc is being used. In browsing through the conf/embedded-jboss-beans.xml for the mc config, I did not see anything related to the ejb3 container or aop layer to load the conf/ejb3-interceptor
Yes, I wrote this test to stop people breaking it.
That doesn't mean I am going to fix it when people do!
My new years resolution is to stop wasting time
cleaning up after the zoo animals. :-)
Looking at CVS, Ben Wang was the last person to modify
the instance cache in 4.0.x
This is BMP so that r
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060131023917Lbuild.56
BUILD COMPLETE - build.56Date of build: 01/31/2006 02:39:17Time to build: 31 minutes 9 secondsLast changed: 01/30/2006 11:09:35Last log entry: Make a
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20060131031155
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
17 matches
Mail list logo
