Missing 2.1-SNAPSHOT from maven repo

Hi guys,

could you put the missing 2.1-SNAPSHOT version in the repo again? Apparently there’s no way to force the substitute during annotation processing (or at least I haven’t found any), and gradle doesn’t tell me which library fails:

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:apt'.
   > Could not find com.google.dagger:dagger-compiler:2.1-SNAPSHOT.
     Searched in the following locations:
     ...
     Required by:
         sharethemealandroid:app:unspecified

[mrsasha]

ok, @hamen so I found a workaround for this and a way to prevent this error if you use libraries that are outside of your control. It might be useful to other people who encounter the same problem.

THE WORKAROUND: we cannot control external repo content, but what we CAN do is put the missing libraries in the local repo used for support libraries, usually here: ~/Library/Android/sdk/extras/google/m2repository/com/google/. How to do this? When seeing the above referenced error:

A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
  > Could not find com.google.dagger:dagger:2.1-SNAPSHOT.
    Searched in the following locations:

this searched in the following locations also mentions local repo - it will have file and not http URL - with a list of files he failed to find, like this:

file:~/Library/Android/sdk/extras/google/m2repository/com/google/dagger/dagger/2.1-SNAPSHOT/maven-metadata.xml
        file:~/Library/Android/sdk/extras/google/m2repository/com/google/dagger/dagger/2.1-SNAPSHOT/dagger-2.1-SNAPSHOT.pom
        file:~/Library/Android/sdk/extras/google/m2repository/com/google/dagger/dagger/2.1-SNAPSHOT/dagger-2.1-SNAPSHOT.jar

Now you can go and download the relevant files you want to use from jcenter.com or any other repo (I used the 2.1 release version), rename them as SNAPSHOT files, and put them in the above referenced folders. Gradle will now find them and you don’t have to look for the offending library (at least not immediately).

HOW TO PREVENT (for obvious reasons, you can do this only when you’ve fixed the problem):

• enable offline builds in Android Studio (File -> Settings -> Build, Execution, Deployment -> Build Tools -> Gradle -> Offline work option) OR
• use gradle build -g ./gradle-libs to put cached libraries in your local folder ./gradle-libs and then build using gradle assemble --offline -g ./gradle-libs; refresh the libraries only when you update gradle file, but make a backup of the cached libs folder in case something goes wrong.

[mrsasha]

Yes, once it’s fixed then it’s trivial to do gradle app:dependencies to find which library uses which version and then submit an issue or a fix.