Use plugin in multi module project

[MitjaHenner]

When I use the license plugin in the app module of a multi module project im not getting all the dependencies.

Is there a solution to this?

I thought about adding it to every module but since they are all library modules the plugin doesn't work.

[PaulRashidi]

I've got a rather large revamp of the plugin dependency logic at https://github.com/paulrashidi/play-services-plugins/tree/refactor_dep_checking

It should support multi-module use although you should only really need it for your APK modules.

If you want you can see if it resolves things for you. There are instructions in the pull request I have going for it: https://github.com/google/play-services-plugins/pull/11#commitcomment-30466967

[MitjaHenner]

Im sorry, I was talking about the oss-plugin, its a bit confusing with two plugins on here.

[sperzion]

Perhaps this is related to issue 25? Do the POM files of the missing dependencies have licenses tags?

[sperzion]

@MitjaHenner have you tried specifying your other module dependencies like this: implementation project(path: ':submodule', configuration: 'default')? See issue 25.

[JarmoKukkola]

@MitjaHenner have you tried specifying your other module dependencies like this: implementation project(path: ':submodule', configuration: 'default')? See issue 25.

com.android.tools.build:gradle:3.4.0 gradle-5.1.1-all.zip

I think adding "configuration: 'default'" does not work anymore in recent Gradle version. The project compiles with

implementation project(path: ':submodule')

but not with

implementation project(path: ':submodule', configuration: 'default')

[lukas1]

does anybody have any news regarding this issue? I'm seeing the same problem as @JarmoKukkola