I have an APP
and LIB1
, which has a dependency on LIB2
. If I connect LIB1
to the APP
as a module, then everything is OK. If LIB1
connect LIB1
to the APP
via the implementation files
, then when calling the method from LIB1
swear java.lang.ClassNotFoundException: Didn't find class "com.XXX.XXX.XLog" on path: DexPathList
. XLog is a class in LIB2
. Why is this happening?
|
LIB1
,LIB2
in the question? And what do you really want - why are you not satisfied with the dependence of the type "module"? And yes, theimplementation
dependency is visible only to this module, but not to its consumer. In order forAPP
seeLIB2
“through”LIB1
you need toLIB1
LIB2
asapi ...
inLIB1
api ...
(instead ofimplementation ...
) - woesss