In the .travis.yml file, why is a mvn clean install (line 42 of the latest commit on master)
followed by an mvn package (line 47) given that the mvn install will ALSO package the project(s)? (i.e. install seems to be a superset of package in maven terms) On Monday, June 6, 2016 at 6:56:35 PM UTC+3, Pantelis Karamolegkos wrote: > > Assuming someone wants to fork and proceed with heavy DSpace > customization, what is the recommended testing strategy? > i.e. which of the tests should be kept in a CI environment like travis? > (apart from our own custom tests we may set up) > (note: 99% of the customization will most likely take place on jspui) > Is there any documentation on dspace's (Unit/Integration) tests? > > Thx, > > P.K. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
