Torben have you gotten any feedback? Is this in for tomorrows release ...
I do not see this as a risky change; adding a new event notification does
not have any backwards compatibility concerns.
--
Jody Garnett
On 10 February 2017 at 10:22, Torben Barsballe <[email protected]>
wrote:
> Continuing from earlier discussion, a GSIP is required in order for this
> change to actually get into GeoServer, see: https://github.com/geoserver/g
> eoserver/wiki/GSIP-157
>
> This proposal is to update the CatalogPostModifyEvent (and associated
> firePostModifed methods) to track changed values, similar to the current
> implementation of CatalogModifyEvent.
>
> This requires some API changes in a few catalog methods and interfaces.
>
> Ultimately, it is a useful, but relatively minor change requiring some
> not-backwards-compatible API changes.
>
> While I would like to get this into 2.11, I understand that it is cutting
> it a bit close to the code freeze at this point.
>
> Torben
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
