You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2007/05/19 18:00:16 UTC
[jira] Created: (PLUTO-368) Create testsuite tests for JSR-286
portlet filters
Create testsuite tests for JSR-286 portlet filters
--------------------------------------------------
Key: PLUTO-368
URL: https://issues.apache.org/jira/browse/PLUTO-368
Project: Pluto
Issue Type: Test
Components: portlets-testsuite
Affects Versions: 1.1-286-COMPATIBILITY
Reporter: Craig Doremus
Fix For: 1.1-286-COMPATIBILITY
Testsuite tests need to be created to test JSR-286 portlet filters. This is necessary to make sure merging the 1.1-286-COMPATIBILITY branch with the Pluto trunk and any other 1.1-286-COMPATIBILITY branch refactorings does not break this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-368) Add portlet filter tests to testsuite
for JSR-286
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-368:
--------------------------------
Fix Version/s: 1.1-286-trunk-merge
Affects Version/s: 1.1-286-trunk-merge
Summary: Add portlet filter tests to testsuite for JSR-286 (was: Create testsuite tests for JSR-286 portlet filters)
> Add portlet filter tests to testsuite for JSR-286
> -------------------------------------------------
>
> Key: PLUTO-368
> URL: https://issues.apache.org/jira/browse/PLUTO-368
> Project: Pluto
> Issue Type: Test
> Components: portlets-testsuite
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Craig Doremus
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>
> Testsuite tests need to be created to test JSR-286 portlet filters. This is necessary to make sure merging the 1.1-286-COMPATIBILITY branch with the Pluto trunk and any other 1.1-286-COMPATIBILITY branch refactorings does not break this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-368) Add portlet filter tests to testsuite
for JSR-286
Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549899 ]
Benjamin Gould commented on PLUTO-368:
--------------------------------------
I've attached the beginnings of some PortletFilter tests to PLUTO-442, because the patch mostly contained code that will be used by all of the JSR 286 compatibility tests. Future additions to the Portlet Filter tests should be attached to this issue.
> Add portlet filter tests to testsuite for JSR-286
> -------------------------------------------------
>
> Key: PLUTO-368
> URL: https://issues.apache.org/jira/browse/PLUTO-368
> Project: Pluto
> Issue Type: Test
> Components: portlets-testsuite
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Craig Doremus
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>
> Testsuite tests need to be created to test JSR-286 portlet filters. This is necessary to make sure merging the 1.1-286-COMPATIBILITY branch with the Pluto trunk and any other 1.1-286-COMPATIBILITY branch refactorings does not break this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-368) Add portlet filter tests to testsuite
for JSR-286
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552556 ]
Craig Doremus commented on PLUTO-368:
-------------------------------------
Added back SupportedModesServiceImpl.loadPortletModes() from 1.1-286-COMPATIBILITY branch and its call in init so that FilterManagerImpl can be initialized too. Thanks to Christian for his suggestion to look at this class (see https://issues.apache.org/jira/browse/PLUTO-371#action_12552555).
The FilterManager stuff should be refactored out of SupportedModesServiceImpl into a service class that DriverConfiguration initializes at portal startup.
> Add portlet filter tests to testsuite for JSR-286
> -------------------------------------------------
>
> Key: PLUTO-368
> URL: https://issues.apache.org/jira/browse/PLUTO-368
> Project: Pluto
> Issue Type: Test
> Components: portlets-testsuite
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Craig Doremus
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>
> Testsuite tests need to be created to test JSR-286 portlet filters. This is necessary to make sure merging the 1.1-286-COMPATIBILITY branch with the Pluto trunk and any other 1.1-286-COMPATIBILITY branch refactorings does not break this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (PLUTO-368) Add portlet filter tests to testsuite
for JSR-286
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus closed PLUTO-368.
-------------------------------
Resolution: Fixed
The tests were added to the testsuite back in SVN rev 604407 and 604408.
> Add portlet filter tests to testsuite for JSR-286
> -------------------------------------------------
>
> Key: PLUTO-368
> URL: https://issues.apache.org/jira/browse/PLUTO-368
> Project: Pluto
> Issue Type: Test
> Components: portlets-testsuite
> Affects Versions: 2.0.0, 1.1-286-COMPATIBILITY
> Reporter: Craig Doremus
> Fix For: 2.0.0, 1.1-286-COMPATIBILITY
>
>
> Testsuite tests need to be created to test JSR-286 portlet filters. This is necessary to make sure merging the 1.1-286-COMPATIBILITY branch with the Pluto trunk and any other 1.1-286-COMPATIBILITY branch refactorings does not break this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.