Re: [EXTERNAL] [Numbers][All] Separate Java target version for "src/test"

[Ralph Goers <ra...@dslextreme.com>]

I don’t understand this. Log4j2 was one of the first adopters of multi-release jars. 
There were problems in the beginning but those have virtually all been resolved. 
We haven’t had any complaints in ages. Log4j 2 2.14.1 supports Java 8. 

Fully supporting JPMS (i.e. - adding a module-info.java file) while trying to support 
Java 8 is another thing entirely. I gave up on that and the minimum JDK version 
for that will be Java 11.

Ralph

> On Jun 13, 2021, at 3:37 PM, John Patrick <nh...@gmail.com> wrote:
> 
> So I want to start using Java 11 and take advantage of Java Modules. But
> with a bug in Java Multi-Jar not supporting 1.8 as base and 11 upon that,
> and most dependencies I want to upgrade eventually get stuck on a commons
> project holding a pure JPMS solution.
> 
> Potentially someone raise an enhancement to drop support for Java 1.8 which
> isn't happening for Java 17, but for Java 18 which is only 8 month away it
> could happen. So at that point it might be a shock for commons projects as
> you might be blocking open source projects, or they roll off commons
> projects... just a thought.
> 
> I've tried to do a seamless upgrade, or suggest a roadmap, but haven't got
> anywhere, but think I might just raise a JEP to drop 1.8 in Java 18...
> 
> John
> 
> 
> On Thu, 10 Jun 2021 at 14:07, Gilles Sadowski <gi...@gmail.com> wrote:
> 
>> Le jeu. 10 juin 2021 à 14:42, John Patrick <nh...@gmail.com> a
>> écrit :
>>> 
>>> If the tests are valid and useful once post Java 1.8, what about
>>> starting the next release branch where the min version bumps to Java
>>> 11.
>> 
>> [Numbers] and related components were meant to replace and
>> improve some functionalities provided in [Math] v3.6.1 whose
>> target was Java 5 (!).
>> A few years ago, the bump to Java 8 was considered a bold move
>> (for "Commons"). :-}
>> 
>> If we are sure that Java 11 is no problem for anyone who'd go
>> through the upgrade effort, then indeed why not?
>> 
>> Gilles
>> 
>>> As Java 17 starting ramp down starts today I believe so in 3 months we
>>> will have 3 LTS (1.8, 11 and 17) releases. So technically Java 18
>>> development starts tomorrow and I expect 1.8 will be dropped shortly
>>> from backwards support as they want to get off the classpath fully and
>>> onto the modules path.
>>> 
>>> Anyway, just a thought.
>>> 
>>> John
>>> 
>>> On Thu, 10 Jun 2021 at 12:05, sebb <se...@gmail.com> wrote:
>>>> 
>>>> Thanks.
>>>> 
>>>> I've updated the RELEASE-NOTES accordingly (feel free to tweak the
>> text)
>>>> 
>>>> On Thu, 10 Jun 2021 at 00:58, Alex Herbert <al...@gmail.com>
>> wrote:
>>>>> 
>>>>> I have removed the requirement for Java 9 from the build. It is
>> still used
>>>>> in the performance testing module.
>>>>> 
>>>>> Alex
>> 
>> ---------------------------------------------------------------------
>> 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