Hello Robert, just watched your JavaOne presentation. Very interesting :-)
Robert Scholte <[email protected]> schrieb am So., 25. Sep. 2016 um 13:48 Uhr: > It depends. If you are changing existing methods to only work with Java8, > that would be a problem (read: we cannot upgrade). If you have both Java8 > and pre-Java8 implementations, either by reflection or proper encapsulated > code it'll work for us. > We do it ourselves too[1] > > for us it would be nice if the target is still 1.7 > > if ( isJava8() ) > { // do java8 stuff } > else > { do classic stuff } ) > > if the java8 stuff uses reflection, you can build it with JDK7, otherwise > you must use JDK8 > We're thinking about adding APIs for dealing with e.g. Functions. So maven.compiler.source and maven.compiler.target would be 1.8. This would require downstream user to also compile with Java 8. If I understand correctly, this would be a problem for Maven, right? Regards, Benedikt > > Robert > > [1] > > https://maven.apache.org/shared/maven-shared-utils/xref/org/apache/maven/shared/utils/io/FileUtils.html#L831 > > On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter <[email protected]> > wrote: > > > Hi, > > > > at the Apache Commons Project we're currently discussing where we can > > host > > utility classes for working with the features introduced in Java 8. One > > proposal add this to Commons Lang [1]. Since Apache Maven makes use of > > Commons Lang, I would like to know whether it would be a problem for you > > if > > Commons Lang would require Java 8. > > > > Thank you, > > Benedikt > > > > [1] http://markmail.org/message/ecxc4brpxufamuzu > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
