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 "Gonzalo Aguilar (JIRA)" <ji...@apache.org> on 2009/05/29 14:23:45 UTC

[jira] Commented: (PLUTO-567) Make Pluto work even if main portlets are not available.

    [ https://issues.apache.org/jira/browse/PLUTO-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714428#action_12714428 ] 

Gonzalo Aguilar commented on PLUTO-567:
---------------------------------------

Hi Ate

I'm sorry. I cannot use svn because eclipse updated repository to a newer version than I have. So I have to stick with Eclipse svn capabilities. I will recheck how to do it right. 

I will upgrade this with the comments you sent me and resend a clean patch. 

Thanks again.


> Make Pluto work even if main portlets are not available.
> --------------------------------------------------------
>
>                 Key: PLUTO-567
>                 URL: https://issues.apache.org/jira/browse/PLUTO-567
>             Project: Pluto
>          Issue Type: Bug
>            Reporter: Gonzalo Aguilar
>             Fix For: 2.0.1
>
>         Attachments: handle-config-and-portlet-missing.patch, PLUTO-567-patch-cleaned-up.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Pluto stops when a portlet is not available to the container. 
> A small patch will be provided to let the container run even if no portlets are available. 

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