[evla-sw-discuss] Delay models to station boards

[David Harland]

Rich Moeser wrote:
> The schema files for WIDAR are available at 
> https://svn.aoc.nrao.edu/repos/WIDAR/schema so I don't think it's 
> necessary to copy those to the EVLA SVN repository. I've set up a 
> prototype maven project that takes the schemata from the WIDAR SVN 
> repository, runs it through the JAXB compiler, and bundles the resulting 
> JAXB classes into a standalone jar file. This is pretty much the same 
> approach I have taken with the ALMA SDM schemata and it works just fine.
>   

Great -- having these classes packaged into their own jar, without 
reliance on any other classes, is the way to go here. Nice to see it's 
already set up!

Kevin Ryan wrote:
> WIDAR's schema is located at https:// 
> svn.aoc.nrao.edu/repos/widar/trunk/schema/.  (don't ask me why the  
> 'trunk' is in there).

The "trunk" is part of the subversion convention of using

myProject/
trunk/
branches/
tags/

The main development thread is under "trunk" and is all most of us deal 
w/ on a regular basis. Branching is often used when one has some serious 
rearranging of code to do (though when to branch tends to become a 
religious war). Making a branch lets one do all this destruction w/out 
getting in the way of other people who are updating the main trunk. Tags 
are useful for taking a collection of particular revisions of source 
files and saying "together these comprise release 1.2.3". Surf the web 
or talk to Brian Truitt if you want to know more about this (because i 
just told you all i know!).

For these VCI classes i doubt we'll use branches. Once we're past 
initial development, though, it's possible that we might want to make a 
new tag (think "release" or "version") each time the schema files are 
updated.