On Wed, 26 Jul 2000, Jon Stevens wrote:
> Ok,
>
> This is a really good start, but what is in CVS isn't really what I was
> thinking of entirely.
>
> The issue is that there really should not be any .jar files in the TDK's
> CVS. The whole process should work more like this:
>
> cvs co turbine
> cvs co tdk
This is the type of process Dave and I have been talking about, but
the primary goal we decided on was ease of use. This is for people
not familiar with CVS, for people who haven't configured tomcat,
before, and for people who have never used Turbine.
What you outline is definitely how we'd like to build the TDK, but
I don't think each individual should have to do this in order to
get the TDK to work. I don't think it's critical that all the
jars are completely up to date. I think it should be dead simple
for someone to get an example turbine app up and running in a
few minutes. Downloading a big file (a zip, or tgz), extracting
it and having it work immediately.
People more adept at using dev tools can do the checkouts and
build the TDK themselves, but to attract as many people as
possible I think we should provide a self contained TDK
as a download that can be used all on it's own.
> cd tdk/build
> ./build-tdk.sh package-all
I totally agree.
>
> What would then happen is that the TDK would build itself by first trying to
> build Turbine and then copying all the necessary .jar files from Turbine
> into a distribution for itself (ie: tdk/tdk-1.0.tar.gz).
Yes, and this is what we would distribute somewhere.
>
> Of course you would leave the files like what is in tdk/bin and tdk/share/
> since that is specific to the TDK only.
>
> The point is that the TDK can use whatever version of Turbine you want and
> the TDK itself would be version controlled with specific versions of
> Turbine.
For adept developers there would be no limitations, but the TDK
we distribute as a self contained package would have fixed versions.
Once people are comfortable with the way things work, they can
move on to building the TDK themselves.
> I would go so far as even requiring that Tomcat/ServletAPI be checked out of
> CVS as well and simply building it and grabbing the servlet.jar and
> webserver.jar files.
Again, I think that's a bit much for a beginner. I'd like to package
up the whole shooting match. It might be big, but it will be
guaranteed to work because Dave and I will (and whoever else want
to help!) make sure that there is a functioning app that
is demonstrable.
I just want to show people that it works. Then when they
realize the obvious: that Turbine is the only way to go
they can do what they please with the TDK build.xml file.
Dave and I were even thinking about provide a big fat
WAR file that could be used as a precursor to the TDK.
For people who have a servlet container already, but
want to see Turbine in action. A total no-brainer,
something easy that will spark immediate interest.
They see that it works, then they take the time to
move on to the TDK, then eventually building the
TDK themselves. Easy, easy, easy is the goal.
jvz.
--
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
