Are there any objections to backporting #5996 immediately rather than waiting a month?
Did a test build with full tests and it works fine.
I switched the default to GEOSERVER_GEOJSON_LEGACY_CRS=true so it won’t break things for anyone expecting the old CRS representation. Setting the sys prop to either true or false makes the behaviour consistent across an upgrade from 2.5.x to 2.6.x.
Are there any objections to backporting #5996 immediately rather than waiting a month?
Did a test build with full tests and it works fine.
I switched the default to GEOSERVER_GEOJSON_LEGACY_CRS=true so it won’t break things for anyone expecting the old CRS representation. Setting the sys prop to either true or false makes the behaviour consistent across an upgrade from 2.5.x to 2.6.x.
Are there any objections to backporting #5996 immediately rather than waiting a month?
Did a test build with full tests and it works fine.
I switched the default to GEOSERVER_GEOJSON_LEGACY_CRS=true so it won’t break things for anyone expecting the old CRS representation. Setting the sys prop to either true or false makes the behaviour consistent across an upgrade from 2.5.x to 2.6.x.