[PLUTO-24] Update Deploy class maven goals to allow more general deployment

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: unspecified
• Fix Version/s: 1.0.1-rc2
• Component/s: deployer
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 27001
• Assignee: Unassigned
• Reporter: Michael Westbay
• Created: 17/Feb/04 17:57
• Updated: 22/Feb/07 04:58
• Resolved: 24/Nov/04 05:19

Description

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.