[evla-sw-discuss] code organization

[Rich Moeser]

Bryan Butler wrote:
> in my opinion, the directory structure under the project (well, one layer deeper 
> - under the trunk/tag/branch directories) is up to the developer working on it. 
>   i don't think we benefit from alot of argument about it, since we're not 
> really in an environment where lots and lots of people are working on lots and 
> lots of different projects, so we don't need to be overly concerned about 
> conformity.  i'm assuming maven2 will be flexible enough to support different 
> layouts.
>   
I don't think leaving the directory structure - below the project - 
entirely up to the developer is a good idea. What we want to do is add 
structure to a project so that anyone in the group can go to an 
unfamiliar project and know roughly where things are located and how to 
build that project. We may not have many projects right now where 
multiple developers are working on the same code, but there are a few, 
and I would expect there will be several projects - like commons - where 
more than one developer will be adding/modifying code. IMO, if we have a 
predefined structure it will be more efficient for current and future 
developers to start work on the project if the structure is familiar. 
Also, if the project does not have structure it will be difficult to do 
an all-project build.

--Rich