cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Grebnov (Akvelon)" <>
Subject Discuss Android plugin compatibility problem
Date Thu, 16 Jul 2015 15:27:05 GMT
Hi guys, I want to raise the following question - what we should recommend  plugin developers
to avoid 'Multiple dex files defined' issue on Android, for example [3]

UNEXPECTED TOP-LEVEL EXCEPTION: Multiple dex files define Landroid/support/v4/accessibilityservice/AccessibilityServiceInfoCompat$AccessibilityServiceInfoVersionImpl;

To reproduce this problem you can add both Facebook [1] and PushPlugin[2] and then build android

This happens due to we still use jars to add plugin dependencies, but there are several very
popular among them (like android-support, gson) so we bring the same dependencies several
times so build fails.

I think we should start recommending people to start adding utility/common/popular dependencies
via corresponding gradle configuration (not using libs folder) as the only way to support
multiple plugins which could rely on the same dependency. In this case gradle will be able
to handle this situation correctly using its smart Dependency Management/Versioning logic

For example,

<source-file src="src/android/com/plugin/android-support-v13.jar" target-dir="libs/" />
<framework src="" />

Disadvantage of this approach is that Ant build won't be supported (I know some tricky/more
complex way to correctly support both Ant and Gradle but I don't think it is worth adding
more complexity for plugins developers just to continue supporting Ant).

Guys, any recommendations/thoughts how we should proceed in this situation? Maybe someone
has better solution for this problem?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message