Pluto 1.1 contains a utilities subproject which provides installation,
assembly, deployment, and publishing services. Here is a breakdown of each
1) Installation:
Installing the Pluto Portal to an app server. Currently Tomcat is
supported and jetty support is getting close. An M2 Mojo has also been
implemented to support this.
2) Assembly:
Injecting required elements into a portlet application to make it
deployable within pluto. This currently includes adding servlet
definitions. Assembly is currently working for all app servers and has
both an M2 Mojo which can be added to the plugins configuration of a pom
to automatically be done upon building of the war and an Ant Task which
can be used by portlet application projects not using maven.
3) Deployment:
Deployment (now that assembly and publishing are extracted out) is
simply deploying the war to the app server. Deployment is not yet
implemented (or, it was and is now not working due to changes to all of
the other utilities and mojos). I'm starting to think that we should
simply rely on existing app server mojos and ant tasks to handle this.
****What are others thoughts?****
4) Publishing:
Publishing is notifying the portal about the existence of a portlet
application. As of tonight, this is in place and has both M2 Mojos and
Ant tasks. The Portal must be up and running to accept new deployments
(unless the portlet is manually added to the pluto-portal-driver config
file - in which case it will be auto deployed upon startup.
Each of these utilities exists within the pluto-util subproject. Mojos
are in the maven-pluto-plugin and ant tasks are in pluto-ant-tasks
subproject.
At some point we will also need to add the ability to configure
placement of portlets on a page. Perhaps the only way we need to do
this is admin portlets.
I will be writing up documentation on all of this and hope that users
find these utilities easy to use and a big help. Please let me know if
you have any issues with them or suggestions on how to make them easier.
Thanks,
David
