Hi Jody, I upgraded my test installation from 2.20.4 to 2.21-RC using the windows installer. Everything works fine, including the Oracle-, Monitor- and GeoFence-Plugins. I changed the logging configuration like discussed with the 2.21-M0 release (DirectWriteRolloverStrategy/TimeBasedTriggeringPolicy) and logging works like expected, but I still have to set the full absolute path to the log folder in the FilePattern option (however this isn't a problem in my environment).
Regards Daniel From: Jody Garnett [mailto:jody.garn...@gmail.com] Sent: Tuesday, May 10, 2022 6:13 AM To: GeoServer Users <geoserver-users@lists.sourceforge.net> Subject: [EXTERN!]: [Geoserver-users] GeoServer 2.21-RC available for testing! The GeoServer 2.21<http://geoserver.org/release/2.20-RC/>http://geoserver.org/release/2.21-RC/-RC Release Candidate is available for testing, see release announcement<https://geoserver.org/announcements/2022/05/09/geoserver-2-21-RC-released.html> for a tour of what is new, improved and fixed! · Feature Type Customization - one of my favourite features has returned from GeoServer 1 much improved with ability to dynamically generate attributes! · A language chooser has been added! / Un sélecteur de langue a été ajouté ! · You can now define styles for SINGLE or OPAQUE layer groups (each style can gather together the content and styling needed to produce the correct visual) · GeoPackage WMS and WFS Output (for WPS output we recommend the WPS Downloader extension) · Log4J update, along with Logging REST API and user interface control of request logging. The log4j upgrade supported by activity sponsors opengeogroep.nl<http://opengeogroep.nl>, www.terrestris.de<http://www.terrestris.de>, how2map.com<http://how2map.com>, www.geonovation.nl<https://www.geonovation.nl/> · WPS KML input/output · GDAL 3.x compatibility for those using gdal bridge Thanks to Jody Garnett (GeoCat) for working on this release, and to everyone who has contributed to what is a fantastic update :) Helping test a release candidate is your chance to contribute directly providing testing and feedback on new functionality (and double checking if your favourite bug is fixed.) We ask everyone (individuals, organizations, service providers) to: 1. Download the release candidate<https://geoserver.org/release/2.21-RC/> 2. Test with your own data 3. Reply to this email (even just to say hi) Participating in testing release candidates is a key expectation of our open source social contract<http://www.ianturton.com/talks/foss4g.html#/>. · Helping test is the minimal price of admonition for GeoServer, don't be cheap share your time! · It also just makes good risk management sense; help making a stronger GeoServer · We make an effort to thank each person who tests in our release announcement and project presentations. · GeoServer commercial service providers<http://geoserver.org/support/> are fully expected to test on behalf of their customers. -- GeoServer Project Steering Committee
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
