[
https://issues.apache.org/jira/browse/PLUTO-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518817
]
Craig Doremus commented on PLUTO-340:
-------------------------------------
As I stated in the description, this is a trivial bug. You do not need to
select PlutoAdmin as a portlet to deploy. If you want to test the Page Admin
Portlet, select another portlet like AdminPortlet or one of the testsuite
portlets. If you want to deploy your own portlet custom, it's best to create a
new page for it. At any rate, please review the Help file (help mode) to see
how to use the Page Administrator Portlet. We should fix this bug, but it
should not be cropping up in normal use of the portal driver.
> Page Admin Portlet lists a fictitious PlutoAdmin portlet when the Apache
> Pluto Portal Driver portlet application is selected
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-340
> URL: https://issues.apache.org/jira/browse/PLUTO-340
> Project: Pluto
> Issue Type: Bug
> Components: portlets-admin
> Affects Versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4
> Reporter: Craig Doremus
> Priority: Minor
>
> On the Pluto Page Administrator portlet when you select the Apache Pluto
> Portal Driver application in the Portlet Applications drop down, you get a
> PlutoAdmin selection in the adjacent drop-down (along with About Portlet and
> Pluto Page Admin). Selecting this fictitious portlet and adding it to a page
> results in a portlet window with a stack trace inside.
> At this point, this issue is more of an annoyance than a show-stopping bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
