Applying Plugins
The ways a plugin gets applied: the declarative plugins block, version resolution, apply false, marker artifacts, and the legacy imperative form. Interviewers ask because a misapplied plugin is the first thing that breaks a build script.
on this pageshowhide
explore
- plugins {} DSL Block6 questions
- Plugin Version Resolution5 questions
- apply false in Multi-Project Builds5 questions
- Plugin ID vs Marker Artifact5 questions
- Legacy apply() and apply(from=)5 questions
- Reacting to Applied Plugins5 questions
questions
page 2 of 2Your org mirrors plugins through an internal repository instead of the public Plugin Portal. What has to be true about markers and pluginManagement for `id("…")` resolution to keep working, and what breaks if you only mirror implementation jars?
level: principalimportance: nice to knowfreq 18%
basics
~20 sThe internal repo must serve the marker POMs (<id>:<id>.gradle.plugin) as well as the implementation jars, and pluginManagement.repositories must point at it. If you mirror only the implementation jars, id(...) resolution fails because Gradle can't find the marker to translate the id into a coordinate.
showing 31–31 of 31