[
https://issues.apache.org/jira/browse/PLUTO-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Griffin closed PLUTO-686.
------------------------------
Resolution: Fixed
Fix Version/s: 3.0.1
Fixed by using a Maven profile to define what the expected options should be.
For more information see commits
[a7eeb6f66169b7cefe1ff7ed836bd84646e96c8a|https://github.com/apache/portals-pluto/commit/a7eeb6f66169b7cefe1ff7ed836bd84646e96c8a]
and
[c573052f11d9b55d105eccf8f7e7d5b42b360dcb|https://github.com/apache/portals-pluto/commit/c573052f11d9b55d105eccf8f7e7d5b42b360dcb].
> TCK: Contesting tests that invoke portletConfig.getContainerRuntimeOptions
> --------------------------------------------------------------------------
>
> Key: PLUTO-686
> URL: https://issues.apache.org/jira/browse/PLUTO-686
> Project: Pluto
> Issue Type: Bug
> Components: tck
> Affects Versions: 3.0.0
> Reporter: Vernon Singleton
> Assignee: Neil Griffin
> Priority: Minor
> Fix For: 3.0.1
>
>
> The following tests assume that the portlet container will have the
> javax.portlet.servletDefaultSessionScope runtime option or they assume that
> will have at least 2 options:
> * V2PortletTests_PortletConfig_ApiRender_getContainerRuntimeOptions1
> * V2PortletTests_PortletConfig_ApiRender_getContainerRuntimeOptions2
> * V2PortletTests_PortletConfig_ApiRender_getContainerRuntimeOptions3
> Runtime options are options, so a container may not be forced to implement
> the javax.portlet.servletDefaultSessionScope option.
> The tck should be adjusted to allow each container to specify how many
> options it has for these checks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
