I've had thoughts along the same lines. In general, it's much easier to delete stuff than to add it correctly. Plus, if most people are going to want the majority of the extras, it ends up being a win-win situation. I think it would be a good idea to include a little of everything in the archetype and just let people remove the bits they don't want.
On 6/16/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Had a really cool time doing the Tapestry 5 spiel in Denver and Boulder this week. Sure it cost me about $2000 in lost billable time, but that's just how I roll. Scott Davis had some very good ideas; he's a big proponent of Grails, and he thinks the key is to offer a full stack; i.e., the archetype includes some basic Hibernate entities, plus some scaffolding for those entities, and Maven machinerty to start it all up and run Derby or HSQLDB. So, really, it would be nice if we had even more Trails like behavior as part of the quickstart archetype, right from the get-go. I'm beginning to learn towards the idea that quickstart should evolve to be the "maximal" Tapestry template (and perhaps we add a "minimal" archetype for bare-bones). Thoughts? -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Daniel Gredler http://daniel.gredler.net/
