[Geoserver-devel] 2.20-RC available for testing

GeoServer GeoServer Developer
1

No real issues releasing geowebcache, so on to geoserver:

Downloads:

Jira:

···

–
Jody Garnett

2

Tested:

  • war using tomcat 9.053 and it worked fine
  • docs included appropriate license and were complete
  • javadocs included notice and were fine
  • bin download also worked fine

I think we are ready to go without further testing since this is just a a release candidate

···

–
Jody Garnett

3

I have reviewed the unique fixes for 2.20-RC and assigned each to a component (in many cases “Community modules”).
Please double check https://osgeo-org.atlassian.net/issues/?filter=12122 which is used to outline what has changed for our release anouncement.

···

–
Jody Garnett

4

Headings for this page are incorrect: https://docs.geoserver.org/latest/en/user/services/index.html

···

–
Jody Garnett

5

Javadoc - downloaded and successfully unzipped. Local browsing looks good with
firefox. README.txt uses http instead of https (minor).

HTML docs - downloaded and successfully unzipped. Local browsing of user
manual, dev manual and api looks good with firefox. README.txt uses http
instead of https (minor). VERSION.txt doesn't have expected value
substitution:
version = 2.20-RC
git revision = ${build.commit.id}
git branch = ${build.branch}
build date = 2021-09-13T22:04:24Z
hudson build = ${build.hudsonId}
(minor)

source tarball - downloaded and successfully unzipped. README needs http ->
https at some point. Looks like its building against GT 2.26-RC. I am getting
a failure on one of the tests, but that doesn't appear relevant.

war - downloaded and successfully unzipped. VERSION has strange looking hudson
build:
hudson build = -1
but other parts look good (i.e. the substitution is working for that)
Booted it on tomcat9 and Ubuntu: 11.0.11 (OpenJDK 64-Bit Server VM), looks OK.

    GeoServer Version
    2.20-RC
    Git Revision
    757dd880f6916c48115cfd48981a655c3cf4ea4f
    Build Date
    13-Sep-2021 21:54
    GeoTools Version
    26-RC (rev 1557529d304800cbe8015de7722aee9d60caab2f)
    GeoWebCache Version
    1.20-RC (rev 1.20.x/a5c1c88f6474a8dc323ae501ae968af9d5cc064c)

Checked a few layer preview entries. All good.

Installed
geoserver-2.20-RC-charts-plugin.zip
geoserver-2.20-RC-csw-plugin.zip
geoserver-2.20-RC-excel-plugin.zip
geoserver-2.20-RC-mapml-plugin.zip
geoserver-2.20-RC-wps-download-plugin.zip
geoserver-2.20-RC-wps-plugin.zip

MapML looks nice in layer preview, except doesn't show anything for http://
localhost:8080/geoserver/mapml/tiger-ny/osmtile/
Haven't investigated that yet - other cases seem fine.

GetCapabilities seem good for CSW and WPS

Excel works in layer preview.

Brad

6

Thanks for the detailed testing, some comments inline.

On Fri, 17 Sept 2021 at 04:18, Brad Hards <bradh@anonymised.com> wrote:

Javadoc - downloaded and successfully unzipped. Local browsing looks good with
firefox. README.txt uses http instead of https (minor).

Here is a fix https://github.com/geoserver/geoserver/pull/5284

HTML docs - downloaded and successfully unzipped. Local browsing of user
manual, dev manual and api looks good with firefox. README.txt uses http
instead of https (minor). VERSION.txt doesn’t have expected value
substitution:
version = 2.20-RC
git revision = ${build.commit.id}
git branch = ${build.branch}
build date = 2021-09-13T22:04:24Z
hudson build = ${build.hudsonId}
(minor)

I am not exactly sure how VERSION.txt is populated, I believe in the root pom.xml here:

I am going to guess we need to update the jenkins job to provide those values missing values, some research here indicates Manage Jenkins > Configure System > Global Properties
This will be something for the 2.20.0 release volunteer to test/fix.

source tarball - downloaded and successfully unzipped. README needs http →
https at some point. Looks like its building against GT 2.26-RC. I am getting
a failure on one of the tests, but that doesn’t appear relevant.

Here is a fix https://github.com/geoserver/geoserver/pull/5284

war - downloaded and successfully unzipped. VERSION has strange looking hudson
build:
hudson build = -1
but other parts look good (i.e. the substitution is working for that)
Booted it on tomcat9 and Ubuntu: 11.0.11 (OpenJDK 64-Bit Server VM), looks OK.

GeoServer Version
2.20-RC
Git Revision
757dd880f6916c48115cfd48981a655c3cf4ea4f
Build Date
13-Sep-2021 21:54
GeoTools Version
26-RC (rev 1557529d304800cbe8015de7722aee9d60caab2f)
GeoWebCache Version
1.20-RC (rev 1.20.x/a5c1c88f6474a8dc323ae501ae968af9d5cc064c)

I assume with the change from hudson to jenkins we did not update our scripts. Something for the release volunteer to test/fix when 2.20 is made.

Checked a few layer preview entries. All good.

Installed
geoserver-2.20-RC-charts-plugin.zip
geoserver-2.20-RC-csw-plugin.zip
geoserver-2.20-RC-excel-plugin.zip
geoserver-2.20-RC-mapml-plugin.zip
geoserver-2.20-RC-wps-download-plugin.zip
geoserver-2.20-RC-wps-plugin.zip

Can you confirm that those show up in the server status modules tab? Ian did a bunch of work and I would love a screen snap for the next release announcement.

MapML looks nice in layer preview, except doesn’t show anything for http://
localhost:8080/geoserver/mapml/tiger-ny/osmtile/
Haven’t investigated that yet - other cases seem fine.

MapML adds some new gridset definitions, you probably need to configure tiger-ny to cache OSMTILE gridset. There was discussion about setting up alias so 900913 and OSMTILE would use the same cache.
Still the requirement to add OSMTILE gridset is a subject for the MapML docs.

Thanks again for testing Brad.

Jody

7

Hi Jody and Brad,

The tiger-ny group has a giant polygon that is a backdrop and extends to +/- 90. As such it throws when attempting to project to Web Mercator, and I haven’t figured out how to catch or avoid that yet, except to remove the giant polygon from the layer group.

Will get fixed eventually.

Thank you

Peter

On Fri., Sep. 17, 2021, 3:14 p.m. Jody Garnett, <jody.garnett@anonymised.com> wrote:

Thanks for the detailed testing, some comments inline.

On Fri, 17 Sept 2021 at 04:18, Brad Hards <bradh@anonymised.com> wrote:

Javadoc - downloaded and successfully unzipped. Local browsing looks good with
firefox. README.txt uses http instead of https (minor).

Here is a fix https://github.com/geoserver/geoserver/pull/5284

HTML docs - downloaded and successfully unzipped. Local browsing of user
manual, dev manual and api looks good with firefox. README.txt uses http
instead of https (minor). VERSION.txt doesn’t have expected value
substitution:
version = 2.20-RC
git revision = ${build.commit.id}
git branch = ${build.branch}
build date = 2021-09-13T22:04:24Z
hudson build = ${build.hudsonId}
(minor)

I am not exactly sure how VERSION.txt is populated, I believe in the root pom.xml here:

I am going to guess we need to update the jenkins job to provide those values missing values, some research here indicates Manage Jenkins > Configure System > Global Properties
This will be something for the 2.20.0 release volunteer to test/fix.

source tarball - downloaded and successfully unzipped. README needs http →
https at some point. Looks like its building against GT 2.26-RC. I am getting
a failure on one of the tests, but that doesn’t appear relevant.

Here is a fix https://github.com/geoserver/geoserver/pull/5284

war - downloaded and successfully unzipped. VERSION has strange looking hudson
build:
hudson build = -1
but other parts look good (i.e. the substitution is working for that)
Booted it on tomcat9 and Ubuntu: 11.0.11 (OpenJDK 64-Bit Server VM), looks OK.

GeoServer Version
2.20-RC
Git Revision
757dd880f6916c48115cfd48981a655c3cf4ea4f
Build Date
13-Sep-2021 21:54
GeoTools Version
26-RC (rev 1557529d304800cbe8015de7722aee9d60caab2f)
GeoWebCache Version
1.20-RC (rev 1.20.x/a5c1c88f6474a8dc323ae501ae968af9d5cc064c)

I assume with the change from hudson to jenkins we did not update our scripts. Something for the release volunteer to test/fix when 2.20 is made.

Checked a few layer preview entries. All good.

Installed
geoserver-2.20-RC-charts-plugin.zip
geoserver-2.20-RC-csw-plugin.zip
geoserver-2.20-RC-excel-plugin.zip
geoserver-2.20-RC-mapml-plugin.zip
geoserver-2.20-RC-wps-download-plugin.zip
geoserver-2.20-RC-wps-plugin.zip

Can you confirm that those show up in the server status modules tab? Ian did a bunch of work and I would love a screen snap for the next release announcement.

MapML looks nice in layer preview, except doesn’t show anything for http://
localhost:8080/geoserver/mapml/tiger-ny/osmtile/
Haven’t investigated that yet - other cases seem fine.

MapML adds some new gridset definitions, you probably need to configure tiger-ny to cache OSMTILE gridset. There was discussion about setting up alias so 900913 and OSMTILE would use the same cache.
Still the requirement to add OSMTILE gridset is a subject for the MapML docs.

Thanks again for testing Brad.

Jody

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

8

HTML docs - downloaded and successfully unzipped. Local browsing of user

manual, dev manual and api looks good with firefox. README.txt uses http
instead of https (minor). VERSION.txt doesn’t have expected value
substitution:
version = 2.20-RC
git revision = ${build.commit.id}
git branch = ${build.branch}
build date = 2021-09-13T22:04:24Z
hudson build = ${build.hudsonId}
(minor)

I am not exactly sure how VERSION.txt is populated, I believe in the root pom.xml here:

I am going to guess we need to update the jenkins job to provide those values missing values, some research here indicates Manage Jenkins > Configure System > Global Properties
This will be something for the 2.20.0 release volunteer to test/fix.

Did not find much in global properites, the related links are:

Suggest:

  • build.commit.id should probably figure this out from git after updating version and tagging?
  • build.branch may be from job parameter ${env.BRANCH}
  • build hudson id be replaced with ${env.BUILD_NUMBER}
9

Good to know, on a separate system I ran into an issue with the layer preview … as the layer group does not use OSMTILE, not usre if you have a chance to check what is supported when generating the layerpreivew link.

···

–
Jody Garnett

10

Hi Jody, Brad,

(copying list - omitted by my error)

I haven’t done checking on if the layer/layergroup could be shown in the selected projection, no. Sounds reasonable to do, although I’ll have to have a think on how to go about it.

What I really would like to achieve is to serve such a layer as a “custom projection”, where the projection and grid are defined similar to OSMTILE et al., but aren’t specifically known to the MapML specification via the TCRS name, but are defined in GeoServer/GeoWebCache/GeoTools. So in GeoServer, you could define an OSMTILE-like projection+grid and have the MapML preview link lead to that instead of OSMTILE (which is quite hard coded right now). I would like to figure out how to shoe-horn such a projection+grid definition into standard proj/WKT, ideally.

Here are some examples of custom projections, which use proj4.js strings: https://maps4html.org/experiments/#georeferencing-api (view source on those pages and you’ll see the definitions).

Sorry for hijacking this thread. Happy to discuss though!

Cheers,
Peter