On Dec 27, 2008, at 11:00 AM, Les Hazlewood wrote:
How do you see the directories, i.e. code, resources, etc.?
After working with wicket source trees in my own project trees, I've
become
keen on keeping things co-located based on pacakge.
I like to co-locate based on functionality. Following that paradigm
the packages happen to cluster similarly.
My personal preference
is to have a src and a test directory directly under the module
directory
with code and resources co-located side-by-side for easy access/
lookup. I
noticed this greatly simplified my build scripts too.
Maven work with this setup. Thinking ahead, if any resources need to
be pre-processed, e.g. macro processing, things could get messy on
both Maven and Ant. If we placed the resources in a separate resource
directory per Maven convention we wouldn't need those messy bits.
Just something to think about.
so, for example, we would have
trunk/
|--build.xml
|--pom.xml
|--build.gradle
|--core/
| |--src/
| |--test/
|--web/
| |--src/
| |--test/
|--support/
| |--spring/
| | |--src/
| | |--test/
| |--ehcache/
| | |--src/
| | |--test/
etc...
Is this copacetic? If it is, and we were to have a maven build in
addition
to the regular build, could maven handle this directory structure?
Seems ok to me. Maven can handle it but I have to add some POM
"noise" to get it to work. I'm willing to compromise here so long as
no one points ad those bits and says "yuck".
Regards,
Alan
