gradle-extra-configurations-plugin
gradle-extra-configurations-plugin copied to clipboard
Gradle plugin introducing a provided dependency configuration and marking a dependency as optional.
The readme states: >The following publishing plugins support the correct handling when generating the relevant metadata: > > Maven Publishing > Ivy Publishing This is not really correct. It is...
It would be nice if you could also leave out the version for optional dependencies in the resulting POM. Leaving it out in the Gradle script might not work, as...
``` compile(group: 'org.springframework.cloud', name: 'spring-cloud-starter-zookeeper-discovery', version:'2.1.0.RELEASE',optional) { exclude(module: 'zookeeper') } ``` it's not work,too my maven code is ``` org.springframework.cloud spring-cloud-starter-zookeeper-discovery ${spring-cloud-zookeeper.version} true org.apache.zookeeper zookeeper ```
Can optional be used with the gradle kotlin DSL? If yes, please provide an example. Thanks.
When a project, one, declares a dependency as optional, another project that depends upon project one will pick up the optional dependency transitively. My exception is that an optional dependency...
Should this : ` compile project(':com.apgsga.qcel.dsl') , optional` work? Respectively can optional also be applied to project dependencies?
If a dependency is declared as `provided` and another configuration that is included in resulting artifacts (such as `compile` or `runtime`), it should not remove the dependency from the artifact.