Friday, September 10, 2010

packages in grails

Convention over configuration rewards you for sticking to the typical convention. I don't feel rewarded for package-ify-ing artefacts when using the grails command line. Maybe deeply nested packages based on domain names, products, tiers, technology... blah blah blah is a foolish consistency held over from pure java development. If you are not developing infrastructure or a code base for sharing outside of the application does it really matter?