[evla-sw-discuss] code organization

[Brian Truitt]

My main concern is not what other people think of our repository layout 
or how easy it is for some random stranger to find something in it. If 
they want to find something in particular, they can use a *search 
engine*. That's why we have them.

What I want is something that will make my job easier. That's my 
concern. If I use maven's default directory layout, my job is easier. I 
put stuff where they tell me to put it, type mvn package, and boom, I 
have a web application. Done and done.

Certainly maven is flexible enough to adapt to other directory 
structures, but I want to spend my time writing code, not configuring a 
build environment. If I have to change the maven configuration, my job 
is harder again, and moreover, the job of anyone taking up the reins on 
my project later is also harder because I've strayed from the standard 
and now they have to learn and maintain an odd build environment.

There are advantages to avoiding the overly generic and verbose maven 
directory structure, but there are also advantages to not worrying about 
it and just getting *work* done.

Brian