"Quinton McCombs" <[EMAIL PROTECTED]> writes:
>Granted, I was using the TDK in 2.1. When I moved to 2.2, I stopped
>using the TDK. That could have had a great deal to do with my problems
>concerning the TDK.
I think, most of us did this. The 2.1 TDK simply didn't work with T2.2
I've never looked into the current TDK. I consider it a huge achievement
that Martin was able to get a 2.2 TDK running.
>I would rather see one or two sample apps that are ready to be built
>with Maven replace the TDK. One should use JSP. The other should use
>Velocity. I think this would be much more helpful to new users.
Please read what I proposed. Basically a new TDK would be
- preconfigured servlet container
- (maybe) preconfigured, simple database e.g. hsqldb
- preconfigured build tools (maven, maybe ant)
- some ant/maven tasks to copy an application into the servlet
container for testing (tdk:install, tdk:clean, tdk:deploy)
- a small skeleton to set up a build environment outside
the webapps directory (!). Small means, my current skeleton
has 25 kBytes and consists mainly of TR.props, Log4j.props
and a little ant script to create the directory structure.
- demo apps
- documentation
Well, you might not need it and I might not need it, but getting all
the parts together for testing and debugging a turbine app can be
quite cumbersome and most of us learned how to do this by using the
TDK.
BTW: Internally I use "META" for this "new tdk":
"Maven Environment for Turbine Applications" :-)
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
