posted Jul 11, 2013, 5:00 PM by Tor Norbye
[
updated Jul 12, 2013, 2:55 PM
]
We've just released Android 0.2.0, with the following changes: - Merged in the latest IntelliJ codebase changes. In addition to new features this includes fixes for issues reported by Studio users such as tweaks to Linux font sizes and font rendering.
- Gradle IDE integration fixes:
- Android Gradle plug-in 0.5.0. This new version of the plug-in is not backwards compatible. When opening a project that uses an older version of the plug-in, Studio will show the following error as a balloon in the upper right corner of the IDE:
 You will need to change the version of the Android Gradle plug-in to 0.5.0. Just click the link “Search in build.gradle files” to look for the places where this change needs to be made. (See the Troubleshooting section below for more info). - Gradle errors from
aapt no longer point to merged output files in the build/ folder, they point back to the real source locations - Parallel Builds. It's now possible to use Gradle's parallel builds. Please be aware that parallel builds are in "incubation" (see Gradle's documentation.) This feature is off by default. To enable it, go to "Preferences" > "Compiler" and check the box "Compile independent modules in parallel."
- Inter-module dependencies are now properly configured. Instead of depending on the compiled output, we link to the module itself, making it possible to debug code.
- Updated to the new Gradle Plugin version 0.5
- Fixed IDE model to contain the output file even if it's customized through the DSL. Also fixed the DSL to get/set the output file on the variant object so that it's not necessary to use
variant.packageApplication or variant.zipAlign - Fixed dependency resolution so that we resolved the combination of (default config, build types, flavor(s)) together instead of separately.
- Fixed dependency for tests of library project to properly include all the dependencies of the library itself.
- Fixed case where two dependencies have the same leaf name.
- Fixed issue where Proguard rules file cannot be applied on flavors.
- Release notes for the new Gradle plugin are here: http://tools.android.com/tech-docs/new-build-system
- Further work on the new resource repository used for layout rendering, resource folding in the editor, etc:
- Basic support for
.aar library dependencies (e.g. using a library without a local copy of the sources). Still not working for resource XML validation and navigation in source editors. - Cycle detection in resource references
- Quick Documentation (F1), which can show all translations of the string under the caret, will now also show all resource overlays from the various Gradle flavors and build types, as well as libraries. They are listed in reverse resource overlay order, with strikethrough on the versions of the string that are masked. In the below screenshot for example, we have flavors
f1 /f2 and fa /fb , and the string has both a default translation and a values-no version only in flavor fa , and this is all shown in the table which pops up when you press F1 with the caret on the string key name: You can also invoke Quick Documentation when editing a strings.xml file by invoking it in the name value attribute, to see all the alternate translations. Note that this feature is not just specific to strings; you can invoke Quick Documentation to see the various resource overlays of dimensions, drawables, etc. - Fixes to handle updating the merged resources when the set of module dependencies change
- XML rendering fixes to properly handle character entity declarations and XML and unicode escapes
- Save Screenshot support for the layout preview and layout editor windows
- Template bug fixes
- New projects now get a properly configured local.properties file on creation.
- Various bug fixes to the new project/module/activity wizards
- Lint bug fixes
- And fixes for a number of crash reports; thanks for submitting these.
InstallationTo install 0.2, you'll need to install a new Studio bundle. In other words, we are not offering a patch update from 0.1.9 to 0.2. The reason for that is that we have made changes to for example the bundled SDK such that it includes a pre-configured local Maven repository which can serve up the v4 support library.
NOTE 1: There are some early reports that people are running into problems on Windows if they just run the installer, and it installs itself on top of 0.1.9. Apparently if you don't delete the old installation, some older files end up interfering with 0.2.0 and causing runtime problems. See the Troubleshooting section for more. In short, you may want to move 0.1.9 out of the way first, such that 0.2.0 installs into a new, clean directory.
NOTE 2: There is a patch release available of 0.2 now, so you might be able to patch update from 0.1.9 to 0.2. In this case, your SDK bundled installation will not automatically pick up the bundled Maven repository serving up the android support library. So be sure to read the Troubleshooting section below for how to install it! TroubleshootingWe've extracted all the troubleshooting information for Studio 0.2.0 in the following document: tools.android.com/knownissues. If you run into problems, please visit the document, which gets updated regularly as we hear about issues and work on resolutions. |
|