[JBoss-dev] jboss-portal-2.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20050917020033 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-portal.xml:153: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/17/2005 02:00:33Time to build: 3 minutes 15 secondsLast changed: 09/17/2005 01:32:19Last log entry: integrating jcrcms security configuration Unit Tests: (67) Total Errors and Failures: (25)testAorg.jboss.portal.test.cms.stress.ConcurrentTestCasetestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestFindUser1org.jboss.portal.test.core.RoleModelTestCasetestFindUser2org.jboss.portal.test.core.RoleModelTestCasetestFindUsersorg.jboss.portal.test.core.RoleModelTestCasetestCreateUserorg.jboss.portal.test.core.RoleModelTestCasetestCreateRoleorg.jboss.portal.test.core.RoleModelTestCasetestCountUserorg.jboss.portal.test.core.RoleModelTestCasetestRemoveNonExistingRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveUserorg.jboss.portal.test.core.RoleModelTestCasetestFindRolesorg.jboss.portal.test.core.RoleModelTestCasetestFindRoleMembersorg.jboss.portal.test.core.RoleModelTestCasetestResourceBundleorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestResourceBundleCascadeorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestGetResourceBundleDuringInitorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCase Modifications since last builds: (first 50 of 11)1.11modifiedrussocms/src/resources/portal-cms-sar/META-INF/jboss-service.xmlintegrating jcrcms security configuration1.7modifiedrussocore/src/resources/portal-cms-sar/META-INF/jboss-service.xmlintegrating jcrcms security configuration1.5modifiedrussocore/src/resources/portal-core-sar/conf/login-config.xmlintegrating jcrcms security configuration1.10modifiedrussocms/src/resources/portal-cms-sar/META-INF/jboss-service.xmlintegrating jcr cms1.49modifiedrussocore/build.xmlintegrating jcr cms1.6modifiedrussocore/src/resources/portal-cms-sar/META-INF/jboss-service.xmlintegrating jcr cms1.3modifiedrussocore/src/resources/portal-cms-war/WEB-INF/web.xmlintegrating jcr cms1.9modifiedrussocore/src/resources/portal-core-war/WEB-INF/web.xmlintegrating jcr cms1.20modifiedrussotools/etc/buildfragments/libraries.entintegrating jcr cms1.16modifiedrussocms/build.xmlintegrating jcr cms1.14modifiedrussocore/src/main/org/jboss/portal/core/portlet/catalog/CatalogPortlet.javawindowstate bug
[JBoss-dev] jboss-3.2-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050917012645 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-common.xml:168: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-common.xml:62: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 09/17/2005 01:26:45Time to build: 9 minutes 9 secondsLast changed: 09/17/2005 00:58:32Last log entry: JBAS-2265, cleanup the dumping of the default InitialContext env to avoid the unnecessary type casts. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 1)1.34.2.14modifiedstarksmserver/src/main/org/jboss/naming/NamingService.javaJBAS-2265, cleanup the dumping of the default InitialContext env to avoid the unnecessary type casts.
[JBoss-dev] jboss-portal-2.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20050917012313 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-portal.xml:153: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/17/2005 01:23:13Time to build: 3 minutes 14 secondsLast changed: 09/17/2005 00:59:28Last log entry: integrating jcr cms Unit Tests: (67) Total Errors and Failures: (25)testAorg.jboss.portal.test.cms.stress.ConcurrentTestCasetestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestFindUser1org.jboss.portal.test.core.RoleModelTestCasetestFindUser2org.jboss.portal.test.core.RoleModelTestCasetestFindUsersorg.jboss.portal.test.core.RoleModelTestCasetestCreateUserorg.jboss.portal.test.core.RoleModelTestCasetestCreateRoleorg.jboss.portal.test.core.RoleModelTestCasetestCountUserorg.jboss.portal.test.core.RoleModelTestCasetestRemoveNonExistingRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveUserorg.jboss.portal.test.core.RoleModelTestCasetestFindRolesorg.jboss.portal.test.core.RoleModelTestCasetestFindRoleMembersorg.jboss.portal.test.core.RoleModelTestCasetestResourceBundleorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestResourceBundleCascadeorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestGetResourceBundleDuringInitorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCase Modifications since last builds: (first 50 of 8)1.10modifiedrussocms/src/resources/portal-cms-sar/META-INF/jboss-service.xmlintegrating jcr cms1.49modifiedrussocore/build.xmlintegrating jcr cms1.6modifiedrussocore/src/resources/portal-cms-sar/META-INF/jboss-service.xmlintegrating jcr cms1.3modifiedrussocore/src/resources/portal-cms-war/WEB-INF/web.xmlintegrating jcr cms1.9modifiedrussocore/src/resources/portal-core-war/WEB-INF/web.xmlintegrating jcr cms1.20modifiedrussotools/etc/buildfragments/libraries.entintegrating jcr cms1.16modifiedrussocms/build.xmlintegrating jcr cms1.14modifiedrussocore/src/main/org/jboss/portal/core/portlet/catalog/CatalogPortlet.javawindowstate bug
[JBoss-dev] jboss-remoting-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite?log=log20050916215544 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-remoting.xml:35: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 09/16/2005 21:55:44Time to build: 14 secondsLast changed: 09/16/2005 13:36:03Last log entry: Small change on jrunit.jar (Throwing exception when X is not available) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 5)1.5modifiedcsuconiclib/jboss/jrunit.jarSmall change on jrunit.jar (Throwing exception when X is not available)1.15modifiedrsigalsrc/main/org/jboss/remoting/transport/multiplex/Protocol.javaAdded timeout for Request Manager Shutdown.Removed Server Socket Query.1.8modifiedrsigalsrc/main/org/jboss/remoting/transport/multiplex/MultiplexingInputStream.javacosmetic.1.2modifiedrsigalsrc/main/org/jboss/remoting/transport/multiplex/MultiplexingDataInputStream.javacosmetic.1.8modifiedrsigalsrc/main/org/jboss/remoting/transport/multiplex/InputMultiplexor.java*** empty log message ***
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20050916212805 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-JBossCache.xml:77: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/16/2005 21:28:05Time to build: 27 minutes 29 secondsLast changed: 09/16/2005 16:57:16Last log entry: unit test is under tests now and examples is for individual updBug fix. Unit Tests: (976) Total Errors and Failures: (6)testConcurrentUpgradeorg.jboss.cache.transaction.DeadlockTesttestMoreThanOneUpgraderorg.jboss.cache.transaction.DeadlockTesttestReadCommittedorg.jboss.cache.lock.LockTesttest2ReadersAnd1Writerorg.jboss.cache.lock.ReentrantWriterPreferenceReadWriteLockTesttestConcurrentAccessWithRWLockorg.jboss.cache.transaction.ConcurrentTransactionalTesttestReadCommittedorg.jboss.cache.transaction.IsolationLevelReadCommittedTest Modifications since last builds: (first 50 of 8)1.9modifiedbwangexamples/aop/sensor/article/pojocache.htmlunit test is under tests now and examples is for individual updBug fix.1.4modifiedcsuconiclib/jrunit.jarJBBENCH-45 - Updating reporter version1.8modifiedbstansberryexamples/aop/sensor/article/pojocache.htmlCopy edits prior to publication.1.7modifiedbwangexamples/aop/sensor/article/pojocache.htmlswitched to png1.1addedbwangexamples/aop/sensor/article/image/object_split.pngadded1.1addedbwangexamples/aop/sensor/article/image/propagation_object.pngadded1.1addedbwangexamples/aop/sensor/article/image/propagation_overview.pngadded1.1addedbwangexamples/aop/sensor/article/image/propagation_topology.pngadded
[JBoss-dev] jboss-portal-2.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20050916212425 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-portal.xml:153: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/16/2005 21:24:25Time to build: 3 minutes 25 secondsLast changed: 09/16/2005 11:18:50Last log entry: windowstate bug Unit Tests: (67) Total Errors and Failures: (25)testAorg.jboss.portal.test.cms.stress.ConcurrentTestCasetestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestFindUser1org.jboss.portal.test.core.RoleModelTestCasetestFindUser2org.jboss.portal.test.core.RoleModelTestCasetestFindUsersorg.jboss.portal.test.core.RoleModelTestCasetestCreateUserorg.jboss.portal.test.core.RoleModelTestCasetestCreateRoleorg.jboss.portal.test.core.RoleModelTestCasetestCountUserorg.jboss.portal.test.core.RoleModelTestCasetestRemoveNonExistingRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveUserorg.jboss.portal.test.core.RoleModelTestCasetestFindRolesorg.jboss.portal.test.core.RoleModelTestCasetestFindRoleMembersorg.jboss.portal.test.core.RoleModelTestCasetestResourceBundleorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestResourceBundleCascadeorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestGetResourceBundleDuringInitorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCase Modifications since last builds: (first 50 of 1)1.14modifiedrussocore/src/main/org/jboss/portal/core/portlet/catalog/CatalogPortlet.javawindowstate bug
[JBoss-dev] RE: Clustering as a standalone? (wasRE:[JBoss-dev]RE:[jboss-cvs]jbossmx/src/main/org/jboss/ha/jndi/treecache ...)
Sigh! The integration issue has nothing to do whether you have one or multiple jars. If look at the current code base for 4.x and head, none of the Clustering code depends specifically on the Jgroups version, for example. We agree that Clustering is an aspect. So there is no reason why the same aspect library can't work both in 4.0 and head. So when we upgrade in the future, we upgrade as an aspect (meaning cluster, jboss cache and jgroups jar together). You certify on one clustering stack/version. It is easier for everybody. -Ben -Original Message- From: Adrian Brock Sent: Friday, September 16, 2005 2:32 PM To: Ben Wang Cc: jboss-development@lists.sourceforge.net; Jerry Gauthier; [EMAIL PROTECTED]; QA Subject: RE: Clustering as a standalone? (wasRE:[JBoss-dev]RE:[jboss-cvs]jbossmx/src/main/org/jboss/ha/jndi/treec ache ...) On Fri, 2005-09-16 at 17:26, Adrian Brock wrote: > NADA. Clustering == replication, failover, load balancing Integration > == Tomcat, EJB3, etc. Since it is not obvious. By providing one module that *integrates* jgroups/JBossCache/Tomcat/EJB3/Others in one jar, you are effectively locking all these together at the version you compiled over/tested. Clustering is not the abitrator of which versions of Tomcat, Hibernate, Remoting, etc. gets used by other projects. Clustering should dance to the integration project's tune. -- Adrian Brock Chief Scientist JBoss Inc. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: Clustering as a standalone? (was RE:[JBoss-dev]RE:[jboss-cvs]jbossmx/src/main/org/jboss/ha/jndi/treecache ...)
On Fri, 2005-09-16 at 17:26, Adrian Brock wrote: > NADA. Clustering == replication, failover, load balancing > Integration == Tomcat, EJB3, etc. Since it is not obvious. By providing one module that *integrates* jgroups/JBossCache/Tomcat/EJB3/Others in one jar, you are effectively locking all these together at the version you compiled over/tested. Clustering is not the abitrator of which versions of Tomcat, Hibernate, Remoting, etc. gets used by other projects. Clustering should dance to the integration project's tune. -- Adrian Brock Chief Scientist JBoss Inc. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: Clustering as a standalone? (was RE:[JBoss-dev]RE:[jboss-cvs]jbossmx/src/main/org/jboss/ha/jndi/treecache ...)
No quite sure what you meant? But if I understand it correctly, then I think the future clustering will consist of 3 key jar files: Jgroups.jar, jboss-cache.jar, and jboss-clustering.jar Where jboss-clustering will consists packages from current Clustering module, Tomcat layer, and ejb3 (ha-remoting & sfsb). Of course if fine-grained is needed, jboss-aop.jar, trove.jar, and qdox.jar will also be needed. -Ben -Original Message- From: Adrian Brock Sent: Friday, September 16, 2005 11:11 AM To: Ben Wang Cc: jboss-development@lists.sourceforge.net; Jerry Gauthier; [EMAIL PROTECTED]; QA Subject: RE: Clustering as a standalone? (was RE:[JBoss-dev]RE:[jboss-cvs]jbossmx/src/main/org/jboss/ha/jndi/treecache ...) On Fri, 2005-09-16 at 01:43, Ben Wang wrote: > It is to the opposite. If we do a better job of packaging and > consolidate the jar files, we wouldn't have so many jboss-related jar > files currently distributed with JBossCache. So prove to me that you can do this for JBossCache then we can consider it for clustering. :-) -- Adrian Brock Chief Scientist JBoss Inc. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
