android-plugin pinned to Gradle 1.8?

[Davis Ford]

Hi, I upgraded to > Gradle 1.9-rc-4 but my build now generates the error:

> Gradle version 1.8 is required. Current version is 1.9-rc-4.

The line it is complaining about:

apply plugin: 'android-library'

So, does this mean the current plugin is pinned to 1.8?

The plugin I'm using:

dependencies {

    classpath 'com.android.tools.build:gradle:0.6+'

  }

[Jake Wharton]

Yes.

You should use the Gradle wrapper in your projects so that your system Gradle version has no effect.

---
Jake Wharton
http://about.me/jakewharton

--
You received this message because you are subscribed to the Google Groups "adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Davis Ford]

Hi Jake,

I'm aware of the wrapper, but I was interested in upgrading to the newer version of Gradle, regardless.  I scanned the ADT tools release notes, and this mailing list for any mention of "1.9" and came up empty, so I was trying to ascertain if the plugin requires 1.8 and will not work with the newer version -- the answer appears to be yes.

--
You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/Xntuvifurjg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

http://daisyworks.com

@zenocon

[Jake Wharton]

You can build and install a SNAPSHOT of the plugin locally to bump the version of Gradle that it is compatible with. Once 1.9 is actually released the plugin will be updated. The tools team has been timely in synchronizing across releases.

---
Jake Wharton
http://about.me/jakewharton

[Xavier Ducrohet]

We are currently using internal API*, so we make the plugin compatible with only known versions. Right now this only includes 1.8.

Once 1.9 is out we'll release an update that will enable 1.9 support (we have already tested it).

(*) obviously we are working to stop using them, but it's a work in progress.

Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com

Please do not send me questions directly. Thanks!

[Alexej Kubarev]

Is there a targeted release date for the updated Gradle plugin?

We are looking into starting to use 1.9 for many different reasons but Android plugin is currently setting a stop for it :-(

Also i did see that only "startsWith(MINIMAL_VERSION)" is used, where MINIMAL_VERSION is set to 1.8 (1.9 now in master).. Shouldn't it be possible to use both 1.8 and 1.9 at this point?

//Alex

[Xavier Ducrohet]

it's going to be a couple of weeks.

[Scott Battaglia]

Is there a new estimate for this?  (or did I miss an update?).  We're hitting a bug with doing local snapshot deployments that was fixed in 1.9 for which I am having trouble finding a workaround for in the current Gradle version.

Basically, in 1.8, the publish plugins don't respect the fact that when deploying a snapshot locally you don't use unique versions.

Thanks

Scott

[Tom Billiet]

I've seen the changelog of the android-gradle repo has been modified 7 days ago where now 1.9 is even mandatory: https://android.googlesource.com/platform/tools/build/+/master/changelog.txt
I'm wondering why 0.7.0 has not hit maven central yet?

Tom

Op dinsdag 10 december 2013 23:16:49 UTC+1 schreef Scott Battaglia:

[Jake Wharton]

Because it hasn't been released yet.