lint/test errors shouldn't always abort the build

[joemfb]

At the very least, there needs to be an options to continue anyway. Run into this doing deployments an deadline; always fun to be forced to fix unit tests at the last minute ...

[grtjn]

I vote for a --novet, that effectively skips the jshint and jscs validation in the vet task, or make it continue without abort.

You can also disable things manually, but then it is permanent. The minimum to get past js syntax issues without aborting is commenting out the last two lines of the vet task:

gulp.task('vet', function() {
  log('Analyzing source with JSHint and JSCS');

  return gulp
    .src(config.alljs)
    .pipe($.if(args.verbose, $.print()))
    .pipe($.jshint())
    .pipe($.jshint.reporter('jshint-stylish', {verbose: true}))
//    .pipe($.jshint.reporter('fail'))
//    .pipe($.jscs())
  ;
});

[grtjn]

Or maybe gulp build should not vet, unless --vet was provided? (any votes?)

[grtjn]

I added an --ignoreErrors feature as part of #305..

[joemfb]

Great, that works for me!