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 "ZHENG Zhong (JIRA)" <ji...@apache.org> on 2006/02/17 18:35:24 UTC
[jira] Created: (PLUTO-215) Create admin portlet for Pluto portal
driver
Create admin portlet for Pluto portal driver
--------------------------------------------
Key: PLUTO-215
URL: http://issues.apache.org/jira/browse/PLUTO-215
Project: Pluto
Type: New Feature
Components: portal driver
Versions: 1.1.0
Reporter: ZHENG Zhong
Fix For: 1.1.0
Create admin portlet for Pluto portal driver to make it easier to
assemble/deploy/publish portlet apps to Pluto.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "David H. DeWolf" <dd...@apache.org>.
Zhong ZHENG wrote:
> Hi, Patrick,
>
> The pluto-maven-plugin is just a maven adaptor, and all the actual job
> (assemble/deploy)
> is done by the pluto-util module. I think the pluto-util module already
> contains all the
> functionality the admin portlet needs.
>
Agreed. The maven plugin is not needed. Just use the util api --
that's why it was seperated out.
> In addition, it will be convenient if the admin portlet can publish the
> deployed portlets to
> portal. Currently this could only be done by manually editing the portal
> driver config file.
> It will be great if there is an additional step in the flow to
> automatically inject information
> to the portal config file. We don't need something complex to customize
> the portlet layout,
> just adding all deployed portlets to the portal page will be OK.
Agreed. The programmatic hooks for this are allready in place. In
fact, I've successfully been able to "publish" through a simple GET
request to the portal.
Take a look at how the publish tasks do it.
David
>
> Thanks for all your help!
>
> Regards.
>
> On 2/21/06, *Patrick Huber* <stackmagic@gmail.com
> <ma...@gmail.com>> wrote:
>
> Ok, I think I see a way how to do this:
>
> Input from the user:
> - desired context name
> - type of container (tomcat/jetty) if we can't determine this ourselfs
> - a .war file
>
> Flow:
> - make sure all required data is in the request
> - save the uploaded file to a temporary location
> - tell the Assemble Mojo about the webapp and let it do its thing
> - tell the Deployment Mojo about the webapp and let it do its thing
> too. We supply that mojo with the deployer class selected by the user
>
> So we get these dependencies
> - maven-pluto-plugin (19KB)
> - pluto-util (36KB)
> - maven-core (133KB)
> - maven-artifact (77KB)
> - maven-plugin-api (10KB)
> - maven-project (103KB)
> Total: 378KB, just to get an idea....
>
>
> I think this could work quite nice. Please tell me if you're okay with
> including all these maven dependencies or if you see any problems with
> the above idea.
>
> Patrick
>
>
> --
> "I love deadlines. I like the whooshing sound they make as they fly
> by." -- Douglas Adams
>
>
>
>
> --
> ZHENG Zhong
> - http://heavyz.blogspot.com/
> - http://people.apache.org/~zheng/
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Zhong ZHENG <he...@gmail.com>.
Hi, Patrick,
The pluto-maven-plugin is just a maven adaptor, and all the actual job
(assemble/deploy)
is done by the pluto-util module. I think the pluto-util module already
contains all the
functionality the admin portlet needs.
In addition, it will be convenient if the admin portlet can publish the
deployed portlets to
portal. Currently this could only be done by manually editing the portal
driver config file.
It will be great if there is an additional step in the flow to automatically
inject information
to the portal config file. We don't need something complex to customize the
portlet layout,
just adding all deployed portlets to the portal page will be OK.
Thanks for all your help!
Regards.
On 2/21/06, Patrick Huber <st...@gmail.com> wrote:
>
> Ok, I think I see a way how to do this:
>
> Input from the user:
> - desired context name
> - type of container (tomcat/jetty) if we can't determine this ourselfs
> - a .war file
>
> Flow:
> - make sure all required data is in the request
> - save the uploaded file to a temporary location
> - tell the Assemble Mojo about the webapp and let it do its thing
> - tell the Deployment Mojo about the webapp and let it do its thing
> too. We supply that mojo with the deployer class selected by the user
>
> So we get these dependencies
> - maven-pluto-plugin (19KB)
> - pluto-util (36KB)
> - maven-core (133KB)
> - maven-artifact (77KB)
> - maven-plugin-api (10KB)
> - maven-project (103KB)
> Total: 378KB, just to get an idea....
>
>
> I think this could work quite nice. Please tell me if you're okay with
> including all these maven dependencies or if you see any problems with
> the above idea.
>
> Patrick
>
>
> --
> "I love deadlines. I like the whooshing sound they make as they fly
> by." -- Douglas Adams
>
--
ZHENG Zhong
- http://heavyz.blogspot.com/
- http://people.apache.org/~zheng/
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Patrick Huber <st...@gmail.com>.
Hi all
I had a look the admin portlet last week but I'll be pretty busy with
all the exams the next two weeks and the preparations for my diploma
thesis - so I won't have much time.
What I did so far:
- write a portlet and servlet, calling a class named PlutoAdmin
- an instance of PlutoAdmin is stored in the session for later requests
- PlutoAdmin builds on a two-phase model just like the portlet's action/render
- PlutoAdmin then does all the work, it's a controller/adapter to the
assemble and deploy tasks
Problems
- the assemble and deploy tasks don't look really finished, if i had
the time, i'd probably refactor them somewhat
- my initial concept and the concept of the assemble and deploy tasks
don't match so well but that can be fixed
Notes
- wherever something's left to do, there's a TODO comment
- licence should be APL everywhere, if it's not, I have no problem
with changing it to APL. The default in my eclipse is GPL.
- It should all be pretty straightforward. nevertheless, I added some
javadoc comments
- pretty much everything that's missing is some glue between
plutoadmin and the tasks and outputting the responses.
If anyone would like to pick it up from here, download the source from
here: http://www.swisstech.net/files/pluto-admin.tar.gz
I'm sorry I don't have time to continue this, but I also don't want to
stall so I'm giving you what I have so far...
Patrick
2006/2/22, Elliot Metsger <em...@jhu.edu>:
> Hi Patrick,
>
> I have a question below:
>
> Patrick Huber wrote:
> > Ok, I think I see a way how to do this:
>
> <snip>
>
> > Flow:
> > - make sure all required data is in the request
> > - save the uploaded file to a temporary location
> > - tell the Assemble Mojo about the webapp and let it do its thing
> > - tell the Deployment Mojo about the webapp and let it do its thing
> > too. We supply that mojo with the deployer class selected by the user
>
> After the deployment, can we test to make sure that the descriptor files
> can be unmarshalled by the pluto portal up front, in time to notify the
> uploader of the .war (instead of waiting for the "Error invoking
> portlet" when the user loads the page). I will definitly get the exact
> impl classes later but I'm waiting for coffee to brew then I'm off to
> the salt mines, er work.
>
> Here's the situation I ran across when I was working with the
> descriptors sub-project and the effort to create servlet 2.4 descriptors:
>
> With minor modifications descriptors subproject could successfully grok
> an existing servlet 2.4 web.xml (that is, unmarshal it to a WebAppDD)
> and successfully rewrite it with the Pluto servlet wrappers. Great!
> BUT, the problem came when the pluto portal attempted to invoke my
> portlet: the pluto portal was unable to unmarshal the Pluto-modifed web.xml.
>
> I will get exact stacktraces/classes later. That may help clarify -
>
> Thanks,
> Elliot
>
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by Elliot Metsger <em...@jhu.edu>.
Hi Patrick,
I have a question below:
Patrick Huber wrote:
> Ok, I think I see a way how to do this:
<snip>
> Flow:
> - make sure all required data is in the request
> - save the uploaded file to a temporary location
> - tell the Assemble Mojo about the webapp and let it do its thing
> - tell the Deployment Mojo about the webapp and let it do its thing
> too. We supply that mojo with the deployer class selected by the user
After the deployment, can we test to make sure that the descriptor files
can be unmarshalled by the pluto portal up front, in time to notify the
uploader of the .war (instead of waiting for the "Error invoking
portlet" when the user loads the page). I will definitly get the exact
impl classes later but I'm waiting for coffee to brew then I'm off to
the salt mines, er work.
Here's the situation I ran across when I was working with the
descriptors sub-project and the effort to create servlet 2.4 descriptors:
With minor modifications descriptors subproject could successfully grok
an existing servlet 2.4 web.xml (that is, unmarshal it to a WebAppDD)
and successfully rewrite it with the Pluto servlet wrappers. Great!
BUT, the problem came when the pluto portal attempted to invoke my
portlet: the pluto portal was unable to unmarshal the Pluto-modifed web.xml.
I will get exact stacktraces/classes later. That may help clarify -
Thanks,
Elliot
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Patrick Huber <st...@gmail.com>.
Ok, I think I see a way how to do this:
Input from the user:
- desired context name
- type of container (tomcat/jetty) if we can't determine this ourselfs
- a .war file
Flow:
- make sure all required data is in the request
- save the uploaded file to a temporary location
- tell the Assemble Mojo about the webapp and let it do its thing
- tell the Deployment Mojo about the webapp and let it do its thing
too. We supply that mojo with the deployer class selected by the user
So we get these dependencies
- maven-pluto-plugin (19KB)
- pluto-util (36KB)
- maven-core (133KB)
- maven-artifact (77KB)
- maven-plugin-api (10KB)
- maven-project (103KB)
Total: 378KB, just to get an idea....
I think this could work quite nice. Please tell me if you're okay with
including all these maven dependencies or if you see any problems with
the above idea.
Patrick
2006/2/20, David H. DeWolf <dd...@apache.org>:
> On 2/19/06, Patrick Huber <st...@gmail.com> wrote:
> > > Hi, Patrick,
> > > > For the web-service, we could do all the work in a servlet and use a
> > > > portlet as thin frontend. Everything the Portlet does, is dispatching
> > > > the request to the servlet.
> > >
> > > Having some sort of web service is a good idea, but i don't have much
> > > experience on that... i will take a look at that if i have time.
> >
> > By web-service, I actually mean a simple servlet. Nothing that'd
> > include soap and all that stuff. Just a simple servlet, to which a
> > client can upload a war file.
>
> +1 -- me too -- we don't need to go crazy! :)
>
> >
>
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by "David H. DeWolf" <dd...@apache.org>.
On 2/19/06, Patrick Huber <st...@gmail.com> wrote:
> > Hi, Patrick,
> > > For the web-service, we could do all the work in a servlet and use a
> > > portlet as thin frontend. Everything the Portlet does, is dispatching
> > > the request to the servlet.
> >
> > Having some sort of web service is a good idea, but i don't have much
> > experience on that... i will take a look at that if i have time.
>
> By web-service, I actually mean a simple servlet. Nothing that'd
> include soap and all that stuff. Just a simple servlet, to which a
> client can upload a war file.
+1 -- me too -- we don't need to go crazy! :)
>
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Patrick Huber <st...@gmail.com>.
> Hi, Patrick,
> > For the web-service, we could do all the work in a servlet and use a
> > portlet as thin frontend. Everything the Portlet does, is dispatching
> > the request to the servlet.
>
> Having some sort of web service is a good idea, but i don't have much
> experience on that... i will take a look at that if i have time.
By web-service, I actually mean a simple servlet. Nothing that'd
include soap and all that stuff. Just a simple servlet, to which a
client can upload a war file.
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Zhong ZHENG <he...@gmail.com>.
Hi, Patrick,
Thanks for your interests in the pluto admin portlet.
On 2/19/06, Patrick Huber <st...@gmail.com> wrote:
>
> I was already thinking a bit about deployment and we'd probably have
> to have some servlet-container-specific code for each servlet
> container we want to support.
Yes. Currently we are planning to support tomcat and jetty.
Do you think it makes sense to let the deployer enter a context name
> or should we just assume the deployer already includes a
> META-INF/context.xml? I don't know but that file may be
> servlet-container-specific too...
IMHO, auto-generation of context.xml is preferred. The admin portlet
should be able to deploy a *standard* portlet app. All container-specific
configurations (such as tomcat's META-INF/context.xml) should be
auto-generated or configurable via the admin portlet interface.
For the web-service, we could do all the work in a servlet and use a
> portlet as thin frontend. Everything the Portlet does, is dispatching
> the request to the servlet.
Having some sort of web service is a good idea, but i don't have much
experience on that... i will take a look at that if i have time.
Patrick
>
>
> --
> "I love deadlines. I like the whooshing sound they make as they fly
> by." -- Douglas Adams
>
As for introducing some additional dependencies (such as SpringPortlet)
into pluto, IMHO, we should make sure that:
1/ We are not using some early-access libs, since they may be unstable.
2/ We are using some libs that are re-distributable under the apache
license.
Check the maven 2 repository ( http://repo1.maven.org/maven2/ ) to make
sure that the lib is available from there... otherwise, building pluto will
require
that users download the lib and put into their local repo manually.
3/ We use some dependencies because we need them to avoid re-inventing
the wheel... So, before implementing something, we'd better ask ourselves
if using a certain dependency can really save our time and make our code
simpler...
Thanks again for all your help!
Regards.
--
ZHENG Zhong
- http://heavyz.blogspot.com/
- http://people.apache.org/~zheng/
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Patrick Huber <st...@gmail.com>.
I was already thinking a bit about deployment and we'd probably have
to have some servlet-container-specific code for each servlet
container we want to support.
In case of tomcat, a deployer could upload a portlet and the admin
portlet would a) copy that file to the webapps directory or b) use the
tomcat deployer.
I find both methods ok, but in order for b) to work, the manager
webapp has to be deployed and the admin portlet needs to know
user/pass to access the manager webapp. This could be solved by adding
input fields for that information.
Do you think it makes sense to let the deployer enter a context name
or should we just assume the deployer already includes a
META-INF/context.xml? I don't know but that file may be
servlet-container-specific too...
For the web-service, we could do all the work in a servlet and use a
portlet as thin frontend. Everything the Portlet does, is dispatching
the request to the servlet.
Patrick
2006/2/19, David H. DeWolf <dd...@apache.org>:
> I'm personally fine with whatever as long as:
>
> 1) it's an optional portlet
>
> 2) it's not too heavy
>
> though, I do think it's worth having some sort of "web service" or
> deployment servlet that can be used to programmatically deploy through
> clients (i.e. tomcat manager webapp)
>
> David
>
> Patrick Huber wrote:
> > All,
> >
> > in case I find time to do this, are there any constraints on the
> > technology to use? I've gotten pretty used to SpringPortlet in the
> > last months, during my student research project. On the other hand,
> > It's probably a quite small portlet and spring would be total
> > overkill...
> >
> > Patrick
> >
> >
> > 2006/2/17, ZHENG Zhong (JIRA) <ji...@apache.org>:
> >
> >>Create admin portlet for Pluto portal driver
> >>--------------------------------------------
> >>
> >> Key: PLUTO-215
> >> URL: http://issues.apache.org/jira/browse/PLUTO-215
> >> Project: Pluto
> >> Type: New Feature
> >> Components: portal driver
> >> Versions: 1.1.0
> >> Reporter: ZHENG Zhong
> >> Fix For: 1.1.0
> >>
> >>
> >>Create admin portlet for Pluto portal driver to make it easier to
> >>assemble/deploy/publish portlet apps to Pluto.
> >>
> >>--
> >>This message is automatically generated by JIRA.
> >>-
> >>If you think it was sent incorrectly contact one of the administrators:
> >> http://issues.apache.org/jira/secure/Administrators.jspa
> >>-
> >>For more information on JIRA, see:
> >> http://www.atlassian.com/software/jira
> >>
> >>
> >
> >
> >
> > --
> > "I love deadlines. I like the whooshing sound they make as they fly
> > by." -- Douglas Adams
> >
>
>
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "David H. DeWolf" <dd...@apache.org>.
I'm personally fine with whatever as long as:
1) it's an optional portlet
2) it's not too heavy
though, I do think it's worth having some sort of "web service" or
deployment servlet that can be used to programmatically deploy through
clients (i.e. tomcat manager webapp)
David
Patrick Huber wrote:
> All,
>
> in case I find time to do this, are there any constraints on the
> technology to use? I've gotten pretty used to SpringPortlet in the
> last months, during my student research project. On the other hand,
> It's probably a quite small portlet and spring would be total
> overkill...
>
> Patrick
>
>
> 2006/2/17, ZHENG Zhong (JIRA) <ji...@apache.org>:
>
>>Create admin portlet for Pluto portal driver
>>--------------------------------------------
>>
>> Key: PLUTO-215
>> URL: http://issues.apache.org/jira/browse/PLUTO-215
>> Project: Pluto
>> Type: New Feature
>> Components: portal driver
>> Versions: 1.1.0
>> Reporter: ZHENG Zhong
>> Fix For: 1.1.0
>>
>>
>>Create admin portlet for Pluto portal driver to make it easier to
>>assemble/deploy/publish portlet apps to Pluto.
>>
>>--
>>This message is automatically generated by JIRA.
>>-
>>If you think it was sent incorrectly contact one of the administrators:
>> http://issues.apache.org/jira/secure/Administrators.jspa
>>-
>>For more information on JIRA, see:
>> http://www.atlassian.com/software/jira
>>
>>
>
>
>
> --
> "I love deadlines. I like the whooshing sound they make as they fly
> by." -- Douglas Adams
>
Re: [jira] Created: (PLUTO-215) Create admin portlet for Pluto portal driver
Posted by Patrick Huber <st...@gmail.com>.
All,
in case I find time to do this, are there any constraints on the
technology to use? I've gotten pretty used to SpringPortlet in the
last months, during my student research project. On the other hand,
It's probably a quite small portlet and spring would be total
overkill...
Patrick
2006/2/17, ZHENG Zhong (JIRA) <ji...@apache.org>:
> Create admin portlet for Pluto portal driver
> --------------------------------------------
>
> Key: PLUTO-215
> URL: http://issues.apache.org/jira/browse/PLUTO-215
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.1.0
> Reporter: ZHENG Zhong
> Fix For: 1.1.0
>
>
> Create admin portlet for Pluto portal driver to make it easier to
> assemble/deploy/publish portlet apps to Pluto.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
[jira] Commented: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-215?page=comments#action_12455230 ]
David DeWolf commented on PLUTO-215:
------------------------------------
The scope of this portlet(s) should be:
1) Upload War
2) Reassemble War with the updated web.xml
3) Invoke App Server Specific Deployment Hooks
The container should take care of everything from here (auto plushing) and a unique portlet should be implemented (has been) for placing portlets on pages.
> Create admin portlet for Pluto portal driver
> --------------------------------------------
>
> Key: PLUTO-215
> URL: http://issues.apache.org/jira/browse/PLUTO-215
> Project: Pluto
> Issue Type: New Feature
> Components: portal driver
> Affects Versions: 1.1.0
> Reporter: ZHENG Zhong
> Assigned To: Craig Doremus
> Fix For: 1.1.0
>
>
> Create admin portlet for Pluto portal driver to make it easier to
> assemble/deploy/publish portlet apps to Pluto.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "Patrick Huber (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-215?page=comments#action_12367382 ]
Patrick Huber commented on PLUTO-215:
-------------------------------------
Please refer to the discussion on the mailing list: http://mail-archives.apache.org/mod_mbox/portals-pluto-dev/200602.mbox/%3c1876626704.1140197724492.JavaMail.jira@ajax.apache.org%3e
> Create admin portlet for Pluto portal driver
> --------------------------------------------
>
> Key: PLUTO-215
> URL: http://issues.apache.org/jira/browse/PLUTO-215
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.1.0
> Reporter: ZHENG Zhong
> Fix For: 1.1.0
>
> Create admin portlet for Pluto portal driver to make it easier to
> assemble/deploy/publish portlet apps to Pluto.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-215?page=all ]
Craig Doremus reassigned PLUTO-215:
-----------------------------------
Assignee: Craig Doremus
> Create admin portlet for Pluto portal driver
> --------------------------------------------
>
> Key: PLUTO-215
> URL: http://issues.apache.org/jira/browse/PLUTO-215
> Project: Pluto
> Issue Type: New Feature
> Components: portal driver
> Affects Versions: 1.1.0
> Reporter: ZHENG Zhong
> Assigned To: Craig Doremus
> Fix For: 1.1.0
>
>
> Create admin portlet for Pluto portal driver to make it easier to
> assemble/deploy/publish portlet apps to Pluto.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma closed PLUTO-215.
---------------------------
Resolution: Duplicate
Assignee: (was: Craig Doremus)
Duplicate of PLUTO-378
> Create admin portlet for Pluto portal driver
> --------------------------------------------
>
> Key: PLUTO-215
> URL: https://issues.apache.org/jira/browse/PLUTO-215
> Project: Pluto
> Issue Type: New Feature
> Components: portal driver
> Affects Versions: 1.1.0
> Reporter: ZHENG Zhong
>
> Create admin portlet for Pluto portal driver to make it easier to
> assemble/deploy/publish portlet apps to Pluto.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-215) Create admin portlet for Pluto portal
driver
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-215?page=all ]
David DeWolf updated PLUTO-215:
-------------------------------
Fix Version/s: 1.2.0
(was: 1.1.0)
IMHO, this should not hold up the 1.1.0 GA release. Moving to 1.2.0
> Create admin portlet for Pluto portal driver
> --------------------------------------------
>
> Key: PLUTO-215
> URL: http://issues.apache.org/jira/browse/PLUTO-215
> Project: Pluto
> Issue Type: New Feature
> Components: portal driver
> Affects Versions: 1.1.0
> Reporter: ZHENG Zhong
> Assigned To: Craig Doremus
> Fix For: 1.2.0
>
>
> Create admin portlet for Pluto portal driver to make it easier to
> assemble/deploy/publish portlet apps to Pluto.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira