Just as there was Retroweaver et al. for running Java 5 code with generics on Java 1.4, Retrolambda lets you run Java 8 code with lambda expressions, method references and try-with-resources statements on Java 7, 6 or 5. It does this by transforming your Java 8 compiled bytecode so that it can run on an older Java runtime. After the transformation they are just a bunch of normal .class files, without any additional runtime dependencies. Read more details.
There is also limited support for backporting default methods and static methods on interfaces. This feature is disabled by default.
Retrolambda supports backporting to Java 7, Java 6 and Java 5 runtimes. And for adventurous developers there are other backporting tools that may let you go from Java 5 down to Java 1.4.
Android developers may use Retrolambda to take advantage of the Java 8 features on Android. Serge Zaitsev has written an article about it and there is a Gradle plugin which makes it easy.
Retrolambda does not backport the new Java 8 APIs, but there are other projects that have backported some of them:
- streamsupport backports the
java.util.streamAPI - ThreeTen backports the
java.timeAPI
Retrolambda can be run as a Maven plugin, Gradle plugin or command line application. Also have a look at some tips for using Retrolambda effectively.
To run Retrolambda using Maven, add the following to your pom.xml:
<plugin>
<groupId>net.orfjackal.retrolambda</groupId>
<artifactId>retrolambda-maven-plugin</artifactId>
<version>2.0.6</version>
<executions>
<execution>
<goals>
<goal>process-main</goal>
<goal>process-test</goal>
</goals>
</execution>
</executions>
</plugin>See the plugin documentation for all possible parameters. There is also a usage example in end-to-end-tests/pom.xml
Gradle Retrolamba Plugin is developed by Evan Tatarka. See its site for usage instructions.
Download
the latest retrolambda.jar from Maven Central.
Use JDK 8 to compile your source code.
Run Retrolambda, using Java 8, on the class files produced by JDK 8. Run
java -jar retrolambda.jar without any additional options to see the
instructions (for your convenience they are also shown below).
Your class files should now run on Java 7 or older.
Usage: java -Dretrolambda.inputDir=? -Dretrolambda.classpath=? [-javaagent:retrolambda.jar] -jar retrolambda.jar
Retrolambda is a backporting tool for classes which use lambda expressions
and have been compiled with Java 8, to run on Java 7 (maybe even Java 5).
See https://github.com/orfjackal/retrolambda
Copyright (c) 2013-2015 Esko Luontola <www.orfjackal.net>
This software is released under the Apache License 2.0.
The license text is at http://www.apache.org/licenses/LICENSE-2.0
Required system properties:
retrolambda.inputDir
Input directory from where the original class files are read.
retrolambda.classpath
Classpath containing the original class files and their dependencies.
Optional system properties:
retrolambda.bytecodeVersion
Major version number for the generated bytecode. For a list, see
offset 7 at http://en.wikipedia.org/wiki/Java_class_file#General_layout
Default value is 51 (i.e. Java 7)
retrolambda.defaultMethods
Whether to backport default methods and static methods on interfaces.
LIMITATIONS: All backported interfaces and all classes which implement
them or call their static methods must be backported together,
with one execution of Retrolambda.
Disabled by default. Enable by setting to "true"
retrolambda.outputDir
Output directory into where the generated class files are written.
Defaults to same as retrolambda.inputDir
retrolambda.includedFiles
List of files to process, instead of processing all files.
This is useful for a build tool to support incremental compilation.
If the Java agent is used, then Retrolambda will use it to capture the
lambda classes generated by Java. Otherwise Retrolambda will hook into
Java's internal lambda dumping API, which is more susceptible to suddenly
stopping to work between Java releases.
Be sure to run comprehensive tests on your target JVM version (e.g. Java 7), in case the code accidentally uses Java 8 APIs or language features that Retrolambda doesn't backport.
During development, inside an IDE, it's the easiest to use Java 8, without Retrolamba, to compile and run tests. But in your continuous integration and release builds you should run all tests using the target Java version. For example, you can configure Maven Surefire Plugin to run tests using a different JVM.
I recommend setting up environment variables JAVA8_HOME, JAVA7_HOME etc. and referring to those variables in the build configuration, instead of relying on what happens to be the default Java version in JAVA_HOME.
You will need Java 8 for compiling and also for generating Javadocs. JDK 7's Javadoc tool will fail for some valid Java 8 code.
Lambda expressions are backported by converting them to anonymous inner classes. This includes the optimization of using a singleton instance for stateless lambda expressions to avoid repeated object allocation.
Method references are basically just syntax sugar for lambda expressions and they are backported in the same way.
Try-with-resources statements are backported by removing calls to
Throwable.addSuppressed if the target bytecode version is below Java 7.
If you would like the suppressed exceptions to be logged instead of
swallowed, please create a feature request and we'll make it configurable.
Optionally also:
Default methods are backported by copying the default methods to a companion class (interface name + "$") as static methods, replacing the default methods in the interface with abstract methods, and by adding the necessary method implementations to all classes which implement that interface.
Static methods on interfaces are backported by moving the static methods to a companion class (interface name + "$"), and by changing all methods calls to call the new method location.[1]
[1] The static methods are moved to a companion class even with default method support disabled, because some of them may be lambda implementation methods, but the method calls to static methods are not updated. This may cause weird error messages if static methods on interfaces are accidentally used without enabling default method support.
Does not backport Java 8 APIs.
Backporting default methods and static methods on interfaces requires all backported interfaces and all classes which implement them or call their static methods to be backported together, with one execution of Retrolambda. In other words, you must always do a clean build. Also, backporting default methods won't work across module or dependency boundaries.
May break if a future JDK 8 build stops generating a new class for each
invokedynamic call. Retrolambda works so that it captures the bytecode
that java.lang.invoke.LambdaMetafactory generates dynamically, so
optimizations to that mechanism may break Retrolambda.
- Fixed method references to constructors causing VerifyError on Android (Issue #67)
- Support for lambdas with marker interfaces (Issue #62)
- Fixed a compile error when calling default methods from another module (Issue #56)
- Fixed method references to constructors of the current class (Issue #60)
- Removes bytecode references to
java.lang.invoke.MethodHandles.Lookupon Java 6 and older (Issue #61) - Copies non-class files from input to output directory (Issue #54)
- Fixed Retrolambda generating stack map frames for Java 5 bytecode, causing some bytecode tools to fail (Issue #55)
- Fixed a hack which caused lambdas in interfaces to be backported twice, possibly producing broken method calls in the bytecode (Issue #48)
- Fixed the handling of non-static lambda implementation methods in
interfaces, i.e. lambdas which capture
this(Issue #48) - Removes generic method signatures from the default method implementation methods which are placed in the interface's companion class, to avoid them getting out of sync with their erased method descriptors (Issue #48)
- Fixed not backporting lambda expressions in default methods and static methods on interfaces (Issue #48)
- Backports default methods and static methods on interfaces (Issue #31)
- Backports lambda expressions in an interface's constant initializer (Issue #42)
- Backports try-with-resources statements to Java 6 and older by removing
calls to
Throwable.addSuppressed(Issue #38)
- Support for serializable lambdas (Issue #35)
- Fixed a crash when trying to backport Android classes (Issue #34)
- Fixed a crash when trying backport classes which are nominally the same as those included in the JRE, but which have different bytecode (Issue #29)
- Does not anymore require the use of a Java agent (Issue #27)
- Maven plugin: by default run Retrolambda in the same process as Maven, making it a bit faster. If Maven is not running under Java 8, then will fall back to forking the process and using the Java agent mechanism
- Maven plugin: use the JDK from Maven Toolchains
if available. The
java8homeconfiguration parameter overrides this (Issue #24)
- Added an optional
-Dretrolambda.includedFilesparameter to support the incremental compilers of build tools (Issue #23) - Decides which lambda classes to save based on the current class being processed, instead of the class loader that loaded the lambda class (Issue #21)
- Maven plugin: made the input and output directories configurable (Issue #20)
- Maven plugin: by default use the current JRE for running Retrolambda.
For the old behavior, add
<java8home>${env.JAVA8_HOME}</java8home>to the plugin configuration
- Android: Fixed NoSuchMethodError when calling a private method to which there is a method reference (Issue #18)
- Fixed the possibility of accidentally overriding private methods to which there is method reference (Issue #19)
- Fixed method references to private methods; will now make them package-private the same way as lambda implementation methods (Issue #17)
- Fixed the Retrolambda Maven plugin not using the project's classpath (Issue #16)
- Maven plugin: save
retrolambda.jarundertarget/retrolambda/ - Suppress false warning about class initializer methods on interfaces
- Maven plugin for running Retrolambda (thanks, Dave Moten)
- Removes from interfaces bridge methods which were generated by JDK 8 e.g. when an interface overrides a method and refines its return type (Issue #13)
- Fixed incompatibility with the Eclipse JDT compiler, version Kepler SR2 with the Java 8 support patch 1.0.0.v20140317-1959 (Issue #12)
- Updated to work with JDK 8 Early Access Build b121 (2013-12-19) (Issue #3)
- Show help if the
-javaagentparameter is missing (Issue #2)
- Create only one instance of lambdas which do not capture arguments; i.e. the same optimization as what JDK 8 does
- Start the sequence number of lambda classes from one (e.g.
com.example.Foo$$Lambda$1) for each enclosing class
- Backports lambda expressions and method references to Java 7 and older
- Tested to work with JDK 8 Early Access Build b99 (2013-07-19)