>
> > > -Original Message-
> > > From: Rob Tompkins
> > > Sent: Thursday, May 16, 2019 8:10 AM
> > > To: Commons Developers List
> > > Subject: Re: [IO] Update to Java 8
> > >
> > >
> > > On 5/15/2019 2:
//github.com/apache/commons-io/commit/6d46195e7cac37c28dd58f462e2d15cc1b1eb388
Gary
>
> > -Original Message-
> > From: Rob Tompkins
> > Sent: Thursday, May 16, 2019 8:10 AM
> > To: Commons Developers List
> > Subject: Re: [IO] Update to Java 8
> &g
elopers List
> Subject: Re: [IO] Update to Java 8
>
>
> On 5/15/2019 2:42 PM, Gary Gregory wrote:
> > Hi all,
> >
> > Time to update to Java 8 methinks.
>
> +1
>
> >
> > Gary
> >
>
> -
On 5/15/2019 2:42 PM, Gary Gregory wrote:
Hi all,
Time to update to Java 8 methinks.
+1
Gary
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Hi all,
Time to update to Java 8 methinks.
Gary
On Wed, 16 Jan 2019 at 10:52, sebb wrote:
> Unless there is a clear need to switch to Java 8, why force it on
> downstream users who may not be ready to upgrade?
I consider this to be a delicate balance between making projects
attractive to contributors and keeping compatibility with super old
On Wed, 16 Jan 2019 at 15:14, Gary Gregory wrote:
>
> On Mon, Jan 14, 2019 at 11:30 AM Matt Sicker wrote:
>
> > I'd be in favor of upgrading to Java 8. It would certainly make
> > porting my Jenkins deleteRecursive family of methods back upstream
> > easier (lambdas mainly). It would also allow
On Mon, 14 Jan 2019 at 16:30, Matt Sicker wrote:
>
> I'd be in favor of upgrading to Java 8. It would certainly make
> porting my Jenkins deleteRecursive family of methods back upstream
> easier (lambdas mainly). It would also allow for adding functional
> APIs for IO (which may also require some
On Mon, Jan 14, 2019 at 11:30 AM Matt Sicker wrote:
> I'd be in favor of upgrading to Java 8. It would certainly make
> porting my Jenkins deleteRecursive family of methods back upstream
> easier (lambdas mainly). It would also allow for adding functional
> APIs for IO (which may also require
I'd be in favor of upgrading to Java 8. It would certainly make
porting my Jenkins deleteRecursive family of methods back upstream
easier (lambdas mainly). It would also allow for adding functional
APIs for IO (which may also require some checked versions of
java.util.function).
On Sat, 12 Jan
On Sat, 12 Jan 2019 at 15:42, John Patrick wrote:
>
> Personally as a consumer/user I wouldn't expect a minor update to bump
> the min java version required, I would expect a major version number
> bump.
>
> Also I think all commons projects should be bumped to Java 8 asap, as
> those on java 5,
Personally as a consumer/user I wouldn't expect a minor update to bump
the min java version required, I would expect a major version number
bump.
Also I think all commons projects should be bumped to Java 8 asap, as
those on java 5, 6 or 7 are probably happy with the current versions
and would
I am OK with updating Commons IO to Java 8 for release 2.7.
Others?
Gary
On Sat, Jan 12, 2019 at 6:54 AM Arvind Venugopal
wrote:
> Hello,
>
> This is regarding the JIRA issue IO-597. I am not sure if this has to be
> taken up because the fix for this bug would need Java 8 which would be
>
13 matches
Mail list logo
