Hi,
it seems we forgot to upgrade XStream to version 1.4.5 (or if we want the latest, 1.4.7),
which we needed to allow unrecognized fields to be ignored (which in turn allows easier migration between GeoServer versions).
What do you think? Should we do it before 2.5.0?
Or maybe do it on trunk, see if anything bad happens, and port back by 2.5.1?
Hi,
it seems we forgot to upgrade XStream to version 1.4.5 (or if we want the latest, 1.4.7),
which we needed to allow unrecognized fields to be ignored (which in turn allows easier migration between GeoServer versions).
What do you think? Should we do it before 2.5.0?
Or maybe do it on trunk, see if anything bad happens, and port back by 2.5.1?
Hi,
it seems we forgot to upgrade XStream to version 1.4.5 (or if we want the latest, 1.4.7),
which we needed to allow unrecognized fields to be ignored (which in turn allows easier migration between GeoServer versions).
What do you think? Should we do it before 2.5.0?
Or maybe do it on trunk, see if anything bad happens, and port back by 2.5.1?
On Sun, Feb 23, 2014 at 3:05 AM, Jody Garnett <jody.garnett@anonymised.com>wrote:
Is it worth doing a review of our dependencies and issuing an RC2.
Is there anything else besides xstream that is due for an update?
I would avoid doing further changes to the dependencies.
I proposed XStream for a couple of reasons:
* it's the same XStream series, just a few patch versions up
* it would allow us easier backport of functionality that requires extra
configuration in the 2.5.x series
On Sun, Feb 23, 2014 at 10:49 AM, Andrea Aime
<andrea.aime@anonymised.com>wrote:
On Sun, Feb 23, 2014 at 3:05 AM, Jody Garnett <jody.garnett@anonymised.com>wrote:
Is it worth doing a review of our dependencies and issuing an RC2.
Is there anything else besides xstream that is due for an update?
I would avoid doing further changes to the dependencies.
I proposed XStream for a couple of reasons:
* it's the same XStream series, just a few patch versions up
* it would allow us easier backport of functionality that requires extra
configuration in the 2.5.x series
And oh, looking at the changelogs, it also seems we need at least 1.4.6 to
run without issues
on jdk 1.8, which is about to be released (it's in RC, although the Linux
downloads are already
marked FCS, first customer shipment)
I'm upgrading master to 1.4.7 to see how that goes