Although I agree with you that the basic template is not hugely useful beyond a demo, I think that is intentional.
Simply typing grails install-templates and then customizing them (as per your rules below) would seem to suffice. I do that on all non-trivial Grails projects I implement.
Making the current template simpler I would agree with, making it more complex I would shy away from.
Richard
On Fri, Jul 3, 2009 at 4:22 AM, mumek2008
<marko.umek@...> wrote:
I'm currently a little bit unhappy with the code generation support for example grails create-domain-class.
For a simple project the current code generation is sufficent, but for more real world projects which will be organized in plugins, the current code generation is not nice.
I need copyright, User name a.s.o. on level grails project/plugin. Some of the projects will be open source, others closed source or different customers. So currently there is a lot of DRY-violation.
--
---
Richard Vowles,
Talk to me about development in Grails, Groovy, Java and for the Blackberry
ph: +64275467747, linkedin, skype:rvowles
get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! -
http://tinyurl.com/cmcceh
podcast:
http://www.illegalargument.com
