TESTS FAILED |
Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:61: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:114: 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: 11/20/2006 20:00:59 |
Time to build: 73 minutes 38 seconds |
Last changed: 11/20/2006 18:56:02 |
Last log entry: deprecate FQN |
Unit Tests: (2476) Total Errors and Failures: (102) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Modifications since last build: (first 50 of 141) | ||||
5696 | modified | julien@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/FQN.java | deprecate FQN |
5693 | modified | roy.russo@jboss.com | //trunk/core/src/resources/portal-core-war/WEB-INF/jsp/dashboard/editpage.jsp | stub dashboard ui |
5693 | modified | roy.russo@jboss.com | //trunk/core/src/main/org/jboss/portal/core/portlet/dashboard/Configurator.java | stub dashboard ui |
5692 | modified | julien@jboss.com | //trunk/core/src/main/org/jboss/portal/core/deployment/jboss/PortletAppDeployment.java | JBPORTAL-1015 : Allow reconfiguration of a portlet instance from the deployment descriptor portlet-instances.xml |
5692 | modified | julien@jboss.com | //trunk/core/src/resources/portal-core-sar/portal-aop.xml | JBPORTAL-1015 : Allow reconfiguration of a portlet instance from the deployment descriptor portlet-instances.xml |
5692 | modified | julien@jboss.com | //trunk/core/src/resources/portal-samples-war/WEB-INF/portlet-instances.xml | JBPORTAL-1015 : Allow reconfiguration of a portlet instance from the deployment descriptor portlet-instances.xml |
5692 | modified | julien@jboss.com | //trunk/core/src/main/org/jboss/portal/core/metadata/InstanceMetaData.java | JBPORTAL-1015 : Allow reconfiguration of a portlet instance from the deployment descriptor portlet-instances.xml |
5692 | modified | julien@jboss.com | //trunk/core/src/main/org/jboss/portal/core/deployment/jboss/ObjectDeployment.java | JBPORTAL-1015 : Allow reconfiguration of a portlet instance from the deployment descriptor portlet-instances.xml |
5691 | modified | roy.russo@jboss.com | //trunk/core/src/main/org/jboss/portal/core/portlet/dashboard/Configurator.java | stub dashboard ui |
5691 | modified | roy.russo@jboss.com | //trunk/core/src/main/org/jboss/portal/core/ui/configurator/InvokePortletRenderCommand.java | stub dashboard ui |
5691 | modified | roy.russo@jboss.com | //trunk/core/src/resources/portal-core-war/WEB-INF/portlet.xml | stub dashboard ui |
5691 | modified | roy.russo@jboss.com | //trunk/core/src/resources/portal-core-war/WEB-INF/portlet-instances.xml | stub dashboard ui |
5690 | modified | julien@jboss.com | //trunk/core/src/main/org/jboss/portal/core/deployment/jboss/PortletAppDeployment.java | minor improvement on javadoc |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/container/PortletApplicationRegistry.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/CacheInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/SessionInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/container/PortletApplicationRegistryImpl.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/ModeInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/container/PortletContainerInvoker.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/MetaInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/container/PortletContainerRegistryListener.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/SecurityInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/container/PortletContainer.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/CapabilitiesInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/PortletInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/container/PortletApplicationImpl.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/test/portlet/info/PreferenceInfoTest.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5689 | modified | julien@jboss.com | //trunk/portlet/src/main/org/jboss/portal/portlet/aspects/portlet/ValveInterceptor.java | - let the PortetContainerInvoker produce a Portlet implementation in front of the PortletContainer- the portlet container now does not have the notion of an ID unique among all portlet applications as it should not have (it can only now the id=name in the same application)- leverage the portlet container registry listener to have the PortletContainerInvoker be aware of the container registrations/unregistrations so it can create the appropriate Portlet implementation that it will return |
5688 | modified | julien@jboss.com | //trunk/build/ide/intellij/idea60/modules/cms/cms.iml | project file udpate improvements |
5688 | modified | julien@jboss.com | //trunk/build/ide/intellij/idea60/modules/bridge/bridge.iml | project file udpate improvements |
5688 | modified | julien@jboss.com | //trunk/build/ide/intellij/idea60/modules/core/core.iml | project file udpate improvements |
5687 | modified | julien@jboss.com | //trunk/federation/src/main/org/jboss/portal/federation/FederatingPortletInvoker.java | return the federated invoker on invoker registration |
5687 | modified | julien@jboss.com | //trunk/federation/src/main/org/jboss/portal/federation/impl/FederatingPortletInvokerService.java | return the federated invoker on invoker registration |
5686 | added | roy.russo@jboss.com | //trunk/core/src/resources/portal-core-war/WEB-INF/jsp/dashboard/editpage.jsp | stub dashboard ui |
5686 | added | roy.russo@jboss.com | //trunk/core/src/resources/portal-core-war/WEB-INF/jsp/dashboard | stub dashboard ui |
5686 | added | roy.russo@jboss.com | //trunk/core/src/resources/portal-core-war/WEB-INF/jsp/dashboard/addpage.jsp | stub dashboard ui |
5686 | added | roy.russo@jboss.com | //trunk/core/src/main/org/jboss/portal/core/portlet/dashboard | stub dashboard ui |
5686 | added | roy.russo@jboss.com | //trunk/core/src/main/org/jboss/portal/core/portlet/dashboard/Configurator.java | stub dashboard ui |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/tag/RegionTagHandler.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/strategy/StrategyContext.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/impl/render/empty/EmptyPortletRenderer.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/deployment/jboss/LayoutDeployment.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/tag/PortletTagHandler.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/ThemeLink.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/impl/LayoutServiceImpl.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/deployment/jboss/ThemeDeployment.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/impl/render/div/DivDecorationRenderer.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/impl/render/div/DivWindowRenderer.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/LayoutDispatcher.java | - removed log4j dependencies |
5685 | modified | roy.russo@jboss.com | //trunk/theme/src/main/org/jboss/portal/theme/impl/strategy/MaximizingStrategyImpl.java | - removed log4j dependencies |