Hi,
If there will be autodetect it should also detect JRE versions higher than 11 and not to use those. There has been a few cases like this https://gis.stackexchange.com/questions/360609/geoserver-feature-extraction-failed-to-retrieve-value-for-input-features/360613#360613 lately.
-Jukka Rahkonen-
(attachments)
···
Lähettäjä: Jody Garnett <jody.garnett@…403…>
Lähetetty: maanantai 28. kesäkuuta 2021 19.06
Vastaanottaja: Torben Barsballe <torbenbarsballe@…403…>
Kopio: GeoServer geoserver-devel@lists.sourceforge.net
Aihe: Re: [Geoserver-devel] PSC meeting notes, June 22nd 2021
Thanks for testing Torben! I am glad the new wrapper is working.
I expect we will need to fix the shortcuts before sharing with the user list.
Auto detecting a JRE is a good idea, I also like it when the scripts autodetect a “jre” folder in the install location making geoserver “self-contained”.
–
Jody Garnett
On Thu, 24 Jun 2021 at 10:55, Torben Barsballe <torbenbarsballe@…403…> wrote:
I tried out the Windows installer, here’s some feedback:
The actual install works fine, and the signing looks correct (OSGeo correctly shows up as the signing agency in the system popup).
I like the ability to choose the port and admin username/password through the installer.
One small nitpick - the ability for the installer to auto detect an existing Java install (assuming its in one of the normal places) would be cool, but that’s very much a nice-to-have.
The one issue I did run into is the start menu shortcuts to start/stop GeoServer are broken:
Inspecting the shortcuts, they point to (respectively):
- startService.bat instead of startup.bat
- stopService.bat instead of shutdown.bat
(They at least point to the right directory, just the wrong filename, so this should be an easy fix)
Using the correct bat files works fine - GeoServer starts up as expected, and seems to work as normal.
Cheers,
Torben
On Thu, Jun 24, 2021 at 10:06 AM Jody Garnett <jody.garnett@…403…> wrote:
GeoTools / GeoServer PMC meeting - 2021-06-22### Attending- Torben Barsballe
- Andrea Aime
- Patric Way
- Jody Garnett
Actions from last meeting:- [DONE] Torben: Add details on Cite Cleanup discussion to list
- [DONE] Torben: Add monthly docker system prune job to Jenkins
- Discuss removal of stale community modules on mailing list, then update main
- [FAILED] Jody: Try a scheduled delete/rebuild of S3 docs, to clean up dangling pages
Agenda1. OpenRewrite introductions
- GeoServer 2.18.4 release status update
- i18n GSIP update
- Windows installer update
- S3 Docs
- CITE tests, merging?
Actions- Test windows installer
OpenRewrite introductions
Introduction from Patrik, cool project
Looking at 4-5 migration, close enough to consider doing the rest by hand
Smaller recipes
Removing diamond operators
Removing unneeded throwables
Andrea: describe QA checks (with PMD and so on…)
- The combo of refactor needs a QA check to prevent problem from recurring
Consider a brute force check:
Add a QA check that applies the refactor, if any source code is changed then fail
Takes about about 20 mins so maybe not
Discussion on logistics
- Patrick is going to try a sample PR on removing unneeded throws
GeoServer 2.18.4 release status update
Everything is built,
Note: JIRA can now generate release notes in markdown + HTML, for more customizability
i18n GSIP update
Any further feedback?
- Some discussion on primary language - first in the list does not makes sense (because combines from service, and all layer documents)
- I would choosing from service, and add placeholder for admin if that primary language not available
Follow INSPIRE thing is the only real “standard”, the standards are silent (except WCS 2.0)
Messy situation:
- WCS 2.0 has support for languages, based on OWS 2.0
- Anything else does not, since they are based on OWS 1.1 or older (or not even based OWS, like WMS)
Windows installer update
Sander (geocat developer) asks for feedback on this file (for this a one-off, not yet part of the build): https://sourceforge.net/projects/geoserver/files/GeoServer/2.19.1/
- All the things are signed with osgeo certificate, please test
- Building in some azure environment, building and signing in linux did not work out.
Action: Ask the user list? Torben will test …
S3 Documentation
Follow up to last meeting and email discussion:
- AWS S3 remove / rysnc did not work due (sigh)
- We need to move to a different approach, like GitHub pages for just the current version.
Jody is still working on domains (this is needed before any documentation migration) …
CITE tests, merging?
Feedback
- Jody will ask devops folks to look at it from GeoCat (if not merge it).
Notes:
- Added some docker cleanups to avoid filling up jenkins
- Failures are reported as such now
Docker
What about actual geoserver/docker stuff?
- https://github.com/geoserver/docker ← anything? No update …
Tradeoff around production / training use:
Production
The one that includes extensions is slower to download/startup
Smaller startup, that downloads extension is faster to download, but results in network traffic
Having a small / fixed one for geoserver training use would be fine
Make a large image that includes extensions (already downloaded)
- Choose which ones are installed on initial startup
- For real production use folks could comment out which ones are already downloaded
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
