[JBoss-dev] jboss-remoting-testsuite-1.4 Build Timed Out

2006-02-25 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060225015715 BUILD TIMED OUTAnt Error Message:build timeoutDate of build:02/25/2006 01:57:15Time to build: Unit Tests: (0) Total Errors and Failures:

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

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

[JBoss-dev] Re: Finalizing the Release of JBAS 3.2.8.SP1 4.0.4.GA - YourHelp is Needed

2006-02-25 Thread Mark Little
Yes, we're still on target for a 4.0.4 plug-in for end of March. Mark. Scott M Stark wrote: The new jta code is not fully cleaned and in a public repository. Need to check with Mark/Kevin to see if this is still on target for a 4.0.4 release next month. -Original Message- From:

[JBoss-dev] Re: Finalizing the Release of JBAS 3.2.8.SP1 4.0.4.GA - YourHelpis Needed

2006-02-25 Thread Mark Little
Yes. The intention is for 2 plugins for 4.0.4: one to cover the purely local JTA implementation (which becomes the default in 5.0) and one to cover JTS/WS-T (which will remain as a separate plugin in 5.0). Mark. Andy Miller wrote: JBoss Transactions should stay an optional plug-in for the

[JBoss-dev] Re: Finalizing the Release of JBAS 3.2.8.SP1 4.0.4.GA - YourHelp is Needed

2006-02-25 Thread Mark Little
So it depends what you expect to see. http://jira.jboss.com/jira/browse/JBTM-2 is one example of the tasks left. You need to remember that the main integration effort was done months ago in Arjuna, who've been selling the integrated components for a few years. What we're doing here is a

[JBoss-dev] RE: Finalizing the Release of JBAS 3.2.8.SP1 4.0.4.GA - YourHelp is Needed

2006-02-25 Thread Scott M Stark
At a minimum there needs to be a placeholder issue in the http://jira.jboss.com/jira/browse/JBAS project that links to the JBTM issues that need to be completed. Otherwise 4.0.4.GA can go out without anyone actually testing the integration. Beyond that, is this going to be integrated into the

[JBoss-dev] jbossretro-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossretro-testsuite?log=log20060225123519 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jbossretro-testsuite.xml:75: The following error occurred while executing this line:

[JBoss-dev] concurrent-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/concurrent-testsuite?log=log20060225124236 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line:

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

2006-02-25 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log20060225112357 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line:

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

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

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

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