I found the release zip generation works just by adding the bintray dependency,
"classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'"
And ignoring
"classpath 'com.github.dcendents:android-maven-plugin:1.2'"
Also the,
"android-maven-plugin:1.2" is now moved to a new repo and from the official documentation we should use, "classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'" along with "apply plugin: 'com.github.dcendents.android-maven'" in app module.
Can you please clarify what would be the best approach for adding dependency at this moment?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I found the release zip generation works just by adding the bintray dependency,
"classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'"
And ignoring
"classpath 'com.github.dcendents:android-maven-plugin:1.2'"
Also the,
"android-maven-plugin:1.2" is now moved to a new repo and from the official documentation we should use, "classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'" along with "apply plugin: 'com.github.dcendents.android-maven'" in app module.
Can you please clarify what would be the best approach for adding dependency at this moment?