renzoolguin
commented
6 years ago Resolving this issue actually takes two parts. @NiSHoW mentioned the first step. I confirmed it by testing that change in this fork.
The second step is fixing the plugin-build.gradle template in cordova-android. My current hacky solution is to run the following script as a cordova hook:
config.xml
<hook
comment="Update Cordova Plugin Gradle Template for Gradle 3.0+"
src="hooks/cordova-plugin-gradle-update.js"
type="after_platform_add"
/>hooks/cordova-plugin-gradle-update.js
module.exports = function(context) {
var fs = require('fs');
var pattern = /debugCompile (project\(.*)\,.*(\))\n\s*releaseCompile.*/g;
var replacement = 'implementation $1)';
var target = 'platforms/android/cordova/lib/plugin-build.gradle';
console.log('Updating Cordova Plugin Gradle Template to work with gradle 3.0+');
fs.readFile(target, 'utf8', function (err,data) {
if (err) return console.log(err);
data = data.replace(pattern, replacement);
fs.writeFile(target, data, 'utf8', function (err) {
if (err) return console.log(err);
console.log('Updated: ' + target);
});
});
};I'm not sure if and when cordova-android plans on fixing that. Ideally they will fix that in both versions 6.4.0 and 7.0.0. I say that because v7.0.0 introduced structural changes that I don't think most developers want to make right now.
If anyone has a better solution or knows of something that I'm missing, then please share.
Environment: Cordova-CLI: 7.0.1 Cordova-Android: 6.4.0 Gradle: 4.4.1
agamemnus
eAi
Saturnyn
erobertson42
Johnafriedman
There is a new system to add dependencies build-extra.gradle file of project download-library must be change like this
see this reference: https://stackoverflow.com/questions/33718663/gradle-error-configuration-declares-dependency-which-is-not-declared