[
https://issues.apache.org/jira/browse/CB-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513908#comment-15513908
]
Joe Bowser commented on CB-11590:
---------------------------------
CB-11083 is directly related to this.
> Gradle 'provided' not excluding dependancy from runtime
> -------------------------------------------------------
>
> Key: CB-11590
> URL: https://issues.apache.org/jira/browse/CB-11590
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Reporter: Steven Reid
> Labels: build, gradle
>
> I've created a build-extras.gradle to compile a 3rd party .jar dependancy
> into my application. This 3rd party .jar dependancy exists on the android
> device under systems/framework so I need to only compile it, but not provide
> it at run time (otherwise I get DEX issues because 2 identical .jar files
> exist at runtime).
> I've confirmed the .jar dependancy is compiled AND included in the apk file
> deployed to the android device using "dependancies { provided
> files('my-file.jar') }" in the build-extras.gradle file. Using android studio
> and a non-cordova based project i've used the same syntax (provided) and the
> my-file.jar was compiled BUT NOT included in the apk...thus it worked.
> Why isn't 'provided' working the same way it works on a non-cordova android
> project? And is there another way to get a .jar dependancy compiled but NOT
> included in the final apk file?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
