commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [io] Make requirement Java 7?
Date Tue, 26 Apr 2016 14:25:29 GMT
On Apr 26, 2016 5:57 AM, "Dave Brosius" <dbrosius@mebigfatguy.com> wrote:
>
> People stuck on Java 6, for whatever inane reason, are in a very
restrictive use case, and as such are not likely doing 'progressive' things
like upgrading 3rdparty jars. I just don't see the point of trying to
support some of the new release's code base on java 6, and others on java
7. The extra management that's required is not worth the 2 people who want
a new version of commons-io for java 6. We are talking about an end of life
date coming up on 4 years.

Yes!

>
>
> Just upgrade the whole thing to 7.

Yes!

Gary

>
> -dave
>
>
> On 04/26/2016 08:41 AM, Emmanuel Bourg wrote:
>>
>> Le 26/04/2016 14:29, sebb a écrit :
>>
>>> How can we say that the source code is Java 6 compatible if it cannot
>>> be compiled with Java 6?
>>
>> It's Java 6 compatible at runtime, not at build time. We can say that
>> because:
>> - the project is configured to generate Java 6 compatible bytecode
>> - 99% of the code doesn't use Java 7 APIs
>>
>> The Java 6 compatibility stops if the new utils classes are used.
>>
>>
>>> The ASF releases source.
>>
>> Yes, and we release source that builds with Java 7 and runs with Java 6.
>>
>> Emmanuel Bourg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message