On Thu, Aug 07, 2014 at 12:38:33PM -0500, Tim Donohue wrote: > What you probably saw was Travis's normal Maven build process. Travis > always does the following in this order: > > [Task #1] mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V > (To install any missing dependencies into ~/.m2/ on the Travis server) > > [Task #2] travis_retry mvn clean package license:check > -Dmaven.test.skip=false > (To actually build & run tests..this step is prefixed by "travis_retry" > as it will attempt to run this step up to three times if it fails)
That makes sense. I should have looked at the build setup more closely. Thanks. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
