View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.6-testsuite?log=log20070423200017

TESTS FAILED
Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:204: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.
Date of build: 04/23/2007 20:00:17
Time to build: 110 minutes 39 seconds
Last changed: 04/23/2007 18:47:04
Last log entry: removed unused code

 Unit Tests: (2418)  Total Errors and Failures: (14)
testGetterOverrideorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_4_GA)
testAttributesAreNotCachedorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_4_GA)
testStaticAttributeorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_4_GA)
testGetterOverrideorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_5_GA)
testAttributesAreNotCachedorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_5_GA)
testStaticAttributeorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_5_GA)
testGetterOverrideorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_x)
testAttributesAreNotCachedorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_x)
testStaticAttributeorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_x)
testGetPortletPropertyDescriptionorg.jboss.portal.test.wsrp.v1.producer.PortletManagementTestRunner(4_0_4_GA)
testModifyRegistrationorg.jboss.portal.test.wsrp.v1.producer.RegistrationTestRunner(4_0_4_GA)
testDeregisterorg.jboss.portal.test.wsrp.v1.producer.RegistrationTestRunner(4_0_4_GA)
testGetServiceDescriptionRequiringRegistrationOfferedPortletsorg.jboss.portal.test.wsrp.v1.producer.ServiceDescriptionTestRunner(4_0_4_GA)
testGetServiceDescriptionRequiringRegistrationNoOfferedPortletsorg.jboss.portal.test.wsrp.v1.producer.ServiceDescriptionTestRunner(4_0_4_GA)
 

 Modifications since last build:  (first 50 of 73)
7036modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/portal/command/render/RenderPageCommand.javaremoved unused code
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/ControllerContext.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/command/mapper/URLFactory.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/instance/InstanceURLFactory.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/command/mapper/DelegatingURLFactoryService.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/portal/PortalObjectURLFactory.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core-cms/src/main/org/jboss/portal/core/cms/CMSObjectURLFactory.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/classic/ThrowableResponseHandler.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7035modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/command/mapper/SimpleURLFactory.javaadded ControllerContext in the signature of the doMapping(...) of URLFactory
7034modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/InstanceManagerBean.javaconsistent behavior when clicking update/cancel from security editor go to portal object page (the udpate was going to the parent of the portal object)
7034addedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/AuthorizationBean.javaconsistent behavior when clicking update/cancel from security editor go to portal object page (the udpate was going to the parent of the portal object)
7034modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PortalObjectManagerBean.javaconsistent behavior when clicking update/cancel from security editor go to portal object page (the udpate was going to the parent of the portal object)
7034deletedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/AbstractAuthorizationBean.javaconsistent behavior when clicking update/cancel from security editor go to portal object page (the udpate was going to the parent of the portal object)
7033modifiedjulien@jboss.com//trunk/core-admin/src/resources/portal-admin-war/WEB-INF/jsf/editPortalSecurity.xhtmlsecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/InstanceManagerBean.javasecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/resources/portal-admin-war/WEB-INF/jsf/common/editSecurity.xhtmlsecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PortalObjectManagerBean.javasecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/AbstractAuthorizationBean.javasecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PortletManagerBean.javasecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/resources/portal-admin-war/WEB-INF/jsf/instances.xhtmlsecurity update/cancel was not working properly : fixes that
7033modifiedjulien@jboss.com//trunk/core-admin/src/resources/portal-admin-war/WEB-INF/jsf/editPageSecurity.xhtmlsecurity update/cancel was not working properly : fixes that
7032modifiedjulien@jboss.com//trunk/core/src/resources/portal-core-sar/conf/standardjboss-portlet.xmlrenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/aspects/portlet/AjaxInterceptor.javarenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/deployment/JBossApplicationMetaDataFactory.javarenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/impl/model/content/InternalContentProvider.javarenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/metadata/portlet/AjaxMetaData.javarenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core-samples/src/resources/portal-samples-war/WEB-INF/jboss-portlet.xmlrenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core/src/resources/portal-core-sar/dtd/jboss-portlet_2_6.dtdrenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7032modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/metadata/portlet/JBossPortletMetaData.javarenamed "asynchronous" to "partial-refresh" in jboss-portlet.xml as it describes better the feature, asynchronous is not precise enough
7031modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/ns/NavigationalStateKey.javamake CachedUserImpl and NSKey serializable for clustering
7030modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/portlet/CachedUserImpl.javamake CachedUserImpl and NSKey serializable for clustering
7030modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/ns/NavigationalStateKey.javamake CachedUserImpl and NSKey serializable for clustering
7029modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PropertyInfo.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PropertiesBean.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/actions/PropertyAction.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029deletedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PropertiesFilter.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PreferencesBean.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PortalObjectManagerBean.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/resources/portal-admin-war/WEB-INF/faces-config.xml- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/main/org/jboss/portal/core/admin/ui/PropertyBean.java- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7029modifiedjulien@jboss.com//trunk/core-admin/src/resources/portal-admin-war/WEB-INF/jsf/common/editProperties.xhtml- portal object property editor updates were not persisted in backend implying a reset of properties set at runtime on next reboot- update the property editor layout to be more usable and use correct CSS class names
7028modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/portal/DefaultPortalCommandFactory.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/instance/InstanceCommandFactory.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/wsrp/src/main/org/jboss/portal/wsrp/consumer/portlet/WSRPPortlet.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/command/mapper/DelegatingCommandFactoryService.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/command/mapper/SimpleCommandFactory.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/Controller.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/bridge/build.xml- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/portlet/src/main/org/jboss/portal/portlet/aspects/portlet/WindowStatesInterceptor.java- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue
7028modifiedjulien@jboss.com//trunk/jems/build.xml- fix for JBPORTAL-1315 : Portlets "forget" that they are in EDIT mode- added modules-package-tests so it is possible to package tests all modules with the build/build.xml file- remove the nav state scope from the server module- pass the ControllerContext as part of the doMapping(...) in CommandFactories so they can retrieve the nav state scope correctly- updated fix that Thomas did for the prb with the maximized/normal window issue