From 044120d5faa1550b48c98191428c08b29ef8e087 Mon Sep 17 00:00:00 2001 From: Evan Tatarka Date: Tue, 14 Apr 2015 17:23:08 -0400 Subject: [PATCH] update changelog and readme to reflect new greater importance of plugin application order --- CHANGELOG.md | 13 +++++++------ README.md | 17 ++++++++--------- 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ab10211..1276e83 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,24 +3,25 @@ - Fixed minor warning typo. - Uploaded to the gradle plugin portal. -### 3.0.0 +#### 3.0.0 A whole bunch of changes! - Changed the default retrolambda to 2.0.0 - Added support for default methods, add `defaultMethods true` to the retrolambda block. Note: due to a current limitation in retrolamba, this will require all of your class files to be fed through retrolambda on each build. This may adversely affect build times. - `incremental false` is no longer deprecated but has different semantics. Instead of being a hack - around gradle-retrolambda breaking other plugins, it now only forces all of your class files to be + around gradle-retrolambda breaking other plugins, it now only forces all of your class files to be run through retrolambda instead of only the changed ones. - Added support for android unit tests, including lambdas in the tests themselves. - No longer patch the android jar, modify the classpath instead. This should resolve issues with using gradle-retrolambda with more obscure android sdks, like google glass. This should also speed up a clean build since it doesn't have to do any zipping shenanigans. -- Ensure the gradle plugin is compiled with java 6 compatibility. This should allow you to run +- Ensure the gradle plugin is compiled with java 6 compatibility. This should allow you to run gradle with an older version of java if you don't want java 8 set as the default. This was always the intention, but was broken in the last build. -- More minor changes to how the java compile task is replaced, this should ensure better - compatibility with other plugins. +- More minor changes to how the java compile task is replaced, this should ensure better + compatibility with other plugins. Note: these changes make the plugin application order more + important. *Make sure you you apply this plugin last.* - Removed 'retrolambda', now you can only apply the plugin with 'me.tatarka.retrolambda'. #### 2.5.0 @@ -55,7 +56,7 @@ the gradle plugin portal. #### 2.2.3 -- Change dependency back to `localGroovy()`, `org.codehaus.groovy:groovy-all:2.3.3` was causing +- Change dependency back to `localGroovy()`, `org.codehaus.groovy:groovy-all:2.3.3` was causing issues. #### 2.2.2 diff --git a/README.md b/README.md index 561d1d8..0de2141 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ Usage id "me.tatarka.retrolambda" version "3.0.1" } ``` - + 3. There is no step three! The plugin will compile the source code with java8 and then replace the class @@ -84,7 +84,7 @@ retrolambda { - `exclude 'Test'` Sets which sets/variants to not run through retrolambda. Only one of either `include` or `exclude` should be defined. - `jvmArgs` Add additional jvm args when running retrolambda. -- `defaultMethods` Turn on default and static methods in interfaces support. Note: due to a +- `defaultMethods` Turn on default and static methods in interfaces support. Note: due to a limitation in retrolamba, this will set `incremental` to false. The default is false. - `incremental` Setting this to false forces all of your class files to be run through retrolambda instead of only the ones that have changed. The default is true. @@ -128,9 +128,9 @@ Known Issues --------------- ### Using Google Play Services causes retrolambda to fail Version `5.0.77` contains bytecode that is incompatible with retrolambda. This should be fixed in -newer versions of play services, if you can update, that should be the preferred solution. To work -around this issue, you can either use an earlier version like `4.4.52` or add `-noverify` to the jvm -args. See [orfjackal/retrolambda#25](https://github.com/orfjackal/retrolambda/issues/25) for more +newer versions of play services, if you can update, that should be the preferred solution. To work +around this issue, you can either use an earlier version like `4.4.52` or add `-noverify` to the jvm +args. See [orfjackal/retrolambda#25](https://github.com/orfjackal/retrolambda/issues/25) for more information. ```groovy @@ -139,7 +139,7 @@ retrolambda { } ``` -### Compiling for android-L doesn't work when using Android Studio's sdk manager. +### Compiling for android-L doesn't work when using Android Studio's sdk manager. For some reason only known to the gods, when using Android Studio's sdk manager, there is no `android-L` directory sdk directory. Instead, it happily builds using the `android-20` directory instead. To work around this, you can symlink @@ -147,9 +147,8 @@ the `android-L` directory to point to `android-20`. See [#36](https://github.com/evant/gradle-retrolambda/issues/36). ### Build fails with using `android-apt` -This is because `android-apt` modifies the `javaCompile` task and this plugin -replaces it. Since `v2.4.1` this is fixed, you just need to ensure you apply -this plugin _before_ `android-apt`. +This is because `android-apt` modifies the `javaCompile` task and this plugin +replaces it. Since `v2.4.1` this is fixed, you just need to ensure you apply this plugin _last_. Updates -------