CB-6481 adds plugin level hooks support

[sgrebnov]

1.Support of js hook files (nodejs is used to run script file)

2.Support of the following hook types

• beforeinstall/preinstall – run before plugin is installed
• install/postinstall/afterinstall – run after plugin is installed
• uninstall – run after plugin is uninstalled

<script type="postinstall" src="scripts/postinstall.js" />
<script type="preinstall" src="scripts/preinstall.js" />
<script type="install" src="scripts/install.js" />

3.Use context argument to retrieve execution parameters inside hook function

module.exports = function(context) {
    console.log('hook.js>> platform: ' + context.platform);
    console.log('hook.js>> projectDir: ' + context.projectDir);
    console.log('hook.js>> pluginDir: ' + context.pluginDir);
    console.log('hook.js>> cmdLine: ' + context.cmdLine);

    var deferral = new Q.defer();

    setTimeout(function(){
        deferral.resolve();
    }, 1000);

    return deferral.promise;
}

[ligaz]

You can use scripts.slice(0) here.

[sgrebnov]

Thx, updated

[mmocny]

Did a quick pass and ran some tests locally. I haven't reviewed the patch thoroughly, yet. Notes:

• Using Q works for me for all the install hooks, but not for the uninstall hook.. odd! Its also odd that Q is used without requireing it, since if you try to require it you get module not found.
• Why do we support both pre_/post_ and before_/after_ versions?
• Why don't we support before/after for uninstall?
• Why have an "install" hook that is == afterinstall?!
• To be consistent with the CLI hooks, I suggest: before_plugin_install, after_plugin_install, before_plugin_uninstall, after_plugin_uninstall
• I cannot require('cordova'). Not sure exactly how to approach this problem, but I would like to at least be able to run cordova commands from these hooks, like the node equivalent of cordova plugin ls.
• Why are we specifying hooks in plugin.xml instead of using a hooks/ folder? This seems quite opposite of the CLI, and I'm not sure why. If you want hooks to run only for a specific platform, you can use the provided context to early exit, instead of using <platform> tags.

Finally, I'd love to see plugin hooks share a common module with CLI application hooks. Right now the CLI hooks look rather tightly coupled with the CLI application structure, but we could break that up to have common modules for:

• mapping a hook by-name to a set of node scripts to run
• running hooks, passing an appropriate context, preferences, and environment setup

[sgrebnov]

New plugin hooks implementation is coming...closing this one