fix duplicate class problem, when the java-lib module is desired to be embedded in a far-aar library

[kanat]

By default embed configuration pulls the internal 'java-library' module dependencies into the fat-aar, which is not a desired behavior by default.

For instance, if you add dagger dependency to :example:lib-java:build.gradle file, that dagger dependency will be included into your final fat-aar.

[kezong]

There is such a problem.
I think #15 is the same problem.
Everyone's needs may be different, not everyone wants exclude the dependencies.
I think it would be better to add a new parameter in build.gradle, like this:

fataar {
    transitive = false  // default is true;
}

Could you improve the code?

[kanat]

Everyone's needs may be different, not everyone wants exclude the dependencies.

I would agree with you if that was true for any module, but currently transitive dependencies are included only if they were added to java-library, and excluded if they were added to com.android.library.

No need to add custom field. Gradle's configurations already have such a field, so you can switch it by adding this line to your build.bradle:
configurations.embed.transitive = false

Anyway, I guess it's better to add that information to README

[kezong]

Transitive dependencies are also included by remote repository with pom file.
In this way, the default value of transitive is false,which may be more appropriate.
At least, com.android.library,java-library and remote repository are all exclude the dependencies.
Thanks for your comments, I will merge the pull request later and update README and example the next time I upgrade the plugin.