You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all the repo can be overridden by using extra.gradle. as changes done under feat: add custom repositories support #867
But still cordovaLib is using cordova.gradle have block
repositories {
google()
mavenCentral()
}
which means dependency io.github.g00fy2:versioncompare:1.4.1@jar could not be resolved using any internal artifact repository server like jfrog artifactory or nexus,
Feature Description
Extend the existing feature provided under feat: add custom repositories support #867 to cordova.gradle, means instead hardcoded repositories
repositories {
google()
mavenCentral()
}
Read the repos from the already placed repositories.gradle,
which is already in place for androidLib/build.gradle file. Same should be go in to the cordova.gradle. here is the example
Feature Request
Motivation Behind Feature
Currently all the repo can be overridden by using extra.gradle. as changes done under feat: add custom repositories support #867
But still cordovaLib is using cordova.gradle have block
repositories {
google()
mavenCentral()
}
which means dependency io.github.g00fy2:versioncompare:1.4.1@jar could not be resolved using any internal artifact repository server like jfrog artifactory or nexus,
Feature Description
Extend the existing feature provided under feat: add custom repositories support #867 to cordova.gradle, means instead hardcoded repositories
repositories {
google()
mavenCentral()
}
Read the repos from the already placed repositories.gradle,
which is already in place for androidLib/build.gradle file. Same should be go in to the cordova.gradle. here is the example
buildscript {
apply from: 'repositories.gradle'
}
Alternatives or Workarounds
Currently only workaround is to write custom hook to replace the repos mentioned in the cordova.gradle after platform add.
The text was updated successfully, but these errors were encountered: