Hmm, after examining what it generates, it seems wrap your portlet in a pluto servlet...
Antony Stubbs wrote: > > Yes I would also like to know what it does, and why it is necessary to use > - should we not simple be able to deploy simple wars that are portal > compatible? can't pluto detect their existence? > > I have found this, but it doesn't really answer my question - from the > AssembleMojo javadoc: > * The AssembleMojo is responsible for assembling a web application for > deployment > * into the Pluto portlet container. Assembly, in this context, is the > process of > * updating a web application's WEB-INF/web.xml with Pluto specific > parameters for > * deployment in Pluto. > * <p> > * This Mojo is able to operate on individual descriptors by specifying > * <code>portletXml</code>, <code>webXml</code>, and > <code>webXmlDestination</code>. > * If your project uses standard Maven 2 directory layouts, the defaults > will > * provide proper values. > * <p/> > * Example Maven 2 <code>pom.xml</code> usage: > > > chadmichael wrote: >> >> I'm using pluto 1.0.1. >> >> I'm just trying to learn portlets. What exactly does the maven >> portlet deployment do? I'm talking about the one in the source code >> distribution, deploy directory. I'm using it to deploy my portlet >> applications, as per the pluto site docs, and it works, but I want to >> know what it does? >> >> > > ----- ___________________________ http://stubbisms.wordpress.com http://stubbisms.wordpress.com -- View this message in context: http://www.nabble.com/maven-portlet-deployment-tp4435947p19960433.html Sent from the Pluto - User mailing list archive at Nabble.com.
