1. What's the actual, under-the-hood difference be...

# gradle

[Chilli]

1. What's the actual, under-the-hood difference between implementation and compileOnly? The only difference I found on Google is that implementation is available at runtime, but what does it mean exactly? Without a special plugin, Gradle doesn't shade dependencies anyway, no?

[Big Chungus]

I'd also be interested to know how exactly implementation is different from api

[Albert Chang]

compileOnly dependencies are only used to provide symbols at build time and won’t be packaged into built program. This is useful e.g. when you are building a library and you provide RxJava bindings but not all users use RxJava and you don’t want RxJava dependency to be added for those who don’t, in which case you can use compileOnly.

[Albert Chang]

implementation dependencies are not available to the consumer of the library while api dependencies are.

[Hanno]

Yes, for normal compliation, the jar wont contain dependencies, you would need to add a pqckaging plugin so that there happens anything. There are different ways plugins process configurations Like implementation or compileOnly. The fat jar plugin embeds everything into a single jar, whereas the application plugin creates a dist zip with all the jars.

[no]

Does this help? https://stackoverflow.com/questions/44413952/gradle-implementation-vs-api-configuration

[Chilli]

@no
Not really, it describes the difference between implementation and api and not compileOnly.

[algo112]

compileOnly : put the dependency only on the compile classpath
implementation  : put the dependency on compile and runtime classpath

[wakingrufus]

the other factor is how they effect your downstreams. if you are writing library A, and B depends on you, compileOnly will not put the dep on B's runtime nor compile classpath, implementation will put it on B's runtime classpath only, and api will put it on B's compile and runtime classpath (like how compile dependencies worked)

[Chilli]

Would the built JAR files be any different? (without any shading or any plugin at all)

[Hanno]

No, it wont

[Hanno]

But the Metadata of the Module will be, so to put it really simple: your classes inside the jar will be the same, but the pom file in it will not