From 3379eebe4bca22316327b7f1ca92c2240b29187c Mon Sep 17 00:00:00 2001
From: Vojta Jina
Date: Wed, 28 Aug 2013 17:48:46 -0700
Subject: chore(travis): run bower install twice to make sure it does

This is a work-around for Bower/Node.js issue (https://github.com/bower/bower/issues/830). We run `bower install` twice, as the probability of failing twice in a row is very low.

I had to extract `bower` task out of the package, because we need to run `bower install` before building and `grunt bower` can fail, which takes down the whole process and therefore it wouldn't build.
---
 Gruntfile.js | 1 +
 1 file changed, 1 insertion(+)

(limited to 'Gruntfile.js')

diff --git a/Gruntfile.js b/Gruntfile.js
index 8fbf84b0..40ffbd4e 100644
--- a/Gruntfile.js
+++ b/Gruntfile.js
@@ -261,6 +261,7 @@ module.exports = function(grunt) {
   grunt.registerTask('minify', ['bower','clean', 'build', 'minall']);
   grunt.registerTask('webserver', ['connect:devserver']);
   grunt.registerTask('package', ['bower','clean', 'buildall', 'minall', 'collect-errors', 'docs', 'copy', 'write', 'compress']);
+  grunt.registerTask('package-without-bower', ['clean', 'buildall', 'minall', 'collect-errors', 'docs', 'copy', 'write', 'compress']);
   grunt.registerTask('ci-checks', ['ddescribe-iit', 'merge-conflict']);
   grunt.registerTask('default', ['package']);
 };
-- 
cgit v1.2.3