I am cautiously eyeing the “Publication and consumption of plugins to and from custom repositories” from Gradle 2.14 release notes, yet before I start kicking the tires, I would like to ask:
- the 2.14 release notes mention that the
gradle-pluginautomatically adds the plugin marker artifact is to
ivy/maven-publishtasks. How about
- Can we apply the new plugin repo config from init script? Which hook shall we use? Do you have example by any chance?
- Is there still a restriction that we can not use
- I know that the
pluginssection supports a restricted subset of the Groovy syntax - does it allow to use project properties to define plugin versions?
- What would be the programmatic way to apply plugins resolved by the new mechanism? I.e. if I want to apply a plugin from another plugin.
Even if some of these are not supported yet, I am interested with their relative priority in the roadmap.