Gradle Plugins TODEPLETE: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* [[Gradle_Maven_Plugin#Overview|Maven Plugin]] | * [[Gradle_Maven_Plugin#Overview|Maven Plugin]] | ||
* [[Gradle_Maven_Publish_Plugin#Overview|Maven Publish Plugin]] | * [[Gradle_Maven_Publish_Plugin#Overview|Maven Publish Plugin]] | ||
=External Plugins= | |||
If a build requires external plugins that need to be downloaded dynamically, [[build.gradle]] allows for a special DSL element ([[build.gradle#buildscript|buildscript]]) to declare where to download those plugins from. If the plugin is unknown, Gradle will fail with: | |||
<syntaxhighlight lang='bash'> | |||
Plugin with id 'nebula.ospackage-application' not found. | |||
</syntaxhighlight> | |||
Revision as of 22:24, 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 DSL element (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.