[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060321234012 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts

[JBoss-dev] JBossCache 1.3.0.CR1 released

JBossCache 1.3.0.CR1 has been released. This can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=403608     Thanks Rajesh JBoss QA

[JBoss-dev] jboss-cache-testsuite build.46 Build Fixed

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060321195049Lbuild.46 BUILD COMPLETE - build.46Date of build: 03/21/2006 19:50:49Time to build: 35 minutes 5 secondsLast changed: 03/21/2006 18:40:19Last log entry: Disabled a bun

[JBoss-dev] jboss-4.0-testsuite Build Failed

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060321182057 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224: The following error occurred while executing this line: /services/cruisecontrol/work/scripts

[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060321170015 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/

Re: [JBoss-dev] 4.0.4

That sounds like a plan. Scott M Stark wrote: Just do a 4.0.5 soon after than. I don't want to push the 4.0.4.GA as Dimitris said people have been waiting on it for a while. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Monday, March

[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060321142300 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/

[JBoss-dev] Code review

I'm sure others weren't aware of this behaviour, so you might want to check your code: http://jira.jboss.com/jira/browse/JBAS-2973 -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.Net em

[JBoss-dev] jboss-4.0-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log2006032121 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts

[JBoss-dev] FW: Viewer for JMX/MBeans

Yes, viewer for JMXConsole would be a nice feature to be added IMO... For example, a method returning an array of objects could have a viewer formatting the result properly. On JbossProfiler I have a method called Class[] getLoadedClasses() on JVMTIInterface If I had a way to add a viewer metada

[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors

The txtimer errors are due to previous deployments not getting cleaned up due to OOMEs: 2006-03-20 13:20:21,455 WARN [org.jboss.system.ServiceController] Problem start ing service jboss.j2ee:jndiName=test/txtimer/TimerTest,service=EJB java.lang.OutOfMemoryError ... 2006-03-20 13:20:25,895 INFO [o

[JBoss-dev] jboss-seam-testsuite Build Failed

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060321092133 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:54: /services/cruisecontrol/work/scripts/test-output not found.Date of build: 03/21/2006

[JBoss-dev] microcontainer-head-testsuite build.90 Build Fixed

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060321084310Lbuild.90 BUILD COMPLETE - build.90Date of build: 03/21/2006 08:43:10Time to build: 37 minutes 10 secondsLast changed: 03/20/2006 10:56:43Last log entry: [JBMI

[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060321081706 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo

[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060321065101 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo

[JBoss-dev] Re: [jboss-cvs] jbosstest ...

There is a perfectly good way to make this configurable locally without swamping the rest of us with garbage on the console from crappily written tests. There is no need for this anyway. If you write your tests properly using logging, the output goes to output/log/test.log And the System.out/er