RetireJS/grunt-retire

retire stops default tasks even if successful

mengstr opened this issue · 0 comments

Ignoring the risk of making a fool of myself once more I'll just boldly submit another bug report. :)

If the retire task is not the last task in the "default" registerTask list the entries after it is not run even if the retire task is successful. If I run grunt on this projects Gruntfile the output is as follows:

MatsMac:grunt-retire matseng$ grunt
Running "jshint:all" (jshint) task
>> 2 files lint free.

Running "retire:node" (retire) task
Ignoring []
Loading from cache: https://raw.github.com/bekk/retire.js/master/repository/npmrepository.json
Reading /var/folders/1h/5gtkqglj7b7dj_f6cxjpzvl40000gn/T/.retire-cache/1399562008463.json ...
MatsMac:grunt-retire matseng$ 

Switching the order of default tasks

 grunt.registerTask('default', ['retire', 'jshint']);

Gives the following output

MatsMac:grunt-retire matseng$ grunt
Running "retire:node" (retire) task
Ignoring []
Loading from cache: https://raw.github.com/bekk/retire.js/master/repository/npmrepository.json
Reading /var/folders/1h/5gtkqglj7b7dj_f6cxjpzvl40000gn/T/.retire-cache/1399562008463.json ...
MatsMac:grunt-retire matseng$ 

Did I fsck something up again?