Using "ant deployPortletApp"
Portlets should be built using their native build mechanism (in the case of Jasig portlets, generally Maven). This build process should result in a .war file with a web.xml file that does not specify any Pluto-specific information or contain any Pluto jars.
The uPortal "ant deployPortletApp" task is designed to apply the appropriate modifications for the version of Pluto that uPortal 3.2 uses, then deploy the updated portlet war to the appropriate Tomcat location.
ant deployPortletApp -DportletApp=/path/to/my/portlet.war
If you'd like to make sure any existing matching portlet application is deleted before being redeployed, please set the value of "removeExisting" in uPortal's build.properties file to "false".
# Should the existing webapp be removed before deploying the new webapp removeExisting=false
You can also choose whether the ant task will extract the war file while copying it to the servlet container. To perform extraction, set "extractWars" in uPortal's build.properties file to "true".
# Should the deployment tools extract the WARs when copying them into the servlet container extractWars=true
Adding Portlets to uPortal's Portlet Overlays
Although portlets may be manually deployed via the ant command described above, adopters may also instead choose to add a portlet to the uPortal build to be automatically deployed each time the "ant deploy-ear" task is run. This method also allows adopters to use vanilla versions of portlets from a public maven repository, then create "overlays" for any files requiring customization. By following this strategy, adopters no longer need to maintain custom separate portlet projects.