GeoServer 2.9-RC1 Released!

0

0

The GeoServer team is pleased to announce GeoServer 2.9-RC1. Downloads are available (zip, war, dmg and exe) along with docs and extensions.

This release is made by Torben Barsballe (Boundless) in conjunction with GeoWebCache 1.9-RC1 and GeoTools 15-RC1.

This is a release candidate for final testing before we release 2.9.0.

Highlights:

• This release requires Java 8 and is compatible with Oracle JDK and OpenJDK
• GeoServer now requires Servlet 3 (so Tomcat 7 or newer if you are doing a WAR install)
• Update to Spring 4 and JAI-EXT to 1.0.9
• For more information, check the 2.9-beta, 2.9-beta2, and 2.9-M0 release notes.

Fixes since beta:

• Naming geoserver layer differently from underlying postgis table causes aggregates to be omitted in SQL queries supporting time dimension in GetCapabilities and related operations.
• Web interface does not reflect workspace specific WPS enabled/disabled properly
• Enabling WPS for a workspace doesn’t appear on the GUI after reload
• WPS workspace specific configurations fails to load
• Drag and drop rules in GeoFence not working
• Restricting security on layers breaks aggregate visitor optimizations in JDBC stores
• Stacktrace when modifying the configuration of a WMS Cascade layer
• Update jetty version used by windows installer service wrapper
• Stacktrace with unsupported option in GWC Memory Blobstore
• PDF generation can contain invalid polygons whose fill bleeds out in the whole map

For more information see 2.9-RC1 release notes.

About GeoServer 2.9

Articles, docs, blog posts and presentations:

• Internals upgrade to spring-4 for Java 8 compatibility
• GeoServer code sprint success and wicket migration code sprint
• GeoServer Plugin for QGIS
• REST configuration Resources (docs)

GeoServer Community

GeoServer Community modules provide an area for ideas and experimentation. Community highlights for this release:

• The YSLD Styling language provides a more concise alternative to SLD, while still sharing the same structure.

Community modules should be considered a work-in-progress and are subject to quality assurance, documentation IP checks and a maintainer before being considered ready for release.

from Planet GS via John Jason Fallows on Inoreader http://ift.tt/1Tkdj6J
tbarsballe

John Jason Fallows

See author's posts