Hello! I am using

api

instead of

implementation

for a dependency in my library, because my library builds as an extension on top of that library and would not be very usefull without. However, when someone uses my library the dependency declared with

api

is not exposed. Is there something I could have done wrong?

Maybe take a look at your pom file ?

It seems like adding

id("java-library") apply true

to plugins solved it (is it not supposed to work without it?) @mbonnin Sure, I am just off for lunch, will dig it up afterwards.

According to https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_separation, that sounds more or less like what is expected

Yes, so the problem is really that it is possible to use it without the plugin. You think you are using it but you don't. I have actually never used that plugin before, only the java plugin and the kotlin plugin.

That's the beauty of groovy, you can declare whatever you want and the (lack of) compiler will always be happy :troll:

Yeah, most of my more recent projects always uses Kotlin DSL instead. It its far from perfect either but I guess I would not have this problem there....?

Actually, the API configuration does exist, so it wouldn't fail there. The kotlin plugin adds a badly configured api configuration.

Okay, thank you @octylFractal