You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The library uses two dependencies which are part of the API and need to be used by the library user as well. But even though we mark them as api instead of implementation, they are mapped to runtime scope in resulting pom.xml instead of compile scope.
I tested that using java-library plugin fixes this, but that's not compatible with KMP.
Not sure if this is a bug of maven-deployer plugin, I created an issue there.
As a workaround, add these dependencies into your project manually:
The library uses two dependencies which are part of the API and need to be used by the library user as well. But even though we mark them as
api
instead ofimplementation
, they are mapped toruntime
scope in resultingpom.xml
instead ofcompile
scope.I tested that using
java-library
plugin fixes this, but that's not compatible with KMP.Not sure if this is a bug of
maven-deployer
plugin, I created an issue there.As a workaround, add these dependencies into your project manually:
The text was updated successfully, but these errors were encountered: