-----------------------------------------------------------------
Jeffrey D. Brekke Information Systems
[EMAIL PROTECTED] Quad/Graphics
http://www.qg.com 555 South 108th Street
414-566-3302 West Allis, WI 53214-1145 USA
-----------------------------------------------------------------
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 1:43 PM
> To: JetSpeed
> Subject: [1.3a1][vote] packaging options to keep
>
>
> Now that we fully support the WAR format we need to decide
> how many packaging options we are planning to support.
>
> Currently, you can say with have 3 options available :
> - the webapp package
> - the tomcat-build package
> - the src/content and associated files
>
> 3 is too much. Because supporting correctly these 3 packages
> require 3 different installation docs, test process, etc...
>
> * Should we remove the tomcat-build system ?
>
> [ I'm +1. I think that the webapp makes the tomcat-build obsolete ]
+1 No longer needed.
> * Should we remove the content and assimilated directories in src ?
>
> [ I'm +0. We could keep these directories for more advanced
> configuration options that those bundled in the webapp at
> the risk that
> the 2 confs are not kept in synch. ]
+1, KISS.
> * Does anybody have an idea how to package "add-ons" for the webapp ?
> For example, portlets not activated by default, etc...
It would be nice to have a Jetspeed Developers Kit, much like the TDK that
would take the latest jetspeed webapp, and set it up for developers to
extend and add their stuff to. Maybe this would be a special version of the
TDK, set up to generate a default 'jetspeed portal app' ready for
customization. Just a random thought.
I've been trying to figure out how to incorporate the new jetspeed webapp
into our system and still allow the 'base jetspeed' stuff to be upgradeable
in the future. Since any specialization would change .properties files and
stuff, updating to the next version of Jetspeed/Turbine becomes quite the
chore. This of course just maybe the side effect of the current rate of
change in these projects ( Turbine/Jetspeed ).
------------------------------------------------------------------------
This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
