... and how to find it out (in an authorative way)?
In Android Studio 0.8.11: when I check the same it shows 10.0.8.11. which corresponds to http://tool
I think I found a more specific answer, not perfect; it's really complicated as Scott said. I found that the android plugin is referenced from an external repository which is not on github in the getPlugins script:
git clone git://git.jetbrains.org/idea/android.git android
build.txt
in install folder)Unfortunately I didn't find any clear pointer to revision range in the Google Android Studio repo, but you can try matching by dates.
For 13.1.5 on the IntelliJ IDEA website > Downloads: Build: 135.1289
To give a rough estimation one can check in
IntelliJ IDEA\plugins\android\lib\android.jar\META-INF\plugin.xml
Where it's clear what is the minimum version is: <version>10.0.8.12</version>
, since any commits after that may be merged until this line changes to the next version.
For newer Intellij versions (2020+): The build-in Android Gradle Plugin version is visible in Settings -> Plugins -> Android
: 10.android-version.intellijbuild-version
Example:
Source: https://youtrack.jetbrains.com/issue/IDEA-252823#focus=Comments-27-4444522.0-0
It's complicated, and this will be a long answer. Unfortunately, we don't have a good short answer, because we don't do versioning of the plugin in a way that makes sense. This is something we should do.
To answer the question requires looking through JetBrains' commit logs for their different versions of IntelliJ. If I download the git repository for the Android plugin that ships with IntelliJ CE (see below for the longer answer with more details), I see this:
On to the long explanation:
The Android Build Tools team does 2-way code sharing with JetBrains. Android Studio is built on top of the 135 branch of the IntelliJ codebase (which explains the IC-135 you see in its build number), so Android Studio is derived from IJ 13.1.5, with some modifications and patches that haven't been upstreamed. We're not planning on moving to the 138 branch by the time we get to 1.0, so even at release it will still be 13-based, not 14-based.
On JetBrains' side, they mostly take upstream changes from Android for the plugin, but they also have folks working on the plugin on their side (and those changes get merged back down to the Android Studio end of things). At this point in 13's life cycle, they do releases of it slowly and are more conservative about what they pull into the Android plugin (in the interests of stability), so it's not completely up-to-date. They do releases for bug fixes in the main product and not to pick up the latest Android plugin.
In general it's probably not possible to upgrade just your Android plugin if you're running IJ 13. Changes to the plugin frequently require changes to the underlying platform; Android Studio will pick up those changes because its platform is releases along with its plugin, but IJ will need to wait until those changes are upstreamed. Having said that the rate of these changes is quite slow now, but it still happens.
For the 14 EAP release, they should be pulling changes from Android more rapidly, so that build should more closely reflect the current state of Android Studio, though again it depends on how often they do those pulls.
It should be noted that we don't coordinate releases or code pulls with JetBrains for the most part, so a given release of 14 EAP will reflect the current state of Android plugin at the time they did the code pull. As such, it may correspond to some state in between Android Studio releases.
To answer a question in the comments about why Android Studio and IntelliJ are separate products:
If you want everything in one IDE, then your best bet is to probably run IntelliJ CE or Ultimate. It should have all the important functionality of Android Studio, though it may be rougher to use in spots. If you find things that don't work right in it but do work in Android Studio (especially related to Gradle project support), then we consider it a bug, so please file it.