 |
 |
Hi, A general note to all developers of the Java software..... If you are making changes to the trunk that involve modifications to code in the mainline reconstruction or their steering files, or any other important component of the Java software, please test those changes before committing them to the SVN trunk. This basically means that you should run all the tests once before checking things in which is as simple as.... cd trunk; mvn It does not take that long and it will perform a lot of sanity checks. This makes sure basic things like the reconstruction and the clustering are not broken by your changes. It won't necessarily test your specific code changes but it does make sure things are not globally broken. If you are putting in new steering files then you should run them through (probably) EvioToLcio to make sure they work. At a bare minimum, please make sure the JobManager can at least initialize your steering file. This is a minimal amount of testing which should ensure that changes do not break basic functionality in HPS Java. Preferably, new classes should have a corresponding TestCase that goes along with them and is run with the build, but I understand there is not always time to code this up. Also, if there is some large(ish) project you want to work on that involves many changes to the code, then you should branch the entire HPS Java trunk where you can feel free to break everything to your hearts content. Then you would just need to make sure everything is working when merging back in at some future date. If you need tips/instructions on branching and merging in SVN, then please let me know. Thanks. --Jeremy ######################################################################## 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