Why not just move to Java 7?
Gary
Original message
From: Thomas Neidhart
Date: 05/23/2015 02:17 (GMT-08:00)
To: Commons Developers List
Subject: [collections] Preparing a 4.1 release
Hi,
in the next few weeks I will hopefully finish all open issues for an
upcoming 4.1
On 05/24/2015 05:52 PM, Gary Gregory wrote:
> Why not just move to Java 7?
The reason to move to Java 6 is to add support for NavigableMap, which
unfortunately is missing right now.
Moving to Java 7 is not really necessary, the next logical move would be
to Java 8 imho.
In fact it would be worth
On Sun, May 24, 2015 at 7:52 AM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br> wrote:
> Hi Nial
> Do you know why your branch wasn't merged?
I dont really remember. I'm not sure whether all issues were resolved
(perhaps around tags doc generation). I sent the following email at the
start of 2
That all makes sense. Thanks for the clarification.
Gary
On Sun, May 24, 2015 at 10:37 AM, Thomas Neidhart wrote:
> On 05/24/2015 05:52 PM, Gary Gregory wrote:
> > Why not just move to Java 7?
>
> The reason to move to Java 6 is to add support for NavigableMap, which
> unfortunately is missing
Thanks for clarifying Niall.
I'll try to fix the tests, and will try to generate the Maven site and the tags
documentation.
Probably I'll update the commons-parent version in the pom.xml, and will use
the new bootstrap style too - which is already used by other commons components.
Once that's
