search

Mobbeel / fataar-gradle-plugin

Gradle plugin to help embed dependencies in generated AAR artifact
https://plugins.gradle.org/plugin/com.mobbeel.plugin
Apache License 2.0
342 stars 44 forks source link

Run assembleRelease or assembleDebug task of example-lib, the output aar does not include the nested-lib and nested-native-lib #29

Open wingyippp opened 5 years ago

wingyippp commented 5 years ago

What are the steps to reproduce this issue?

  1. Run the assembleRelease or assembleDebug task of example-lib;
  2. The AAR is generated in the build/output/aar directory;
  3. But the AAR does not include the example-nested-lib and example-nested-native-lib

What happens?

the AAR does not include the example-nested-lib and example-nested-native-lib

What were you expecting to happen?

Since the build.gradle of example-lib declared the dependencies of example-nested-lib and example-nested-native-lib, it should include the them in the AAR.

Any logs, error output, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Any other comments?

If the assembleRelease or assembleDebug of example-nested-lib and example-nested-native-lib is run before, let say these two AARs are generated. Then run the assembleRelease or assembleDebug of example-lib, the output AAR will include all its dependencies incorrectly.

pszklarska commented 5 years ago

@wingyippp What's your Gradle plugin version?

wingyippp commented 5 years ago

3.0.0

oscarcpozas commented 5 years ago

Let me check it out.

yandesheng commented 5 years ago

I also encountered this problem, as well as in the example project. I use gradle plugin3.1.4 and gradle 4.4。

derekyuwork commented 5 years ago

I also encountered this problem on gradle plugin 3.0.0 and gradle 4.4