portals-pluto-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David DeWolf (JIRA)" <pluto-...@jakarta.apache.org>
Subject [jira] Commented: (PLUTO-72) Deployment in Release Candidate should not need Maven
Date Mon, 25 Oct 2004 13:45:44 GMT
     [ http://issues.apache.org/jira/browse/PLUTO-72?page=comments#action_54591 ]
David DeWolf commented on PLUTO-72:

After a quick review, I think this is definately a step in the right direction and it should
be considered for inclusion.  The one suggestion I think I'd make before it gets committed
is that it is updated to download it's dependencies before so that they don't have to be distributed
with pluto.  This should be a relatively easy update and if no one beats me to it, I hope
to get it done before 1.0.1 SP2 is released.

> Deployment in Release Candidate should not need Maven
> -----------------------------------------------------
>          Key: PLUTO-72
>          URL: http://issues.apache.org/jira/browse/PLUTO-72
>      Project: Pluto
>         Type: Bug
>   Components: portlet container
>  Environment: All environments
>     Reporter: Craig Doremus
>  Attachments: portlet-deploy.zip
> Deployment of portlets in the Release Candidate should not require Maven. Instead, a
separate 'deploy' directory should include:
> 1. An Ant build file to deploy individual portlets
> 2. A Unix shell script and a Windows batch file to deploy portlets. These scripts would
invoke the Deploy class and take the path to the portlet war file as an argument.
> 3. A separate directory (deploy/lib) that contains jars necessary for the function of
the Deploy class.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message