Plugin breaks with com.android.tools.build:gradle:2.0.0-alpha1

[cypressious]

Syncing project crashes with following stacktrace:

Caused by: java.lang.NoClassDefFoundError: com.android.sdklib.repository.FullRevision
    at com.jakewharton.sdkmanager.internal.PackageResolver.class$(PackageResolver.groovy)
    at com.jakewharton.sdkmanager.internal.PackageResolver.$get$$class$com$android$sdklib$repository$FullRevision(PackageResolver.groovy)
    at com.jakewharton.sdkmanager.internal.PackageResolver.resolveBuildTools(PackageResolver.groovy:66)
    at com.jakewharton.sdkmanager.internal.PackageResolver.resolve(PackageResolver.groovy:58)
    at com.jakewharton.sdkmanager.internal.PackageResolver$resolve$0.call(Unknown Source)
    at com.jakewharton.sdkmanager.internal.PackageResolver.resolve(PackageResolver.groovy:20)
    at com.jakewharton.sdkmanager.internal.PackageResolver$resolve.call(Unknown Source)
    at com.jakewharton.sdkmanager.SdkManagerPlugin$_apply_closure2_closure3.doCall(SdkManagerPlugin.groovy:38)
    at com.jakewharton.sdkmanager.SdkManagerPlugin$_apply_closure2_closure3.doCall(SdkManagerPlugin.groovy)
    at com.jakewharton.sdkmanager.SdkManagerPlugin.time(SdkManagerPlugin.groovy:45)
    at com.jakewharton.sdkmanager.SdkManagerPlugin$_apply_closure2.doCall(SdkManagerPlugin.groovy:37)
    at org.gradle.listener.ClosureBackedMethodInvocationDispatch.dispatch(ClosureBackedMethodInvocationDispatch.java:40)
    at org.gradle.listener.ClosureBackedMethodInvocationDispatch.dispatch(ClosureBackedMethodInvocationDispatch.java:25)
    at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:44)
    ... 59 more

[plastiv]

This project directly depends on android gradle plugin api and has to be updated everytime googlers break that.
It would be nice to cut current changes into last 1.x release before migrating to 2.x.

[orrc]

Works for me with PR #100.

[dalewking]

ETA for release with PR#100?

[zsperske]

Any ETA on this?

[plastiv]

Until release it is possible to use jitpack (replace commit sha with the latest one)
#73 (comment)

[ligi]

Would be great if this could be released - jitpack works but readability of gradle files suffer

[danielgomezrico]

Im getting

Error:A problem occurred configuring project ':app'.
> Cannot cast object '23.0.2' with class 'com.android.repository.Revision' to class 'com.android.sdklib.repository.FullRevision'

and Im using:

buildscript {
  repositories {
    maven { url 'https://jitpack.io' } // sdk manager
  }

  dependencies {
    classpath 'me.tatarka:gradle-retrolambda:3.2.3'
    classpath 'com.github.JakeWharton:sdk-manager-plugin:0ce4cdf08009d79223850a59959d9d6e774d0f77'
  }
}

[dalewking]

@danielgomezrico The correct revision is 220bf7a

[danielgomezrico]

@dalewking 👍

[anuragdadheech]

Any ETA on release? weird using jitpack.

[iam1492]

+1 weird using jitpack..

[ligi]

just tagging a version would also be a good step - the upload to bintray/mavencentral is not that essential IMHO - but using the hash makes the gadle file hard to read ( or see what version one uses )

[FabianFrank]

+1

[josephmbeveridge]

+1

[jakubkrolewski]

+1
Yes, please, release a new version.

[bootstraponline]

+1

[jaggernod]

+1

[phajduk]

+1

[will-nolan]

+1

[dawidhyzy]

👍

[MikeyNick]

+1

[doneill]

+1

[dalewking]

C'mon Jake, I know you are busy, but it has been over 3 months. This library is used by a lot of people.

[casidiablo]

I worked around it by using jitpack.io:

repositories {
   maven { url "https://jitpack.io" }
}

dependencies {
  classpath 'com.github.JakeWharton:sdk-manager-plugin:master'
}

[ghost]

👍

[thebehera]

+1
AS 2.0 has been released now

[streetsofboston]

+1 for a release fixing this issue (especially since Android 2.0 is now released in stable channel)

[artem-zinnatullin]

Just friendly reminder to +1rs: GitHub now has emoji reactions feature on each comment/issue/pr/etc. Please use it instead of +1 comments.

[Valodim]

those don't work so well for attention though. and android studio 2.0 even nudges developers to update to gradle 2.0.0. hence:

👍

[epeterson-bb]

Any chance you could release build 0.12.1 off of the commit that includes the fix for this issue? It's blocking my project's ability to upgrade to Android Studio 2.0.

[pine]

👍

[rongi]

+1

[hetang]

+1

[AndreasBoehm]

+1

[RBWare]

Jitpack fix not working for me. I end up with

Error:Could not find org.rauschig:jarchivelib:0.6.0.
Searched in the following locations:
    https://maven.fabric.io/public/org/rauschig/jarchivelib/0.6.0/jarchivelib-0.6.0.pom
    https://maven.fabric.io/public/org/rauschig/jarchivelib/0.6.0/jarchivelib-0.6.0.jar
    https://jitpack.io/org/rauschig/jarchivelib/0.6.0/jarchivelib-0.6.0.pom
    https://jitpack.io/org/rauschig/jarchivelib/0.6.0/jarchivelib-0.6.0.jar
Required by:
    RBWare:app:unspecified > com.github.JakeWharton:idk-manager-plugin:master

[orrc]

@RBWare Stack Overflow would be the best place to ask such questions, rather than in an unrelated GitHub issue.

But idk-manager-plugin instead of sdk-manager-plugin?
And jcenter() doesn't appear to be in your list of repositories?

[RBWare]

SO closed my story, linking to the "jitpack" solution on another SO question. Which of course, doesn't work for me.

Per your suggestion, I've tried adding both jcenter() and mavenCentral() to list of repos. As soon as I do, I get

Error:Cause: com.android.sdklib.repository.FullRevision again.

Full addition:

buildscript {
    repositories {
        jcenter()
        maven { url 'https://maven.fabric.io/public' }
        maven { url 'https://jitpack.io' }
    }

    dependencies {
        classpath 'io.fabric.tools:gradle:1.+'
        classpath 'com.github.JakeWharton:sdk-manager-plugin:master'
    }
}

[orrc]

@RBWare I don't know what "the other solution" refers to, but it doesn't make sense to use master with JitPack.

From https://jitpack.io/docs/#how-to:

Add the dependency information:

• Group: com.github.Username
• Artifact: Repository Name
• Version: Release tag, commit hash or -SNAPSHOT

You should choose a recent commit hash, as listed under the "Commits" link on the JitPack page for this repo. I suppose master-SNAPSHOT should also work, but it's not a good idea to point at a moving target.

[RBWare]

This is the SO "other solution" I mentioned: http://stackoverflow.com/a/33889117/879082

master-SNAPSHOT again returns:

Error:Cause: com.android.sdklib.repository.FullRevision

I also tried using, 1d29782dd6ffa18880c8cbada748fb3dea45e7be, which is the latest commit to master, same issue.

[ligi]

you don't want to take from master at all - master is what is released - you want the unreleased stuff - hence the need for jitpack - but better asks these questions on StackOverflow

[RBWare]

Ideally, master is what should be released. However, there are commits to master... I'd say ~28 or so, since the last release of the library in 2014. I guess I'll just try again on SO.

[dtogias]

+1. Please release a new version

[Obfuscati0n]

+1

[Malachiasz]

please release this fix

[fmatosqg]

@JakeWharton regarding your answer on #117, would you be happier if someone else takes over the maintenance/releases responsibility? If true how can we make that transition happen, if not what is the next step towards making both you and the community happier?

This is a great plugin, I think it would be sad to have it discontinued.

[ZacSweers]

Use https://github.com/tadfisher/android-sdk-updater.

[stetro]

+1

[jayhack7]

Has anyone figured out anything concerning this problem? I feel like I'm in a Google rabbit hole...

[FabianFrank]

I've switched to the previously mentioned android-sdk-updatet script. The downside is that it doesn't infer your dependencies, but the upside is that it runs well with the 2.0 plugin and won't break when Google changes the Android gradle plugin.

[jayhack7]

OK, I'll try that. Thank you.