[evla-sw-discuss] code organization

[Bryan Butler]

so i had a look at this.  boy, their documentation leaves a bit to be desired 
(maybe i'm supposed to know this, but what the hell is supposed to go in 
src/site?  and what is the difference between sources and resources?).

pretty java-centric.  maybe that's OK.

it'll need a src/main/c and src/main/python and maybe others (src/main/FORTRAN 
for CALC???) i guess.

where do we put documentation (which is not javadoc)?  for instance, with the 
PST, we have raw LaTeX (plus .sty file), some image files, a Perl script (so sue 
me), and some config files, which all need to reside in the same place.  do we 
make a src/main/doc directory?  and does the result of running the script need 
to go in a directory under target (target/doc or somesuch)?

is this the time we try to go with a trunk and branch development (we could call 
them "stable" and "devel"; or "stable" and "test"; or "old" and "test"; or 
whatever, but the subversion recommendation is to use trunk, branch, and tags)? 
  if so, i assume we do that for each project separately, so we have
  .../pst/trunk/...
  .../pst/branch/...
  .../pst/tags/...
  .../opt/trunk/...
  .../opt/branch/...
  .../opt/tags/...
???

and, just to open this can of worms, will we attempt to convert over all of our 
old cvs stuff to subversion, or will we just copy over the most recent version 
and start fresh?  i'd really like to retain the old revision information, but it 
might make it painful, i don't know.  at the very least we should keep the old 
cvs in place so we can track the older revisions.

	-bryan


On 10/25/06 13:28, Rich Moeser wrote:
> If we are sticking with Maven - I see no reason not to - then I suggest 
> we follow their recommended directory layout which is described at 
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html. 
> It's slightly different than what the Maven folks recommended in Maven 1.x.
> 
> --Rich
> 
> 
> Stephan Witz wrote:
>> This is to kick off discussions about the organization of our software,
>> by which I mean the layout of the repository and the build mechanism:
>> we've been talking about moving from maven 1.0 to 2.something, and from
>> cvs to subversion, and if we do such a thing, now is the best time to
>> address the current directory structure of our projects: what the layout
>> of the repository is and where each chunk of what we have will go.
>>
>> You have opinions, share them. We have a couple of weeks to make noise
>> at each other before the new repository is setup and ready for us to start
>> porting things over to it. Once we start that process I really don't want
>> to have to backtrack and rework the layout.
>>
>> _______________________________________________
>> evla-sw-discuss mailing list
>> evla-sw-discuss at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
>>   
> 
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss