Gradle Plugins TODEPLETE: Difference between revisions
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
=External Plugins= | =External Plugins= | ||
If a build requires external plugins that need to be downloaded dynamically, [[build.gradle]] allows for a special | If a build requires external plugins that need to be downloaded dynamically, [[build.gradle]] allows for a special script block [[Gradle_Project_and_Build_Script#buildscript.7B.7D|buildscript{...}]] to declare where to download those plugins from. If the plugin is unknown, Gradle will fail with: | ||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
Plugin with id 'nebula.ospackage-application' not found. | Plugin with id 'nebula.ospackage-application' not found. | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 22:26, 19 May 2018
External
Internal
Overview
Most of Gradle's power comes from external plugins. A plugin is an extension to Gradle which configures the project it is applied to in some way, typically by adding plugin-specific dependency configurations, tasks and properties. Plugins can be applied to Projects because Project implements PluginAware.
Plugin Initialization
apply plugin:'java'
Plugin List
External Plugins
If a build requires external plugins that need to be downloaded dynamically, build.gradle allows for a special script block buildscript{...} to declare where to download those plugins from. If the plugin is unknown, Gradle will fail with:
Plugin with id 'nebula.ospackage-application' not found.