Enhancement: adds user defined resource folder that is copied to public

[soapdog]

This enhancement adds a user defined resources folder that is copied to public during build. This folder is copied after the theme's resources are copied so it can be used to overlay items as well.

If there is no resources folder present then Harmonic displays a warning saying that no user resources were copied during build. This happens if the folder is not present or if there was an error in the copying process. Node documentations says that fs.exists and fs.existsSync will be deprecated and I didn't want to use functions that will soon go away thus generating debug work for my future self.

This was implemented by splitting the copyResources() function into two functions called copyThemeResources and copyUserResources as mentioned in #138 (which is solved by this PR).

Hope your folks like it, it makes things a lot easier for me at least.

[UltCombo]

Excellent work!

Node documentations says that fs.exists and fs.existsSync will be deprecated

I believe those are already deprecated in io.js.

Note to self:

• Promisify ncp using Bluebird;
• Remove fs.exists/fs.existsSync usage from Harmonic - #142

[jaydson]

[jaydson]

Let's release on npm this feature @UltCombo ?

[UltCombo]

@jaydson yep, sure. Go ahead with the Harmonic release while I work with @robsongajunior to release the new JS Rocks build. =]

[jaydson]

Ok!

[jaydson]

Released as v0.3.0

[UltCombo]

Nice!

Now I wonder if it wouldn't be better to place the resources directory inside the src dir. I guess it doesn't matter much either way.