> i) Should the tests run automatically every time the code is packaged? > - Maven tries to run tests when the 'mvn package' command > is given. Whilst this is a good thing to do (as it > highlights any errors that are present in that build), it > does add an extra minute to the build time. This doubles the > time it takes to run 'mvn package'. There are two choices of > what to do here: > 1) Make the tests run automatically, and if you want > to skip them, run 'mvn -Dmaven.test.skip=true package' > 2) Make the tests optional, to run them type 'mvn > -Dmaven.test.skip=false package' > ---
My vote would be to default to 1) and people have to indicate if they don't want them run. > > --- > ii) Some parts of DSpace are 'broken' right now. A good > example is DCDate. It has some issues, such as if the date is > the 1st Jan, then it assumes the granularity of the date is > ........... My preference would be > to commit the faulty test class, but to use a Test Driven > Development methodology for the re-development of DCDate to > ensure we get it right next time. > --- +1. In the case of DCDate its already widely known that it is broken. Having the test there will help in fixing it. Cheers, Robin.. -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
