GeoServer Blog

Month in Review: October 2012

Read More

GeoServer 2.2.1 Released

The GeoServer team is happy to announce the release of GeoServer 2.2.1, now available for download.

A lot of fixes, improved security sub-system and new stable version of GeoWebcache included.


The GeoServer Team.


  1. GEOS-5279 (detail)

  2. Improved IM filter junit tests (detail)

  3. added check for null readParameters and fix format (detail)

  4. Layout fixes for IE (detail)

  5. Updating developer guide to require JDK 6 (detail)

Read More

What browsers do you use with GeoServer?

On the GeoServer developer list we’ve been discussing reducing browser support in the GeoServer web administration console - browser-based clients using OpenLayers and other JavaScript mapping libraries would be unaffected but the admin console would have support for fewer browsers.  Please help inform this decision by letting us know which browsers you are using to configure GeoServer at this web form:

We’ll review the results in one week. Thanks!

Read More

Month in Review: September 2012

There was some very interesting GeoServer-related content published  throughout this summer and into the fall. Individuals and organizations are working hard on the project, and making news daily. Below you’ll find some highlights from the last few months:

If we’ve missed anything comment on this post and we’ll make sure to check out your blog for next month.

Read More

Vienna Code Sprint

This past week a few of the GeoServer developers gathered for a code sprint in Vienna, Austria. The sprint was planned by some of the OpenLayers developers and they graciously allowed us to join the party and share the venue for the week.

Attendees from the GeoServer community included Andrea Aime, Niels Charlier, Justin Deoliveira, Alessio Fabiani, Christian Mueller, and Victor Olaya. With this seasoned team of committers in one location we decide to tackle a problem that has been plaguing developers for quite some time. Slow build and test times.

GeoServer, having been around for a while, has accumulated a large number of test cases in its 10+ years of existence. As of today the GeoServer code base contains 695 test classes and 3189 individual test cases. Wow. While many wouldn’t really consider good test coverage a problem it does come with a price. The more tests a project has the longer it takes to build.

Now like any other best practice following open source project we do have a continuous integration server that runs the tests whenever someone pushes up a change. But being the responsible bunch we are the developers usually run tests before a commit to ensure nothing breaks, especially for larger changes. Long build times start to make things tedious pretty fast. There is only so much coffee a developer can drink in one day.

Ok, enough about the problem, those interested in learning more should read over the recent GSIP that explains the problem and solution in detail. During the sprint the team outlined three goals: improving overall test times, upgrading the codebase to JUnit 4, and setting ourselves up to continue to make testing improvements in the future.

I am very excited to report that we accomplished all three of these goals. The 6 of us worked tirelessly to update every single test case in the codebase and the end result was about a 50% improvement making the build run twice as fast. The following chart shows the improvements in the various modules.

Great stuff. Thanks again to the developers who attended and made it such a productive week.

We’d also like to extend a very special thank you to the Research Group Cartography of the Vienna University of Technology for sponsoring the sprint by providing such an excellent venue. And an even bigger thanks to Andreas Hocevar who secured the venue, planned accommodations for attendees, and kept us all sufficiently caffeinated by brining along is espresso machine. Also a congratulations to the OpenLayers team who made some awesome progress toward OL3.

Read More