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 <[EMAIL PROTECTED]> 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/
