> * kill the tdk .. we allready have a maven-plugin for torque .. i think > it would be better to write a turbine-plugin and kill the tdk
I volunteered earlier to write to Sans-TDK howto for turbine, but have been holding off until Scott's Wiki idea coalesces. By the way, what is the status of the Wiki? And do people agree that such a document alone would be sufficient to leave the TDK behind? I like the maven plugin idea, and would use it personally, but I am concerned that coupling Turbine with maven would lead to the same problems that having a TDK has caused, that is, confusion and complexity, just with different command line options than we currently have. I feel it is important that Turbine have a document describing how to organize a Turbine application with nothing but a compiler, and maybe ant if they choose. I am thinking "baby steps" up to a complete application. I would expect this document to be the road guide for a new user's first application. And then provide the optional maven plugin for people who find it attractive, the idea of having a strictly defined project structure with maven. Thanks for listening, Chris -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
