On Wed, 4 Dec 2002 05:14, you wrote: > 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?
Yeah, that would be awesome! > 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? I think it would be best if someone would volunteer to develop a sample application first. Something small and simple (like the Velocity forum demo) that exercises as much of the Turbine API as possible. > Or is my question moot, and we already have a sufficient structure > defined by previous work with the tdk? There are 2 main application layouts that Turbine developers tend to use: 1. The TDK "classic" layout which stores everything inside the webapp directory. 2. A "CVS" layout similar to Scarab's layout. I am not sure which one is the preferred layout for the sample application. Any thoughts? > I guess the only outstanding pieces would be ant targets and the > maven plugin (since it has yet to be written or contributed). Most of the ant targets can be taken from the TDK build files. Regards, -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
