[
https://issues.apache.org/jira/browse/PLUTO-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499615
]
Andreas Foerster commented on PLUTO-340:
----------------------------------------
Hi,
I checked out the 1.1.3 pluto release from the repo but unfortunately, there is
still this exception. I mean, in PLUTO-355 there is the way described how to
deploy a portlet without the help of the Apache Pluto Portal Admin portlet.
But to be honest, this way is very annoying and costs a lot of time. Is there
any way to solve this issue so I can deploy portlets with just a few clicks?
By the way, I tried to build the latest pluto release:
svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ pluto
but it failed because of an uncompleted test.
The build of the 1.1.3 release was successful with a Tomcat 5.5.9:
svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.3
pluto
> 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
> 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.
