[ 
https://issues.apache.org/jira/browse/PLUTO-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Griffin closed PLUTO-673.
------------------------------
    Resolution: Fixed

Fixed in commit 
[9bc57805cf0693330ea064abb3536744e9ff56fc|https://github.com/apache/portals-pluto/commit/9bc57805cf0693330ea064abb3536744e9ff56fc]

> TCK: Contesting V2EnvironmentTests_PortalContext_ApiRender_getPortalInfo1
> -------------------------------------------------------------------------
>
>                 Key: PLUTO-673
>                 URL: https://issues.apache.org/jira/browse/PLUTO-673
>             Project: Pluto
>          Issue Type: Bug
>          Components: tck
>    Affects Versions: 3.0.0
>            Reporter: Neil Griffin
>            Assignee: Neil Griffin
>             Fix For: 3.0.1
>
>
> The Javadoc for 
> [PortalContext.getPortalInfo()|https://portals.apache.org/pluto/portlet-3.0-apidocs/javax/portlet/PortalContext.html#getPortalInfo()]
>  states:
> {quote}
> Returns information about the portal like vendor, version, etc.
> The form of the returned string is servername/versionnumber. For example, the 
> reference implementation Pluto may return the string Pluto/1.0.
> The portlet container may return other optional information after the primary 
> string in parentheses, for example, Pluto/1.0 (JDK 1.3.1; Windows NT 4.0 x86).
> {quote}
> The Portlet 2.0 TCK simply tested for a non-null return value. But 
> V2EnvironmentTests_PortalContext_ApiRender_getPortalInfo1 in the Portlet 3.0 
> TCK mandates that spaces are not permitted.
> This test fails on Liferay Portal because the return value is "Liferay 
> Community Edition Portal / 7.1.0"
> Since the Portlet 2.0 TCK did not test for spaces and there is no explicit 
> requirement stated in the Javadoc that spaces are not allowed in the return 
> value, the recommendation would be to modify the test to permit spaces.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to