4.7.7 Plugin Install Failure Strategies

Failures may occur during plugin installation. It may be the case that a plugin could not be found in the configured repositories, or a JAR dependency failed to be resolved. When this happens the build will try its best cope with the error, usually by continuing installing remainder plugin dependencies (if any).

This behavior can be altered by specifying a value for `griffon.install.failure`. Accepted values are:

Value | Description
--- | ---
abort | Aborts the installation sequence, even if there are other plugins left to be installed. It will also delete all installed plugins in the current session.
continue | Continues with the next plugin in the list. this is the default behavior.
retry | Retries failed plugins a second time. A second failure skips the plugin from being installed but does not affect any other plugins that have been successfully installed or are yet to be installed.

For example, to return the build to its previous behavior (abort on failures) you'll type the following in your command prompt

    griffon -Dgriffon.install.failure='abort' compile