Hi, after the addition of compileOnly configuration into Gradle I would expect that MavenPublication publishing type would respect compileOnly configuration and generate proper Maven provided scope in the generated pom file. This is however not working in Gradle 4.0-rc-1. Can you verify/add it to…

Publishing plugin should respect compileOnly configuration

st_oehme (Stefan Oehme) June 8, 2017, 2:49pm 2

compileOnly dependencies are only for compilation. They must never leak into clients, so there would be no point putting them into a published POM (no matter which scope).

Topic		Replies	Views
Compile dependencies published to maven as runtime scope Bugs plugins , not-a-bug	0	1843	August 3, 2016
Maven-publish scopes runtime dependencies as compile Help/Discuss plugins	1	633	April 21, 2019
Maven-publish plugin generated pom making dependency scope runtime Old Forum Archive	13	15712	February 19, 2015
Gradle-generated pom.xml marks all dependencies as runtime Bugs	3	3861	April 14, 2016
How to publish without adding dependencies to resultant POM Help/Discuss	1	676	April 20, 2023

Publishing plugin should respect compileOnly configuration

Related topics