Sounds reasonable. I think you have your answer On Monday 26 September 2016, Stian Soiland-Reyes <[email protected]> wrote:
> If you don't mind helping with back porting, then we can help push > maintenance releases out :) > > On 26 Sep 2016 11:03 a.m., "Stephen Connolly" < > [email protected] <javascript:;>> wrote: > > > Well another question is how much longer will we support Java 7 anyway... > > what we have said in the past is the next release line after JDK9 is > > released will only support Java 8+... now we could change that, but that > is > > *currently* what we have currently stated. I suspect that a bump to Java > 8 > > by commons-lang would have a corresponding major version bump... would > that > > also include a package name relocation (ala commons-lang3) to indicate > > breaking API changes? > > > > Would the commons PMC object to us looking for maintenance releases on > the > > old line (perhaps even with us committing the fixes to the maintenance > line > > if necessary... IIUI commons is "open commit" so any Maven committer > > *should* have a commit bit on commons... we'd just need the commons PMC > to > > assist getting releases out)? > > > > I suspect the answers to the above are all favourable... in which case I > > say "don't let us hold you back" > > > > On 25 September 2016 at 15:20, Robert Scholte <[email protected] > <javascript:;>> > > wrote: > > > > > On Sun, 25 Sep 2016 16:11:22 +0200, Benedikt Ritter < > [email protected] <javascript:;>> > > > wrote: > > > > > > Hello Robert, > > >> > > >> just watched your JavaOne presentation. Very interesting :-) > > >> > > > > > > thanks! > > > > > > > > >> Robert Scholte <[email protected] <javascript:;>> 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? > > >> > > > > > > As long as we say that users can run Maven with Java7, then yes it > would > > > block us from upgrading. Is that a problem? Maybe, as long as we don't > > hit > > > a bug commons-lang. > > > > > > Robert > > > > > > > > > > > >> 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] <javascript:;>> > > >>> 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] > <javascript:;> > > >>> For additional commands, e-mail: [email protected] > <javascript:;> > > >>> > > >>> > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > <javascript:;> > > > For additional commands, e-mail: [email protected] > <javascript:;> > > > > > > > > > -- Sent from my phone
