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

Ate Douma updated JS2-871:
--------------------------

    Summary: Upgrade Pluto container to version 2.0.0 with Portlet 2.0/JSR-286 
support  (was: Upgrade Pluto container to version 2.0 for up-to-date JSR-168 
support)

Updating this issue summary to indicate this now does cover JSR-286 support for 
Jetspeed release 2.2 already.
All tests of the JSR-286 TCK are passing on the upgraded Jetspeed-2 trunk too: 
time to close this issue as completed.

> Upgrade Pluto container to version 2.0.0 with Portlet 2.0/JSR-286 support
> -------------------------------------------------------------------------
>
>                 Key: JS2-871
>                 URL: https://issues.apache.org/jira/browse/JS2-871
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Container
>    Affects Versions: 2.2
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>            Priority: Critical
>             Fix For: 2.2
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Pluto 2.0 is currently undergoing refactoring (see Pluto branch 
> 2.0-spi-refactoring) to restore the ability to incorporate it back in larger 
> scale Portals like Jetspeed-2.
> The currently used Pluto 1.0.1 container is outdated and we need to get back 
> in sync with Pluto trunk development ASAP.
> Note: the target for this upgrade is JSR-168 only (for now).
> Adding JSR-286 (Portlet API 2.0) will be a follow up task for the next major 
> Jetspeed 2 release (2.3 or higher).
> One particular important integration point is the Portlet Preferences. 
> JS2-869 targets a complete rewrite of the Jetspeed Preferences backend and 
> that issue should take the new Pluto 2.0 model and API into account. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to