[evla-sw-discuss] code organization

[Bryan Butler]

i don't think we intend to *enforce* building with maven2 (at least that was 
never the way i was thinking about it).

keeping things in subversion (if we all agree that the change from cvs to 
subversion is OK) *will* be enforced.

	-bryan


On 10/25/06 17:12, Martin Pokorny wrote:
> On Wed, 2006-10-25 at 15:21 -0600, Bryan Butler wrote:
>> so i had a look at this.  boy, their documentation leaves a bit to be desired 
>> ...
>> pretty java-centric.  maybe that's OK.
> 
> I'd like to stick with my autotools stuff for building the CBE code.
> What I've seen of maven so far doesn't make me optimistic about having
> it do the "configure && make" two-step that's required to build my code.
> Oh well, maybe there are some peripheral benefits to using maven with C
> code.
> 
> The high-level organization of the repository should be orthogonal to
> the project management and/or build tools we use for the various
> projects in the repository. Project/build tools have their own
> requirements, and it's probably safest to bury those at lower levels
> within a project. Whether it's desirable to put java, C, perl or
> whatever into their own subdirectories depends on the project and tools
> used by that project. In the CBE case, I don't need that sort of
> distinction (that "c" subdirectory in the current CVS tree is pointless
> for the CBE), while other subdirectories do make some sense.
>