Are you using eclipse? ctrl + shift + R is great (use * as wildcard) Or you can use this plugin http://code.google.com/p/loom-t5/ Otherwise you can bundle your source anyhow you like, as long as your build makes the war correctly at the end of the day. The maven folder structure is only a (good, tried and trusted) recommendation.
On 19/06/2008, Geoff Callender <[EMAIL PROTECTED]> wrote: > > Perhaps I've lost my mind, but I'm struggling to find a good reason why we > keep our templates and properties separate from our java source. I find it > causes nothing but pain having to incessantly jump between these > disconnected parts of the source tree. Is it purely to appease some Maven > convention? > > What makes it even stranger is that the java classes end up together with > the templates and properties anyway - my build process puts classes, > templates and properties all together in WEB-INF/classes/ regardless of > where they come from. Live class reloading loves it that way and it keeps > them secure from prying hackers. > > So why not mix the source together into the following structure > > src/ > main/ > java/ <-- or perhaps some other name like "t5/" > myproject/ > base/ > components/ > css/ > images/ > META-INF/ > mixins/ > pages/ > services/ > WEB-INF/ > > and let the build coax it into the WAR file correctly? > > Cheers, > > Geoff > >
