> Martin: > docs are really important .. so having a document describing how to > organize a turbine app + a maven plugin > (we also could offer a build.xml for people preferring ant) sounds like > a good replacement for the tdk ... > i haven't looked at all usefull maven goals to produce a web-app .. > maybe we just need the torque plugin + a sample project.xml + maven.xml
...and... > Rodney: > I think a small sample application and a tutorial would be ideal. It sounds like we are thinking something like the following documents to replace the tdk. 1. A small introductory application 2. A tutorial on the creation of the said application 3. A walk through building said application with a maven plugin (to be written/contributed) 4. A walk through building said application with ant Is this correct? How do we go about doing this? Do we all agree on an application and a standard structure, then build it; or have somebody build something first, then rearrange it as a group until we are satisfied? Or is my question moot, and we already have a sufficient structure defined by previous work with the tdk? I guess the only outstanding pieces would be ant targets and the maven plugin (since it has yet to be written or contributed). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
