Re: [pool] how to move to Java8?
Perhaps a path forward would be:
1) Release 2.6.1 now as is.
2) Update to Java 8 for 2.7.
I am OK with jumping to 2) over 1)
That would be up to the RM volunteering for this ;-)
On Sun, Oct 28, 2018 at 7:36 AM Gary Gregory <garydgregory@xxxxxxxxx> wrote:
> +1 for Java 8.
> On Sun, Oct 28, 2018, 06:13 Romain Manni-Bucau <rmannibucau@xxxxxxxxx>
>> +1 to move to java 8, java 7 is more than outdated today even for legacy
>> Le dim. 28 oct. 2018 12:10, Mark Struberg <email@example.com> a
>> écrit :
>> > Hi folks!
>> > I've worked through the open POOL tickets and found a few tickets which
>> > would like to enhance a few of our interfaces.
>> > E.g. in POOL-355 we have a request to add a new method getMaxNumActive()
>> > to the ObjectPool interface.
>> > Now this would of course be a backward compatibility breaking change. If
>> > we would have java8 as minimum then we could easily just add a default
>> > method which returns -1. But since our min Java version is 1.7 we are
>> > doomed...
>> > I would love to get the deadlock fixes out with the current 1.7
>> > requirement first. Because that's important to get to the people
>> > my own customers).
>> > But what after that?Would this justify a commons-pool-3.0?Do we also
>> > to cleanup other stuff? Or should we just raise our min Java
>> requirement to
>> > 1.8 and call it 2.7?
>> > I'm totally fine either way and would love to get any feedback.
>> > LieGrue,strub