"Kevin A. Burton" wrote:
>
> Raphael Luta <[EMAIL PROTECTED]> writes:
> <snip>
>
> >
> > Doesn't run. There's no tomcat in the CVS. In any case, it's only
> > suitable for a generic introduction setup. Most people who will
> > want to use jetspeed will need to reinstall it with different
> > DBs, etc... and we ought to make this task as easy as possible.
>
> Yes... but this solves a number of problems:
>
> - - if you install Jetspeed... now you have a sample configuration which you can
> use to get your configuration working
>
> - - Allows us to skip messages from people who just want to setup jetspeed to see
> what it is like. It is not more like a product. IMO this should be the
> default packaging for 1.2
>
> - - Unit Testing... The Unit testing bases on the tomcat-build. Tomcat is used as
> the testing webserver.
>
> There is no Tomcat is CVS because this wouldn't be a good idea... if you need
> tomcat just pull it down from Jakarta...
> <snip>
>
I don't say tomcat-build serves no purpose, it is worthwhile to have something
that runs out of the CVS without worries (and that means putting Tomcat in
otherwise I don't see the point).
But tomcat-build is a not a replacement for a real Jetspeed WAR that can be
deployed in production servlet environments.
With the EngineContext rework and the refactoring of the Cocoon interface,
nearly all Jetspeed properties can now be expressed relative to the
current servlet context so that should not pose great difficulties to
distribute a WAR.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
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]
