DO NOT REPLY [Bug 27001] New: - Update Deploy class maven goals to allow more general deployment

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27001>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27001

Update Deploy class maven goals to allow more general deployment

           Summary: Update Deploy class maven goals to allow more general
                    deployment
           Product: Pluto
           Version: Current CVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: general
        AssignedTo: pluto-dev@jakarta.apache.org
        ReportedBy: westbay@users.sourceforge.net


When creating a portlet, it would be nice if the portlet creator could extend
the current build and deploy goals.  This is currently possible, however, the
project must be located in a directory directly under the jakarta-pluto root
directory due to a hard coded path in
portal/src/java/org/apache/pluto/portalImpl/Deploy.java.

I propose modifying Deploy.java so that the fourth parameter (arg[3]), which is
currently not being used, be set to the $PLUTO_HOME directory (i.e. the
jakarta-pluto directory).  I am including said patch below, along with patches
to maven.xml under $PLUTO_HOME/testsuite and $PLUTO_HOME/deploy.

Also, please note that $PLUTO_HOME/deploy/maven.xml also synchronizes the
${maven.tomcat.home} property for the first parameter, declared in
build.properties.sample, and used in $PLUTO_HOME/portal/maven.xml and
$PLUTO_HOME/testsuite/maven.xml.  I'm assuming that it being called
${tomcat.home.pluto} here is a bug.