 |
 |
Hi, Stuart. Answers below... > First, svn is replacing cvs as the version control system for hps-java Yes, the CVS should be considered frozen, though it is still technically writable. In fact, all projects in the CVS related to HPS have been migrated, not just hps-java. > requiring appropriate changes to be made to workflows for installing and updating installations of hps-java There are indeed changes which were covered in a series of messages to hps-software from myself. I will also cover this all in more detail at next week's software meeting. > with no change in the use of maven to build the code, correct? Maven is still used but the specifics are somewhat different. Again, see messages to the hps-software list. > Secondly, production code and user code, I'm slightly confused at what is meant by these terms > (putting a name to one example of each should be enough to clear that up) User code is personal analysis Drivers and the like or code that is not used in the mainline reconstruction. These packages usually have the user's name in the package in some form like org.hps.users.jeremym etc. This is an organizational convention only. These classes are now kept in the 'users' area in SVN which is the 'hps-users' Maven module. > but am I right in thinking the changes made in moving to svn makes it easier to keep these separate? Not exactly. I extracted these packages from hps-java and put them in another Maven module after the move to SVN, but it wasn't dependent on the new version control system. BTW, the archives of the hps-software mailing list are here: https://listserv.slac.stanford.edu/cgi-bin/wa?A0=HPS-SOFTWARE But I think you might need a SLAC account to see them (?). ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1