Nach dem Upgrade von Cracklytics maven repo auf das neue Fabric maven repo und gradle plugin sind meine Gradle-Builds unglaublich langsam geworden.Fabric maven repo verursacht langsame Gravel-Builds
Das Problem scheint durch den Stoff Maven Repo Rückgabe eines 401 unauthorized Fehler verursacht werden, wenn gradle eine Abhängigkeit zu lösen versucht:
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/recyclerview-v7/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/appcompat-v7/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/support-v4/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/google/android/gms/play-services/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/support-annotations/21.0.2/support-annotations-21.0.2.pom]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/mediarouter-v7/19.0.1/mediarouter-v7-19.0.1.pom]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/support-annotations/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/recyclerview-v7/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/appcompat-v7/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/support-v4/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/google/android/gms/play-services/maven-metadata.xml]
Der alte Crashlytics Maven Repo diese Ergebnisse nicht zurück.
Hat jemand einen ähnlichen Fehler oder eine Lösung gefunden?
Nicht sicher, aber Sie m Ich habe das gleiche Problem wie hier: http://stackoverflow.com/questions/26854209/could-not-resolve-com-android-supportsupport-v421-0-0-required-by-com-twitter –