For more information check the release notes for beta2 (history beta1|M0)

Update to Spring 4 and JAI-EXT to 1.0.9

This 2.9-beta2 release is released in conjunction with GeoTools 15-beta2 and GeoWebCache 1.9-beta2. Thanks to Jody Garnett (Boundless) and Kevin Smith (Boundless) for this release.

Beta Testing

The GeoServer Team has been hard at work to bring you this beta release. Thanks to the committers for taking part in the emergency spring-4 upgrade and community members joining for subsequent testing and quality assurance: Justin Deoliveira and Andrea Aimie, Emanuele Tajariol, Damiano Giampaoli, Ben Caradoc-Davies, Niels Charlier, Mauro Bartolomeoli, Jody Garnett, Jukka Rahkonen, Brad Hards, Kevin Smith, Chris Snider, Torben Barsballe, Christian Mueller, Luigi Pirelli … and next you!

Here is our priorities for testing:

Seeking confirmation on Java 8 compatibility (test Oracle JDK and OpenJDK on a range of platforms)

Testing of the user-interface (although the team has performed extensive manual testing we need your help)

Release packaging (check for anything out of date, any issues starting up)

]]>http://blog.geoserver.org/2016/04/22/geoserver-2-9-beta2-released/feed/1GeoServer 2.9-beta releasedhttp://blog.geoserver.org/2016/03/01/geoserver-2-9-beta-released/
http://blog.geoserver.org/2016/03/01/geoserver-2-9-beta-released/#respondTue, 01 Mar 2016 23:36:55 +0000http://blog.geoserver.org/?p=2626The GeoServer team is pleased to announce the release of GeoServer 2.9-beta. This is a beta release, focused on making our wicket update available for testing, and trying out our release process to ensure we have not broken anything.

Beta releases are intended for public feedback and are not recommended for production use.

Download bundles are available (zip, war and exe). Our mac dmg is late to the party, we will update the blog post when it arrives.

Highlights:

This release requires Java 8.
We have identified one known incompatibility and may need to adjust our roadmap based on your testing and feedback.

Documentation has a new layout grouping service description and configuration reference together. Services that are an optional install (such as CSW and WPS) have been brought into a consistent location so you can easily see what GeoServer is capable of rather than getting lost in extensions.

Internally we have upgraded the user interface library – taking the opportunity to update global, image processing and raster access screens. The layer group page has also been split into tabs. By popular request the button to add a new layer has been renamed to “Add new layer”.

Legend graphic has always been auto-generated, you can use your own custom icons.

For installations without direct file system access you can now manage resources (icons, fonts,templates) using the REST API.

An useful improvement to the aggregation process is the group aggregate queries (sum, average, count) by an attribute.

This 2.9-beta release is released in conjunction with GeoTools 15-beta and GeoWebCache 1.9-beta. Thanks to Jody Garnett (Boundless) for this release.

A beta release often features lots of last-moment pull requests – thanks to Andrea Amie (GeoSolutions) and Ben Caradoc-Davies (Transient) for their assistance during this review cycle. A further thanks to Larry Shaffer (Boundless) and Chris Del Pino (Boundless) for their build assistance.

The big news for GeoServer 2.9-beta is upgrading our user interface from Wicket 1.4 to Wicket 7. A sprint was organized for this labour intensive task, with plenty of hard work and manual testing. We would like to thank our sponsors OSGeo, Boundless, Vivid Solutions, How 2 Map, San Jose Water Company, Transient and Geobeyond. We should also thank sprint participants and in-kind sponsors scitus development, GeoSolutions, CCRi, Astun Technology and Voyager for making this event possible.

I hope you are enjoying the new website – the download page for 2.6-beta provides links to the expected zip, war, dmg and exe bundles. For this release we are experimenting with providing source downloads directly from the GitHub 2.6-beta tag.

As a development release, 2.6-beta is considered experimental and is provided for testing purposes. This release is not recommended for production (even if you are excited by the new features).

This release is made in conjunction with GeoTools 12-beta. Thanks to Kevin for making a beta release of GeoWebCache 1.6.0-beta with relatively little notice.

What to expect … and what we expect from you

A complete change log is available from the issue tracker. We will ask you to wait for 2.6.0 before we let Andrea write a pretty blog with pictures illustrating what features have been added. Instead 2.6-beta is my chance to ask you to download GeoServer 2.6-beta for testing.

Testing is a key part of the open source social contract. The GeoServer team have identified a few areas where we would like to ask for help. This is your best chance to identify issues early while we still have time to do something about it. For those making use of commercial support ask your vendor about their plans for 2.6-beta testing. We would like to ensure the functionality you depend on is ready to go for a Q2 release.

When testing Geoserver 2.6-beta please let us know on the user list (or #GeoServer) how it works for you. We will be sure to thank you in the final release announcement and product presentations.

Java 7 Testing

With Oracle retiring Java 6 security updates the time has come to raise the minimum bar to Java 7.

We know a lot of downstream projects (such as OSGeo Live) have been waiting for GeoServer to support Java 7. Thanks to CSIRO, Boundless, GeoSolutions for providing Java 7 build environments allowing us to make this transition in a responsible fashion.

Testing:

This is a major testing priority on all platforms.

Windows 7: The start.bat used by the run manually install has trouble running as an administrator. We recommend installing as a service of this release (GEOS-5687)

Mac: You will need to install Oracle Java 7 (as OpenJDK 7 is not yet available for OSX). We have not yet figured out how to run GeoServer.App with Java 7 (GEOS-6588) and are open to suggestions.

This is a really exciting change, swapping out our gt-wfs client code for a new gt-wfs-ng implementation with a new GML parser / encoder. After comparing quality of the two implementations we decided to go all in with this transition .. and thus would really like your help testing.

Pay special attention to the flags used for axis order. There are different flags to account for each way a WFS implementation can get confused. You will find some implementations expect the wrong axis order on request, but are capable of producing the correct axis order output.

We especially ask our friends in Europe to test WFS services published for INSPIRE compliance

This was an epic amount of work by Niels and we have a couple of new features waiting in the wings based on the success of this transition.

Curves support for GML and WMS

A large amount of work has been put into extending the Geometry implementation used by GeoServer.

We have experimented with several approaches over the years (including ISO 19107 and a code sprint with the deegree project) and it is great to finally have a solution. As a long time user of the JTS Topology Suite we have been limited to a Point, Line and Polygon model of Geometry. Andrea has very carefully extended these base classes in to allow for both GML output and rendering. The trick is using a tolerance to convert the the arcs and circles into line work for geometry processing.

Testing for the 2.6-beta release is limited to those with Oracle Spatial. If you are interested in funding/volunteering support for PostGIS please contact the geoserver-devel email list.

Testing:

Look for “Linearization tolerance” when configuring your layer.

Advanced projection handling for raster

We would like to hear feedback on how maps that cross the date line (or are in a polar projection) have improved for you.

GeoServer 2.6 simplifies where configuration files are stored on disk. Previous versions were willing to spread configuration files between the webapps folder, the data directory and any additional directories on request. For GeoServer 2.6 configuration files are limited to the data directory as a step towards improving clustering support and growing our JDBC Config story.

Testing:

No special settings needed

Special request to check files that are edited by hand on disk (such security settings and free marker templates)

Scripting – includes a UI for editing scripts from the Web Administration Application

A final shout out to ask for help testing new formats:

NetCDF

Rib

OGR

Language Support

We are happy to announce the first release having support for Turkish. Many thanks to Engin Gem and the whole translation team for the initial contribution. All modules, core, extensions, and community modules have been translated within 8 month. Great success!

French, Korean, Polish, Romanian were corrected and updated to the latest developments. Thanks to all GeoServer Transifex translators and Frank for managing!

]]>http://blog.geoserver.org/2014/07/24/geoserver-2-6-beta-released/feed/0GeoServer 2.1-beta3 released (now with WMS 1.3)http://blog.geoserver.org/2010/12/20/geoserver-2-1-beta3-released-now-with-wms-1-3/
http://blog.geoserver.org/2010/12/20/geoserver-2-1-beta3-released-now-with-wms-1-3/#respondMon, 20 Dec 2010 15:38:13 +0000http://blog.geoserver.org/?p=811The GeoServer community is proud to announce the release of 2.1-beta3, which is now available for download.

The big feature for this release is support for WMS 1.3. Special thanks goes out to Ordnance Survey, Great Britain’s national mapping agency, for providing OpenGeo with funding to complete the task. With WMS 1.3 mandated by the INSPIRE Initiative, the Ordnance Survey needed to meet the INSPIRE requirements. Rather than implement a solution on their own, they opted to fund the GeoServer project so that other organizations in the UK and the rest of Europe and the world could all benefit.

This is the value and the beauty of open source. Government agencies across Europe can now upgrade their servers to the latest GeoServer at no additional cost. In time, other mapping agencies can and will further benefit one another by funding additional GeoServer improvements, like WFS 2.0 and Application Schema configurations for INSPIRE, but the Ordnance Survey deserves special recognition from all GeoServer users for taking the lead.

In addition to WMS 1.3, this release includes some SLD 1.1 / SE 1.1 enhancements. It will be possible to use most SE 1.1 documents, though not every new option is fully supported yet. User feedback on which new options we should support first is greatly appreciated. Also funded by Ordnance Survey is a community module to implement the WMS extensions for INSPIRE View Service compliance—namely the language parameter and several extended capabilities fields.

We encourage you to download GeoServer 2.1-beta3, try it out, and let us know if there are any bugs. This software is still a beta, so we recommend testing extensively before running it in a production environment. That said, we’re hoping to move to 2.1.0 release candidates soon, so any and all testing will this process move along faster.

]]>http://blog.geoserver.org/2010/12/20/geoserver-2-1-beta3-released-now-with-wms-1-3/feed/0GeoServer 2.1-beta2 now availablehttp://blog.geoserver.org/2010/12/06/geoserver-2-1-beta2-now-available/
http://blog.geoserver.org/2010/12/06/geoserver-2-1-beta2-now-available/#commentsTue, 07 Dec 2010 00:01:27 +0000http://blog.geoserver.org/?p=789We are pleased to announce the second beta release of GeoServer 2.1. Big thanks goes out to GeoSolutions for stepping up to the unglamorous and thankless process of creating a release, not to mention adding lots of great new features.

GeoServer 2.1.0 is shaping up to be quite an incredible step forward. In addition to all the great features of the first 2.1 beta, this release brings a few more.

Graphical File/Directory Chooser

Ever found it difficult to remember the full path when loading a shapefile or GeoTIFF? A new improvement brings an easy graphical file and directory selection tool to browse the file system that GeoServer is on. This is definitely a great enhancement to make GeoServer even easier to configure.

Core improvements to support database-backed catalog

GeoServer’s core catalog interfaces received some tweaks to be able to more easily support different backend storage formats. The current in-memory implementation has a number of drawbacks, the most notable being that it is memory bound which means it can not scale up to large amounts of layers. The support for specific new storage formats is still only available a community module, but these core improvements make it possible to more easily swap in and out different backends.

Font Improvements

Adding new fonts for your maps should now be much easier, as you can just drop font files directly in to your GeoServer data directory and they will be picked up by GeoServer. The admin interface also will list the fonts currently available, including the ones picked up directly from the Java Virtual Machine.

Upgrade to Spring Security 2.0.6

GeoServer has always had Acegi Security as its core, but that library got absorbed by the Spring community, and improved and upgraded to become Spring Security, the official security module of the Spring portfolio. This brings a number of new security protocols to GeoServer, including OpenID and Windows NTLM. It also should be easier to customize security setup, with even more powerful options.

WCS limits

WFS and WMS both have had the ability to limit what a user can request. Now, similar controls are in place for WCS calls as well. Thanks to MassGIS for funding this improvement.

Web Processing Service (WPS) in extensions

The one thing to note from last beta release is that the WPS is maturing, It has been split up in to three modules, “core”, “web”, and “sextante”. The latter has all the algorithms of the Sextante project, but is not yet mature, so it lives in a community module. Web and core live in a new WPS extension, meaning that the core of WPS is now officially supported by GeoServer. You can find the WPS extension on the download page, and add it to GeoServer just like any other extension.

And more

This release also included a number of other bug fixes and improvements. Check out the entire changelog. Help us get to a stable 2.1.0 by downloading the beta and trying it out. Be sure to report any issues on the mailing list or in the bug tracker. We appreciate any and all feedback. We’re hoping to move soon to Release Candidates, after getting one last major improvement in — WMS 1.3.

]]>http://blog.geoserver.org/2010/12/06/geoserver-2-1-beta2-now-available/feed/4GeoServer 2.0-beta2 Releasedhttp://blog.geoserver.org/2009/07/21/geoserver-20-beta2-released/
http://blog.geoserver.org/2009/07/21/geoserver-20-beta2-released/#respondTue, 21 Jul 2009 15:43:29 +0000http://blog.geoserver.org/?p=230The GeoServer community is happy to announce the second beta release of GeoServer 2.0, available for download. The developers have been working hard to get the new user interface up to the quality and functionality of the existing interface. This release of 2.0-beta2 brings us 74 issues closer to that goal.

The most noteworthy feature for 2.0-beta2 is the official inclusion of the app-schema extension. Most people probably know app-schema better as complex features, a feature GeoServer has been striving toward for the past three years. The extension gives GeoServer WFS the ability to support complex feature application schemas such as GeoSciML. Much thanks goes out to Ben Caradoc-Davies, Rini Angreani, and the rest of the AuScope* team for seeing this work through and actually making complex feature support a reality in GeoServer.

For those who missed the previous post about it, Ben and the folks from AuScope recently hosted a complex feature workshop in Perth, Australia, in which a number of the GeoServer developers were brought out. Special thanks for AuScope for hosting the event, which was a great success.

A special thanks also goes out to users who have been downloading the 2.0 alpha and beta releases, trying them out and reporting bugs. The more bug reports we get the faster we can get to the official 2.0 release. This should be the final beta release of 2.0 before it moves into release candidate phase, so stay tuned for RC1 coming soon.

* AuScope Ltd is funded under the National Collaborative Research Infrastructure Strategy (NCRIS), an Australian Commonwealth Government Programme.

]]>http://blog.geoserver.org/2009/07/21/geoserver-20-beta2-released/feed/0GeoServer 2.0, now in betahttp://blog.geoserver.org/2009/06/03/geoserver-20-now-in-beta/
http://blog.geoserver.org/2009/06/03/geoserver-20-now-in-beta/#respondWed, 03 Jun 2009 16:08:51 +0000http://blog.geoserver.org/?p=214The GeoServer Team is happy to announce GeoServer 2.0-beta1, the first beta release of the 2.0 series.

The primary focus of version 2.0 is the new user interface. This interface addresses many suggestions for usability improvements, including paging and filtering of lists of information, batch removal of layers, and the elimination of the Submit-Apply-Save workflow.

Another particularly useful feature added since alpha2 was released is cascading delete. This feature allows a user to remove a workspace or a data store and have all the entities contained inside (such as layers) also be removed. Previously, it was necessary to delete all layers individually before being able to remove a data store. To prevent unintended deletion, a confirmation page details what will be removed.

As usual a host of other fixes and improvements (over 100!) have also been incorporated into this release. Please download, give it a try, and forward your feedback along. We greatly appreciate reporting issues to the users mailing list and look forward to general feedback on the new user interface.