gistfile1.md

I have purposely forced an error building documentation by deleting the config file.

Running:

xavier@xavier ~/www/download.jqueryui.com/tmp/api.jqueryui.com $ grunt build-xml-entries

We get the full error:

>> TaskError: Unable to read "config.json" file (Error code: ENOENT).
>> No "build-xml-entries" targets found.
<WARN> Task "build-xml-entries" failed. Use --force to continue. </WARN>

Running:

xavier@xavier /userdata/Documents/www/download.jqueryui.com $ grunt prepare

We get:

>> Error building documentation: path.existsSync is now called `fs.existsSync`.
<WARN> Task "prepare" failed. Use --force to continue. </WARN>

Aborted due to warnings.

Note that the above Error building documentation is generated by the following js code:

grunt.log.error( errorMsg + ": " + error.stderr )

It means the below is being outputed to stdin.

>> TaskError: Unable to read "config.json" file (Error code: ENOENT).
>> No "build-xml-entries" targets found.
<WARN> Task "build-xml-entries" failed. Use --force to continue. </WARN>

Which means, our grunt error logging function is correct. What we need to fix is how the above is being outputed.