+1 to release as-is and postpone POOL-355, then +1 to Java8 later too
CheersBruno
From: Gary Gregory
To: Commons Developers List
Sent: Tuesday, 30 October 2018 4:17 AM
Subject: Re: [pool] how to move to Java8?
My view is to skip POOL-355 and release the current code still, on Java
I'm fine with sticking with Java 7 for Tomcat as long as the Jenkins build
continues to work properly. Keep an eye on the JDKs available! ;)
On Mon, 29 Oct 2018 at 10:28, Gary Gregory wrote:
> changes.xml is hand crafted and used to generate parts of the site.
>
> Gary
>
> On Mon, Oct 29, 2018 a
changes.xml is hand crafted and used to generate parts of the site.
Gary
On Mon, Oct 29, 2018 at 9:26 AM Mark Struberg
wrote:
> Yes, was not sure whether the changes.xml is generated or hand crafted.
> Gonna add the missing bits.
>
>
> LieGrue,
> strub
>
> > Am 29.10.2018 um 16:17 schrieb Gary
Yes, was not sure whether the changes.xml is generated or hand crafted.
Gonna add the missing bits.
LieGrue,
strub
> Am 29.10.2018 um 16:17 schrieb Gary Gregory :
>
> My view is to skip POOL-355 and release the current code still, on Java
> 7, as 2.6.1, or 2.7.0 if a new feature has been added,
My view is to skip POOL-355 and release the current code still, on Java
7, as 2.6.1, or 2.7.0 if a new feature has been added, which is not clear
since it seems changes.xml has not been updated for the commits over the
last week or two.
Gary
On Mon, Oct 29, 2018 at 6:49 AM Mark Struberg
wrote:
I've went through the list and pretty much the only ticket which was left to
really benefit from it would be the getMaxNumActive() (POOL-355).
But as noted there: after a bit of thinking through it I'm even tempted to
close it as won't fix. Having just a bare maxNumActive doesn't give you much
i
On 28/10/18 11:09, Mark Struberg wrote:
> 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
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 ;-)
Gary
On Sun, Oct 28, 2018 at 7:36 AM Gary Gregory wrote:
> +1 for Java 8.
>
> Gary
>
> On Sun, Oct 28, 2018, 06:13
+1 for Java 8.
Gary
On Sun, Oct 28, 2018, 06:13 Romain Manni-Bucau
wrote:
> +1 to move to java 8, java 7 is more than outdated today even for legacy
> systems
>
> Le dim. 28 oct. 2018 12:10, Mark Struberg a
> écrit :
>
> > Hi folks!
> > I've worked through the open POOL tickets and found a few
+1 to move to java 8, java 7 is more than outdated today even for legacy
systems
Le dim. 28 oct. 2018 12:10, Mark Struberg 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
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 chan
11 matches
Mail list logo
