[Geoserver-devel] Geopackage rest upload issue

[Ian Turton]

Has anyone done anything to GeoPackage handling recently? I've just seen a
bug report on stackexchange which I can confirm -
https://gis.stackexchange.com/questions/484172/geopackage-data-store-errors-when-created-from-curl

Seems that uploading a gpkg (or zipped one) leads to GeoServer getting a
File when it expects a file name which obviously causes issues?

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

Re: [Geoserver-devel] Artefacts for 2.24.3 are ready to test

[Ian Turton]

Not that I can think of, release notes look like esoteric issues to me

Ian

On Fri, 19 Jul 2024 at 16:16, Jody Garnett  wrote:

> Thanks Ian,
>
> Testing a few things and it starts up and appears normal. Is there
> anything specific we should be looking for this release cycle?
> --
> Jody Garnett
>
>
> On Jul 19, 2024 at 6:42:15 AM, Ian Turton  wrote:
>
>>
>> https://build.geoserver.org/view/release/job/geoserver-release/lastSuccessfulBuild/artifact/
>>
>> Thanks
>>
>> Ian
>>
>> --
>> Ian Turton
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

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

[Geoserver-devel] Artefacts for 2.24.3 are ready to test

[Ian Turton]

https://build.geoserver.org/view/release/job/geoserver-release/lastSuccessfulBuild/artifact/

Thanks

Ian

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

Re: [Geoserver-devel] Resolving inconsistency between user experience of stores, and its actual impementation

[Ian Turton]

Wow, that's scarier than I thought it would be. Sounds like a great
improvement to me.

+1

Ian

On Mon, 15 Jul 2024, 16:52 Andrea Aime, 
wrote:

> Hi all,
> in GeoServer we have had for ages an inconsistency between what we present
> in the UI, store wise, and the actual behavior for creating stores, that
> I'd like to make consistent.
>
> UI wise, one goes to create a store, and chooses a specific store type,
> getting its associated form. When enumerating the available stores, one
> also has certainty about the store type, and it's consistent with what was
> chosen in the GUI:
>
> [image: image.png]
>
> So far so good, but when the actual creation happens, things can take
> another route.
> Let me give you some code pointers.
>
> *Finding the Store type *
> The above page populates the "type" column calling
> ResourcePool.getDataStoreFactory(storeInfo
> 
> )
> The method first checks the StoreInfo.getType (e.g., GeoPackage), and
> looks it up based solely on that, matching with the display name of
> factories. If that does not work, then it falls back on using the
> connection parameters.
> This fall back is useful and important, it allows to plugin an alternative
> factory that can handle the same parameters, allows for code upgrades (e.g,
> old jdbc stores vs ng ones, as it happened a few years ago).
>
> *Creating the store*
> ResourcePool.createDataAccess
> 
>  is
> responsible for creating the store. It first looks up a factory by name,
> does some checks on it (and actually throws an exception if the factory is
> not found) and then... throws everything away and creates the store by just
> using the parameters!
>
> The above situation is normally consistent because we try to have stores
> with parameters that are different enough, that two store won't collide
> but it's pretty fragile, and indeed it broke, because the FlatGeoBuf store,
> does not have one of those discriminator fake parameters...
> and the result is this:
> https://osgeo-org.atlassian.net/issues/GEOS-10824
>
> Now, we can add a discriminator to FlatGeoBufDataStoreFactory, or we might
> try to check for well known FGB extensions, sure, but these all look like
> workarounds for a simpler, more basic deficiency: as a user... I've already
> told GeoServer exactly what it should be using, and it even saved my
> choice... why would it try to guess it again? (especially after having
> looked up the factory by name anyways!)
>
> What I'm proposing is a very modest change: in ResourcePool, while
> creating the store, if a factory has already been successfully looked up,
> please try to use it first, and fall back on the current dynamic lookup
> only if that fails. It's a few lines change that should make both developer
> and user experience better. And I'll also change it so that if the factory
> is not found, it won't throw an exception (because really, it shouldn't, it
> should try the dynamic lookup instead).
>
> Objections?
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list

Re: [Geoserver-devel] GSIP-225 - Migrate geoserver-users from SourceForge to discourse

[Ian Turton]

+0

I can see moving to a new service but I'm not sure if discord is an
improvement

Ian

On Thu, 25 Apr 2024 at 16:24, Jody Garnett  wrote:

> I have collected notes from yesterday's meeting into a proposal.
>
> GSIP-225 - Migrate geoserver-users from SourceForge to discourse
> <https://github.com/geoserver/geoserver/wiki/GSIP-225>
>
> The proposal is held open for 10 days until Monday May 6th.
>
>
>- Alessio Fabiani
>- Andrea Aime
>- Ian Turton
>- Jody Garnett +1
>- Jukka Rahkonen
>- Kevin Smith
>- Nuno Oliveira
>- Peter Smythe
>- Simone Giannecchini
>- Torben Barsballe
>
>
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GSIP-224 Individual Contributor clarification

[Ian Turton]

+1

Ian

On Tue, 9 Apr 2024, 18:57 Jody Garnett,  wrote:

> Proposal for discussion
> https://github.com/geoserver/geoserver/wiki/GSIP-224
>
> New text proposed for
> https://docs.geoserver.org/latest/en/developer/policies/committing.html
>  page:
>
> All contributors are asked to provide an assignment agreement for working
> on the project:
>
>
>- individual_contributor
>   
>   - Individual contributor agreement.
>
>
>
>- corporate_contributor
>   
>   - Corporate contributor agreement to authorize employees to work on
>   project. May also be used as a software grant to donate software to the
>   project.
>
>
> GeoServer recognizes that organizations of all shapes and sizes support
> our project with in-kind participation of their employees. Extending commit
> access is made to individuals directly based on their expertise
> demonstrated over time.
>
>
> Thanks!
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer 2.24.3 release manager wanted

[Ian Turton]

I'm away this week but I can do May

Ian

On Wed, 10 Apr 2024 at 10:40, Andrea Aime 
wrote:

> If there are no other takers, I had a scheduled release in May, can move
> it down this month instead.
>
> Regards,
>
> Andrea Aime
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
>
> On Tue, Apr 9, 2024 at 7:21 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi all,
>> the GeoServer 2.24.3 release is due April 18th, currently we don't have a
>> release
>> manager. Any takers?
>>
>> Cheers
>> Andrea
>>
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GSIP 223, Community module graduation, amending generality rule

[Ian Turton]

+1

Ian

On Tue, 26 Mar 2024 at 07:19, Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> +1
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* Torben Barsballe 
> *Lähetetty:* tiistai 26. maaliskuuta 2024 7.11
> *Vastaanottaja:* Andrea Aime 
> *Kopio:* GeoServer 
> *Aihe:* Re: [Geoserver-devel] GSIP 223, Community module graduation,
> amending generality rule
>
>
>
> +1
>
>
>
> Cheers,
>
> Torben
>
>
>
> On Thu, Mar 14, 2024 at 11:21 AM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
> Hi all,
>
> based on the conversations on list and during the PSC meeting, here is
> GSIP-223, to amend the community module graduation generality rule:
>
>
>
> https://github.com/geoserver/geoserver/wiki/GSIP-223
>
>
>
> Further feedback and votes welcomed. As indicated before, please stay on
> topic (rule 1 of the module graduation rules), collateral discussion is
> welcomed in its own separate thread.
>
>
> Regards,
>
> Andrea Aime
>
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
>
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Pre-proposal discussion, amending community module graduation rules

[Ian Turton]

Have we ever actually enforced the 3 users rule? Anyway I'm+1 on relaxing
it if it's causing an issue.

It might make sense for us to allow a company like GeoSolutions to be a
module maintainer for better continuity and general reassurance of the
community that a module will be supported.

Ian

On Tue, 12 Mar 2024, 15:04 Simone Giannecchini, <
simone.giannecch...@geosolutionsgroup.com> wrote:

> Hi Andrea,
> as you know from our internal discussion I pretty much agree on everything.
>
> The three users rule is making it difficult for many users to use
> community modules in prod which is making it very difficult to reach the 3
> users rule.
>
> Regards,
> Simone Giannecchini
> ==
> Online training classes for GeoNode, GeoServer and MapStore from the
> experts!
> Visit https://www.geosolutionsgroup.com/professional-training/ for more
> information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director GeoSolutions Italy
> President GeoSolutions USA
>
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob:   +39  333 8128928
> US: +1 (845) 547-7905
>
> http://www.geosolutionsgroup.com
> http://twitter.com/geosolutions_it
>
> ---
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
>
>
> On Tue, Mar 12, 2024 at 12:20 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi all,
>> I'm starting this conversation to see if/how we can amend the procedures
>> for graduating a community module a bit.
>>
>> For reference, the current procedure is here:
>>
>> https://docs.geoserver.org/latest/en/developer/policies/community-modules.html#id2
>>
>> In particular, I'm thinking about requirement "1", the module has at
>> least 3 users.
>> The reason for the check is a good one, we don't want to clutter the main
>> code base with modules that are specific to one single user site. At the
>> same time, this creates a "chicken and egg" problem, because many sites
>> won't consider using a module until it's supported.
>>
>> So, I'd like to keep the intent of requirement 1, but propose a change in
>> its implementation. 3 usage sites can be one of the options, but can we
>> also consider a PSC opinion on the matter as a valid alternative? And a PSC
>> member can provide feedback on the module generality while the graduation
>> is being voted.
>>
>> I know that Jody wants to also talk about point 3 (module being stable,
>> as a prerequisite, the standards that the module is based on being stable
>> too), but can we please have a separate thread for that?
>>
>> Best regards
>> Andrea
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net

Re: [Geoserver-devel] PSC Nomination: Peter Smythe

[Ian Turton]

+1

Ian

On Wed, 17 Jan 2024 at 19:10, Jody Garnett  wrote:

> I have been meaning to discuss this at the last several geoserver meetings
> - but we have had stacked agendas.
>
> I would like to nominate Peter Smythe for the GeoServer Project Steering
> Committee, and have checked that he is willing to be nominated (thanks
> Peter).
>
> My nomination is two fold:
>
> a) Peter has been a great addition to the team, and has demonstrated the
> community perspective expected of steering committee members: taking on
> maintenance / communication / community care and feeding activities. He has
> also done this with some joy and enthusiasm which is welcome and a good
> reflection on his character.
>
> b) It is good to have a balance of perspectives on the project steering
> committee from different organisations (something we should always try and
> seek out).
>
> Our procedure is here
> https://docs.geoserver.org/latest/en/developer/policies/psc.html#new-psc-members
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] osgeo discourse option for mailing list / forum

[Ian Turton]

te. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.*
>
>
>
> * This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.*
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] [Geotools-devel] Time to upgrade Spotless... and maybe take advantage of the break?

[Ian Turton]

Sounds good to me, not too bothered by which one we go with.

Ian

On Tue, 2 Jan 2024, 17:06 Andrea Aime, 
wrote:

> Hi all,
> you probably know that we are formatting the source code with the Spotless
> Maven plugin,
> in combination with the Google Java Format library.
>
> Currently, we are using an older version of both, because they upgraded
> time ago to require Java 11 as the minimum version, and we were still using
> Java 8. But we have been on Java 11 for a while now, and we can update up
> the dependencies.
>
> I've prepared a pure upgrade of GeoTools, as an example, here:
> https://github.com/aaime/geotools/tree/spotless_upgrade
>
> The update touches 2k files, mostly changing the javadoc style for single
> line javadocs, to use three lines instead. Lots of noise, no significant
> gain in my opinion.
>
> One formatting library that I've been keeping an eye on for a while is
> Palantir's fork of Google Java format. They made some significant changes:
>
>- 4 spaces indent by default (we get this by adopting the AOSP style
>of Google's one)
>- 120 columns rather than 100
>- Formatter optimized for streams and functional style to use less
>space.
>
> They have some significant examples in their landing page
> .
> I've tried this out with GeoTools, and linking what I've found, also with
> GeoServer (both are best viewed offline, in a checkout):
>
>- https://github.com/aaime/geotools/tree/spotless_palantir
>- https://github.com/aaime/geoserver/tree/spotless_palantir
>
> In this case, the GeoTools diff is significantly bigger than the pure
> Spotless upgrade, touches 2k files, but in the end, manages to cut down 60k
> lines of code.
>
> What is your opinion? Would you like to go with Palantir?
>
> If we went down that road, I'd recommend to:
>
>- Wait until the Wicket 9 upgrade is done
>- Wholesale reformat all three projects (GeoTools, GeoWebCache,
>GeoServer)
>- Reformat all active branches for ease of backport (if this ends up
>landing after the 2.25.x release, maybe also reformat the 2.23.x series as
>it will likely get some extra fixes in the next few months).
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> geotools-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-221 mkdocs proposal (closing January 3rd)

[Ian Turton]

+1

Ian

On Wed, 20 Dec 2023, 06:22 Jody Garnett,  wrote:

> I would like to make the following proposal:
>
>
>- GSIP-222 mkdocs
><https://github.com/geoserver/geoserver/wiki/GSIP-221>
>
>
> Thanks to Krishna Lodha (rottengrapes.tech) for woking on this proposal
> with me.
>
> Our policy
> <https://docs.geoserver.org/latest/en/developer/policies/psc.html#> is to
> hold voting open for ten days (December 29 th), given that many people are
> occupied with the festive season I will keep this proposal open until
> January 3rd.
>
>
>- Alessio Fabiani
>- Andrea Aime
>- Ian Turton
>- Jody Garnett +1 initial motion
>- Jukka Rahkonen
>- Kevin Smith
>- Nuno Oliveira
>- Simone Giannecchini
>- Torben Barsballe
>
>
> Community support:
>
>
>- Krishna Lodha
>
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Platform independent binary is broken on main

[Ian Turton]

On Thu, 7 Dec 2023 at 15:07, Jody Garnett  wrote:

> I tested also, and determined that the only way to get that path was to
> start from the bin folder.
> However that is working for me, testing geoserver-main-latest-bin
> download. I added some notes to the ticket also.
>
> I am assuming URLChecks are being enabled by default on main.
>
> Ian do you have any more information about your setup?
>

I was indeed in `bin` to run `start.sh` - it's Java 17, Ubuntu 22.04 usual
terminal, only WPS module installed

Seems like calling `b.getCanonicalPath()` at some point would solve the
problem

I'm just not sure where

Ian

> --
> Jody Garnett
>
>
> On Dec 7, 2023 at 7:02:51 AM, Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Likely starting GeoServer form inside the "bin" folder?
>> It's something I never do.
>>
>> I've tried with a 2.24.1 I had handy and:
>>
>>- Starting as usual from the top, calling "bin/startup.sh", no
>>problem
>>- Getting into "bin" and starting from there... boom! From the logs:
>>
>> GEOSERVER DATA DIR is
>> /home/aaime/devel/gs_releases/geoserver-2.24.1/bin/../data_dir
>> ...
>>  Debugging information 
>> cause-exception : java.lang.IllegalArgumentException
>> cause-message   : Contains invalid '..' path:
>> /home/aaime/devel/gs_releases/geoserver-2.24.1/bin/../data_dir
>> class   : org.geoserver.catalog.impl.DataStoreInfoImpl
>> required-type   : org.geoserver.catalog.impl.DataStoreInfoImpl
>> converter-type  :
>> org.geoserver.config.util.XStreamPersister$StoreInfoConverter
>> line number : 17
>> version : 2.24.1
>> ---
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:81)
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:68)
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:52)
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:136)
>> at
>> com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
>> at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1464)
>>
>> Looking at the bin I have handy, 2.23.3 is still working fine, even with
>> URL checks enabled (enabled them and restarted).
>> GeoServer 2.24.0 also loads fine from bin, with a relative data dir.
>> But 2.24.1 does not so... check the differences between 2.24.0 and 2.24.1
>>
>> Cheers
>> Andrea
>>
>>
>> On Thu, Dec 7, 2023 at 1:00 PM Ian Turton  wrote:
>>
>>> I've just created https://osgeo-org.atlassian.net/browse/GEOS-11224 -
>>> basically you can't have `..` in the data directory path any longer, which
>>> we do by default, I'm guessing this is caused by one of the recent security
>>> fixes, does it ring a bell with anyone?
>>>
>>> Ian
>>>
>>> --
>>> Ian Turton
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards,
>>
>> Andrea Aime
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, 

[Geoserver-devel] Platform independent binary is broken on main

[Ian Turton]

I've just created https://osgeo-org.atlassian.net/browse/GEOS-11224 -
basically you can't have `..` in the data directory path any longer, which
we do by default, I'm guessing this is caused by one of the recent security
fixes, does it ring a bell with anyone?

Ian

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

Re: [Geoserver-devel] Motion: Github sponsorship of marlin-renderer repository

[Ian Turton]

+1

Ian

On Wed, 6 Dec 2023 at 17:26, Jody Garnett  wrote:

> I would like to make a motion to once again support marlin-renderer; an
> infrastructure project which directly benefits GeoServer's performance and
> competitiveness:
>
> Motion: Github $300 sponsorship of bourgesl/marlin-renderer
>> <https://github.com/bourgesl/marlin-renderer> repository on behalf of
>> GeoServer PSC
>>
>
> Reading https://github.com/sponsors/bourgesl it appears there is only one
> sponsor presently, although JetBrains has sponsored in the past.
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Motion: GISSA $500 donation to GISSA

[Ian Turton]

+1

Ian

On Wed, 6 Dec 2023 at 17:22, Jody Garnett  wrote:

> Following up on this week's meeting actions I would like to make the
> following motion:
>
> Make a $500 donation to Geo-Information Society of South Africa (
>> gi...@gissa.org.za) as an appropriate acknowledgement to the
>> contributions Peter Smythe has provided as a new member of our community in
>> 2023.
>>
>
> Peter has been wonderful in making releases this year, and enabling others
> to help out with improvements to the release instructions.
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Shall we enable JTS overlay NG by default?

[Ian Turton]

+1 from me

Ian

On Mon, 4 Dec 2023 at 17:51, Andrea Aime 
wrote:

> Hi,
> it's been discussed a bit in the past, but not actually done... shall we
> enable JTS overlay NG
> by default, unless there is an explicit setting for that property?
>
> Lately I've came across cases where the extra performance and stability
> are useful.
>
> Draft pull request here:
> https://github.com/geoserver/geoserver/pull/7311
>
> We could let this be on the main branch for a while, and it will
> eventually trickle down to stable and maintenance with the new releases.
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Should we add an extra Github action to rock a little the locale/timezone boat?

[Ian Turton]

On Fri, 1 Sept 2023 at 14:57, Andrea Aime 
wrote:

> Hi all,
> today I was trying to make a build and found the following failure:
>
> ---
> Test set: org.geoserver.wfs.response.CSVOutputFormatTest
> ---
> Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.464 s <<< 
> FAILURE! - in org.geoserver.wfs.response.CSVOutputFormatTest
> testDates(org.geoserver.wfs.response.CSVOutputFormatTest)  Time elapsed: 
> 0.019 s  <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[Sun, Ja]n 1, '17> but was:<[dom, ge]n 
> 1, '17>
> at 
> org.geoserver.wfs.response.CSVOutputFormatTest.assertDates(CSVOutputFormatTest.java:546)
> at 
> org.geoserver.wfs.response.CSVOutputFormatTest.testDates(CSVOutputFormatTest.java:526)
>
>
> It's due to a recent test that checks date formatting, without ensuring
> the expected locale is set.
> Now I'm wondering, should we have an extra build among the Github actions,
> that sets the system locale and maybe even the timezone to something
> "different", so that cases like this one would be found out before PR merge?
>
> Suggestions for the locale, timezone, and other possible settings to rock
> the boat a little bit?
>

I'd suggest a GMT+ and a GMT- zone for timezone testing, just based on
previous issues we've had. As for locales I'd guess anything non-english
should be a good test plus may be one with a non-ascii font like Korean,
Japanese or Arabic?

Ian

>
> Cheers
> Andrea
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] who has access to geoserver-docs.s3-website.eu-south-1.amazonaws.com?

[Ian Turton]

On Fri, 4 Aug 2023 at 14:16, Jody Garnett  wrote:

> We do not have access to that system which is why we move to osgeo hosting
> for stuff.
>
> Do you wish to add that jar to our website? Or upload to osgeo maven repo?
>

Either would work and then I can update the URL in the docs. I guess I can
push it to the web site most easily.

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

[Geoserver-devel] who has access to geoserver-docs.s3-website.eu-south-1.amazonaws.com?

[Ian Turton]

Currently the LDAP security tutorial points to a demo ldap system in a jar
that is stored at
http://geoserver-docs.s3-website.eu-south-1.amazonaws.com/acme-ldap-1.0.jar
- as a fix for https://osgeo-org.atlassian.net/browse/GEOS-11092 I've
rebuilt the jar to work with Java 11 but the build system doesn't seem to
actually build and deploy this jar so I'm assuming it is a manual copy.

So I have a new jar but I need some one to tell me how to deploy it or to
deploy it for me

Cheers

Ian

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

[Geoserver-devel] [JIRA] (GEOS-11092) acme-ldap.jar is compiled with Java 8

[Ian Turton (JIRA) via Geoserver-devel]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiODc2OTAzNmE1NmFmNGZmYjk0ZDgzMzEwMjM5MjJhYWQiLCJwIjoiaiJ9
 ) / Task ( 
https://osgeo-org.atlassian.net/browse/GEOS-11092?atlOrigin=eyJpIjoiODc2OTAzNmE1NmFmNGZmYjk0ZDgzMzEwMjM5MjJhYWQiLCJwIjoiaiJ9
 ) GEOS-11092 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11092?atlOrigin=eyJpIjoiODc2OTAzNmE1NmFmNGZmYjk0ZDgzMzEwMjM5MjJhYWQiLCJwIjoiaiJ9
 ) acme-ldap.jar is compiled with Java 8 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11092?atlOrigin=eyJpIjoiODc2OTAzNmE1NmFmNGZmYjk0ZDgzMzEwMjM5MjJhYWQiLCJwIjoiaiJ9
 )

Issue Type: Task Affects Versions: 2.23.2 Assignee: Unassigned Components: 
Documentation Created: 03/Aug/23 10:35 AM Priority: Medium Reporter: Ian Turton 
( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

If you try to work through the LDAP tutorial the acme-ldap.jar doesn’t work on 
a system with Java 11 but does still work with Java 8.

( 
https://osgeo-org.atlassian.net/browse/GEOS-11092#add-comment?atlOrigin=eyJpIjoiODc2OTAzNmE1NmFmNGZmYjk0ZDgzMzEwMjM5MjJhYWQiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11092#add-comment?atlOrigin=eyJpIjoiODc2OTAzNmE1NmFmNGZmYjk0ZDgzMzEwMjM5MjJhYWQiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100233- 
sha1:3ea1a2a )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-11083) anouncement script misses full URL for security issues

[Ian Turton (JIRA) via Geoserver-devel]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiYTQ4YTA3ZmU2ZTIxNDI0MTgwNGZhYjE1NjhlYmFkYWUiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-11083?atlOrigin=eyJpIjoiYTQ4YTA3ZmU2ZTIxNDI0MTgwNGZhYjE1NjhlYmFkYWUiLCJwIjoiaiJ9
 ) GEOS-11083 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11083?atlOrigin=eyJpIjoiYTQ4YTA3ZmU2ZTIxNDI0MTgwNGZhYjE1NjhlYmFkYWUiLCJwIjoiaiJ9
 ) anouncement script misses full URL for security issues ( 
https://osgeo-org.atlassian.net/browse/GEOS-11083?atlOrigin=eyJpIjoiYTQ4YTA3ZmU2ZTIxNDI0MTgwNGZhYjE1NjhlYmFkYWUiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.23.2 Assignee: Unassigned Components: 
website Created: 24/Jul/23 4:04 PM Priority: Medium Reporter: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

Security issues are left as relative links rather than correctly pointing to 
osgeo-org.atlassian…

( 
https://osgeo-org.atlassian.net/browse/GEOS-11083#add-comment?atlOrigin=eyJpIjoiYTQ4YTA3ZmU2ZTIxNDI0MTgwNGZhYjE1NjhlYmFkYWUiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11083#add-comment?atlOrigin=eyJpIjoiYTQ4YTA3ZmU2ZTIxNDI0MTgwNGZhYjE1NjhlYmFkYWUiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100232- 
sha1:a133497 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Release day 29.2, 1.23.2, 2.23.2

[Ian Turton]

I'm about to kick off the release train for GeoTools 29.2, GeoWebCache
1.23.2 and GeoServer 2.23.2 (Well Andrea is going to do the GWC release)

I'll start around 1pm UTC so if you have any last minute back ports you
want included in the releases now is your chance.

Ian

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

Re: [Geoserver-devel] GeoServer 2.23.2 release manager

[Ian Turton]

On Mon, 17 Jul 2023 at 17:07, Andrea Aime 
wrote:

> Hi all,
> the GeoServer 2.23.2 release is planned for tomorrow, but there is no
> release manager associated to it.
>
> I can offer to do it, but I won't be able to work on it until the first
> week of August.
> It's a bit late, I can see that, so if someone else can do it sooner, I'm
> happy to take
> on another release later.
>
>
I'd be happy to do it but I'd need someone to kick GWC out for me

Ian

> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] IAU module: it's mostly data, what to do?

[Ian Turton]

I think it can go in as an extension, it's really just more data.

Ian

On Wed, 12 Jul 2023, 17:25 Andrea Aime, 
wrote:

> Hi all,
> the IAU authority support module (for planetary CRS) in GeoTools is
> basically just packaging new data, and leveraging existing property CRS
> support, already used by gt-epsg-wtk and gt-espg-extension.
>
> Now it's time to package it for GeoServer. It will not have
> anything special for GeoServer, as it's just an extra database, it's a
> simple drop in: the zip file will only contain gt-iau-wkt.
>
> So the question is, where do I package it? Two points of view:
>
>- The database is new, thus community
>- The module is just data, the code is not new: extension
>
> What say you?
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-11057) CSS extension is missing asm jars

[Ian Turton (JIRA) via Geoserver-devel]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMTJkNjQ0Zjk4ZTUwNGU3M2E0MzJjMWYzYTEyZjMzOGMiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-11057?atlOrigin=eyJpIjoiMTJkNjQ0Zjk4ZTUwNGU3M2E0MzJjMWYzYTEyZjMzOGMiLCJwIjoiaiJ9
 ) GEOS-11057 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11057?atlOrigin=eyJpIjoiMTJkNjQ0Zjk4ZTUwNGU3M2E0MzJjMWYzYTEyZjMzOGMiLCJwIjoiaiJ9
 ) CSS extension is missing asm jars ( 
https://osgeo-org.atlassian.net/browse/GEOS-11057?atlOrigin=eyJpIjoiMTJkNjQ0Zjk4ZTUwNGU3M2E0MzJjMWYzYTEyZjMzOGMiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.23.1 Assignee: Unassigned Components: CSS 
Created: 06/Jul/23 11:30 AM Priority: Medium Reporter: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

If you add the CSS extension to GeoServer 2.23.1 it fails as the asm-*.jar 
files are missing from the zip file. Adding the missing jars from the 
2.23-nightly build corrects the problem.

I’m assuming there is something missing in the pom.xml that assembles the zip 
file.

( 
https://osgeo-org.atlassian.net/browse/GEOS-11057#add-comment?atlOrigin=eyJpIjoiMTJkNjQ0Zjk4ZTUwNGU3M2E0MzJjMWYzYTEyZjMzOGMiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11057#add-comment?atlOrigin=eyJpIjoiMTJkNjQ0Zjk4ZTUwNGU3M2E0MzJjMWYzYTEyZjMzOGMiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100230- 
sha1:e339e49 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Longitudinal profile WPS community module permission request

[Ian Turton]

What Jody said about input types, +1

Ian

On Wed, 28 Jun 2023, 11:29 Jody Garnett,  wrote:

> +1, although I do not understand ewkt, or why you would not just accept
> geometry and let WPS parse various formats (via already existing PPIO
> plugins)
>
> On Tue, Jun 27, 2023 at 5:53 PM Fernando Mino <
> fernando.m...@geosolutionsgroup.com> wrote:
>
>> Dear community,
>>
>> I would like to request permission to contribute a new community module
>> with name ```WPS longitudinal profile process```, which provides ability to
>> calculate elevation profile from a coverage layer matching a linestring on
>> top of it, returning the resulting coordinates set.  This process will use
>> the coverage layer elevation data to process and return the final profile.
>>
>> The WPS process will receive as input parameters:
>> 1. layerName - name of the raster layer (coverage) which will be used for
>> altitude profile creation
>> 2. linestringEwkt - linestring in EWKT format, along which the altitude
>> profile will be created
>> 3. distance - maximal distance between points of altitude profile
>>
>> The response contains following objects:
>> profile - contains array of points of the elevation profile
>> infos - general info on process result
>>
>> We will add request and response examples as part of the GeoServer
>> documentation section for this new module.
>>
>> Any feedback is welcome as well as your vote :)
>>
>> Thanks!
>>
>> Regards,
>>
>> Fernando Mino
>>
>> ==
>>
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>>
>> ==
>>
>> Fernando Mino
>>
>> Software Engineer
>>
>> @fmy2kec
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail.
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> --
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-11046) Styles using the custom mark `shape://dot` don't draw any fill

[Ian Turton (JIRA) via Geoserver-devel]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiN2NhODI2ZTVjMjllNGM4MmExM2Q2Njk0NzM4YWI2NDAiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-11046?atlOrigin=eyJpIjoiN2NhODI2ZTVjMjllNGM4MmExM2Q2Njk0NzM4YWI2NDAiLCJwIjoiaiJ9
 ) GEOS-11046 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11046?atlOrigin=eyJpIjoiN2NhODI2ZTVjMjllNGM4MmExM2Q2Njk0NzM4YWI2NDAiLCJwIjoiaiJ9
 ) Styles using the custom mark `shape://dot` don't draw any fill ( 
https://osgeo-org.atlassian.net/browse/GEOS-11046?atlOrigin=eyJpIjoiN2NhODI2ZTVjMjllNGM4MmExM2Q2Njk0NzM4YWI2NDAiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.22.2 Assignee: Unassigned Components: 
styling Created: 23/Jun/23 4:19 PM Priority: Medium Reporter: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

Using a style like:

@mode 'Auto' ;
@style Title 'Test' ;
@style Abstract 'Test' ;

/* @title Test

@abstract Test

*/
*{
  stroke: #a0a0f5 ;
  stroke- width : 1;
  fill: symbol( "shape: //dot" );
    :fill {
    size: 5;
    stroke: #a0a0f5 ;
    stroke- width : 1;
  fill: #a0a0f5 ;
    }
}

produces an unfilled Polygon

Log shows:

22 Jun 08:30:34 TRACE  [renderer.style] - fetching mark of name shape://dot
22 Jun 08:30:34 TRACE  [renderer.style] - Could not find the symbol, returning 
null
22 Jun 08:30:34 TRACE  [renderer.style] - fetching mark of name shape://dot
22 Jun 08:30:34 TRACE  [renderer.style] - applying stroke to mark

So it looks to be a renderer issue

( 
https://osgeo-org.atlassian.net/browse/GEOS-11046#add-comment?atlOrigin=eyJpIjoiN2NhODI2ZTVjMjllNGM4MmExM2Q2Njk0NzM4YWI2NDAiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11046#add-comment?atlOrigin=eyJpIjoiN2NhODI2ZTVjMjllNGM4MmExM2Q2Njk0NzM4YWI2NDAiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100227- 
sha1:d138f7b )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Backporting H2 classpath changes to GeoServer 2.23.x

[Ian Turton]

Seems reasonable to me. +1

Ian

On Mon, 5 Jun 2023 at 13:23, Andrea Aime 
wrote:

> Hi all,
> I'm writing to request a backport of the H2 removal from core modules.
>
> It amounts to removing a direct H2 dependency in GWC disk quota, and the
> same for KML superoverlay support, replacing the database using HSQL.
> In both cases, the database is not migrated, but rebuilt, as it only
> contains information that can be rebuilt from the data available (tiles and
> features).
>
> The pull requests involved are the following:
>
>- https://github.com/GeoWebCache/geowebcache/pull/1143 (GWC HSQL DB
>support, H2 dependency made optional)
>- https://github.com/geoserver/geoserver/pull/6867  (GS follow up with
>GWC GUI updates)
>- https://github.com/geoserver/geoserver/pull/6870 (KML superoverlays
>on HSQL)
>- https://github.com/geoserver/geoserver/pull/6879 (Make sure
>extensions/community modules needing H2
>
> The work was carried out so that transparent switch happens without any
> user intervention, but there is documentation for the one use case where
> some intervention is needed:
>
> https://docs.geoserver.org/latest/en/user/installation/upgrade.html#disk-quota-hsql-db-usage-geoserver-2-24-and-newer
>
> Opinions?
>
> Cheers
> Andrea
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] 2.23.1 artefacts ready for tests

[Ian Turton]

Thanks!

I couldn't tell if the warning was important or not

Ian

On Wed, 24 May 2023, 17:35 Andrea Aime, 
wrote:

> Hi Ian,
> noticed you fixed the posts, and the announcement still would not show
> up... turned out there is a new issue in github actions
> that we worked around (with Jody's help on where to make changes in the
> publishing workflow):
>
>
> https://github.com/geoserver/geoserver.github.io/commit/2c1960182828397d04ce669d63c6a9f0228c5291
>
> The announcement is now public.
>
> Cheers
> Andrea
>
> On Wed, May 24, 2023 at 12:51 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi Ian,
>> weird... I checked and noted the following:
>> - There are two blog posts for 2.23.1, with different dates, in the
>> sources:
>>
>> [image: image.png]
>>
>> Wondering if that might be causing some issue in the automations that
>> prepare the site for publishing?
>>
>> Cheers
>> Andrea
>>
>>
>> On Wed, May 24, 2023 at 12:06 PM Ian Turton  wrote:
>>
>>> For some reason the web page update and blog aren't showing up (even
>>> with cache disabled) and I need to create a GeoTools blog post.
>>>
>>> Ian
>>>
>>> On Wed, 24 May 2023 at 10:33, Andrea Aime <
>>> andrea.a...@geosolutionsgroup.com> wrote:
>>>
>>>> Oh, never mind, I see the release publish job has run yesterday,
>>>> successfully, without changes:
>>>>
>>>> https://build.geoserver.org/view/release/job/geoserver-release-publish/69/console
>>>>
>>>> So I guess all that's missing are the announcements
>>>>
>>>> Cheers
>>>> Andrea
>>>>
>>>> On Wed, May 24, 2023 at 10:53 AM Andrea Aime <
>>>> andrea.a...@geosolutionsgroup.com> wrote:
>>>>
>>>>> Hi Ian,
>>>>> I gave a quick spin at the base package, checking map previews, WFS
>>>>> output formats,
>>>>> a bunch of admin UI panels, everything I looked at seems to be
>>>>> working properly.
>>>>>
>>>>> About the release job, we talked about it quickly yesterday, SF does
>>>>> not seem to be very collaborative,
>>>>> we should try the new upload path. Torben suggested to take the
>>>>> release_publish.sh script add
>>>>> use it inline in the maven job, as a way to quickly test out different
>>>>> alternatives (see also the meeting notes).
>>>>> Once you know what works, fixing the script should be quick.
>>>>>
>>>>> Cheers
>>>>> Andrea
>>>>>
>>>>>
>>>>> On Mon, May 22, 2023 at 5:16 PM Ian Turton  wrote:
>>>>>
>>>>>>
>>>>>> https://build.geoserver.org/view/release/job/geoserver-release/121/artifact/distribution/2.23.1/
>>>>>>
>>>>>> After a bit of a fight I have made GeoServer's release run, so please
>>>>>> let me know if it's working for you
>>>>>>
>>>>>> Ian
>>>>>>
>>>>>> --
>>>>>> Ian Turton
>>>>>> ___
>>>>>> Geoserver-devel mailing list
>>>>>> Geoserver-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards,
>>>>>
>>>>> Andrea Aime
>>>>>
>>>>> ==
>>>>> GeoServer Professional Services from the experts!
>>>>>
>>>>> Visit http://bit.ly/gs-services-us for more information.
>>>>> ==
>>>>>
>>>>> Ing. Andrea Aime
>>>>> @geowolf
>>>>> Technical Lead
>>>>>
>>>>> GeoSolutions Group
>>>>> phone: +39 0584 962313
>>>>>
>>>>> fax: +39 0584 1660272
>>>>>
>>>>> mob:   +39  339 8844549
>>>>>
>>>>> https://www.geosolutionsgroup.com/
>>>>>
>>>>> http://twitter.com/geosolutions_it
>>>>>
>>>>> ---
>>>>>
>>>>> Con riferimento alla normativa sul trattamento dei dati personali
>>>>> (Reg. UE 2016/67

Re: [Geoserver-devel] 2.23.1 artefacts ready for tests

[Ian Turton]

For some reason the web page update and blog aren't showing up (even with
cache disabled) and I need to create a GeoTools blog post.

Ian

On Wed, 24 May 2023 at 10:33, Andrea Aime 
wrote:

> Oh, never mind, I see the release publish job has run yesterday,
> successfully, without changes:
>
> https://build.geoserver.org/view/release/job/geoserver-release-publish/69/console
>
> So I guess all that's missing are the announcements
>
> Cheers
> Andrea
>
> On Wed, May 24, 2023 at 10:53 AM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi Ian,
>> I gave a quick spin at the base package, checking map previews, WFS
>> output formats,
>> a bunch of admin UI panels, everything I looked at seems to be
>> working properly.
>>
>> About the release job, we talked about it quickly yesterday, SF does not
>> seem to be very collaborative,
>> we should try the new upload path. Torben suggested to take the
>> release_publish.sh script add
>> use it inline in the maven job, as a way to quickly test out different
>> alternatives (see also the meeting notes).
>> Once you know what works, fixing the script should be quick.
>>
>> Cheers
>> Andrea
>>
>>
>> On Mon, May 22, 2023 at 5:16 PM Ian Turton  wrote:
>>
>>>
>>> https://build.geoserver.org/view/release/job/geoserver-release/121/artifact/distribution/2.23.1/
>>>
>>> After a bit of a fight I have made GeoServer's release run, so please
>>> let me know if it's working for you
>>>
>>> Ian
>>>
>>> --
>>> Ian Turton
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards,
>>
>> Andrea Aime
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>


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

[Geoserver-devel] 2.23.1 artefacts ready for tests

[Ian Turton]

https://build.geoserver.org/view/release/job/geoserver-release/121/artifact/distribution/2.23.1/

After a bit of a fight I have made GeoServer's release run, so please let
me know if it's working for you

Ian

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

[Geoserver-devel] 2.23.1 and 29.1 releases train will start this friday

[Ian Turton]

If you have any fixes that you want included in the upcoming 2.23.1
GeoServer or 29.1 GeoTools releases please make sure you have backported
them and updated the fix version in the ticket before Friday morning (UTC)
which is when I plan to start the release cycle.

Ian

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

Re: [Geoserver-devel] Volunteer for 2.23.1 release?

[Ian Turton]

On Wed, 17 May 2023 at 16:41, Andrea Aime 
wrote:

> Hi all,
> tomorrow we were supposed to have the 2.23.1 release, but I see there
> is no volunteer marked for it.
>
> Do we have any candidate? Of course it does not have to be tomorrow,
> pick your preference :D
>

I can probably do it on Friday (unless the Giro is in the Alps :-)) unless
anyone is in a hurry to get it out tomorrow

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

Re: [Geoserver-devel] Chipping away at H2 v 1.x dependencies

[Ian Turton]

On Mon, 15 May 2023, 18:31 Jody Garnett,  wrote:

> Ian:
>
> The remove opengis funding is set-up as a cross project thing (not
> specifically allocated to a project budget). That said if it does not meet
> its funding target; or if we cannot attract participants even with money
> there is no obligation to proceed.
>
> I know my own employer does not see the value (so I will not be working on
> the activity even with funding...). I may still help out as a volunteer; if
> only so Andrea can enjoy life.
>

I'm currently negotiating taking 2 weeks leave for the Bolsena sprint, so
if we're not going ahead that please let me know sooner rather than later,
so I can plan to take Lesley somewhere sunny instead.

Ian


--
> Jody Garnett
>
>
> On Mon, May 15, 2023 at 4:03 AM Ian Turton  wrote:
>
>>
>>
>> On Mon, 15 May 2023 at 11:32, Andrea Aime <
>> andrea.a...@geosolutionsgroup.com> wrote:
>>
>>> Hi all,
>>> as you probably know, GeoServer has a core dependency on H2 database
>>> version 1.1.119.
>>> This is slowly becoming troublesome for a few reasons:
>>>
>>>- The 1.x series of H2 is abandoned
>>>- It's accumulating CVEs, while none of them seems to be affecting
>>>our current usage, they still show up in all dependencies reports
>>>
>>> So it would be a good idea to upgrade. H2 version 2 is supported, but it
>>> poses serious upgrade problems: the format of the database changed, and H2
>>> has no compatibility with 1.x databases. The only way to upgrade is to dump
>>> SQL using the older version, and then restore with the newer one.
>>> In addition, H2 retained the same package names, meaning we cannot have
>>> both in the same classpath (unless we use shading).
>>> To make things worse, H2 1.x did not have spatial data types, so we have
>>> WKB stored in the database as binary columns, with spatial indexing
>>> provided by extra libraries that also happen to be dead (hatbox, geodb).
>>>
>>> In GeoSolutions we have been trying to organize an upgrade for a while,
>>> but it turns out it's too much work to be done in one shot (clear funding
>>> issue).
>>>
>>> However, there is an easier path... chipping away at it a few
>>> dependencies at a time. Turns out some of the dependencies towards H2 are
>>> core, and others are in plugins. The one that really need a spatial
>>> database are just in plugins, while the core dependencies need only an
>>> alphanumeric database:
>>>
>>>- GWC disk quota mechanism
>>>- KML superoverlay support (is anyone still using it? 
>>>
>>> In both cases the databases collect caches of information that can be
>>> rebuilt automatically by GeoServer as needed, so no actual migration
>>> procedure is needed: we can drop the old database, and start over with a
>>> new one.
>>>
>>> Disk quota over H2 is not recommended for production environments, but
>>> still, to keep our "ease of use" story going, having an embedded database
>>> would be a good thing.
>>>
>>> So what we propose is easy: for these two use cases we switch the
>>> embedded database usage to HSQL, which has been modestly, but steadily,
>>> serving our CRS database needs for years, without causing trouble. It's
>>> already in our classpath, it has been used for a long time, it's pure java,
>>> and it's small (1.6MB).
>>>
>>> Alternatives considered and discarded for the task at hand:
>>>
>>>- Sqlite/Geopackage: the sqlite jdbc library is a beast (12.2 MB and
>>>growing) and not part of the GWC dependencies.
>>>- H2 v 2.x, because it would mean shading it and right now we'd have
>>>to either shade all other usages of 1.x (can't cover that) or shade 2.x
>>>(which is the opposite of the direction we're going)
>>>
>>> Removing the need for H2 In the core will also allow the possibility of
>>> running GeoServer along with the H2GIS data store (that already depends on
>>> H2 v 2.x). The other places where we need an embedded spatial database may
>>> be covered, in time, by GeoPackage, until we can wave goodbye to the last
>>> usage of H2 v 1.x, but they will be doable one by one and at their own
>>> pace: GeoFence, NetCDF store.
>>>
>>> Other non spatial cases that are in plugins, which might be migrated
>>> later to either GeoPackage or HSQLDB, are wps-jdbc  and importer-jdbc (both
>>> depending on the DataStore interface) a

Re: [Geoserver-devel] Chipping away at H2 v 1.x dependencies

[Ian Turton]

49
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GSIP 219: Multiple CRS authority support, planetary CRS

[Ian Turton]

I assume that some/much of this work will be in the GeoTools tree?

As for how to package this on the one hand I like the simplicity of a new
extension, it's easy for users to understand and provides a good way to
keep track of versions, on the other hand it's easy to forget to add it on
upgrade and break all your layers. Just thinking aloud here, how much
effort would it be to get the existing authority discovery code (or are
they hard coded) to "discover" new authorities by looking in a "well known"
location?

Anyway +1 for the general plan, looking forward to seeing the details

Ian

On Wed, 3 May 2023 at 11:14, Andrea Aime 
wrote:

> Hi all,
> the following proposal aims to add support for authorities other than EPSG
> in selected parts of GeoServer, and provide a working example based on the
> IAU authority (planetary CRSs).
>
> https://github.com/geoserver/geoserver/wiki/GSIP-219
>
> Key points:
>
>- It's not trying to address all places where EPSG authority
>assumptions are made, but provides a specific list instead. Other cases can
>be handled later as bug fixes, as funding comes to fix those as well.
>- Discusses a couple of way to plug in other authorities (can you
>suggest more/better ones?).
>
> Feedbacks/votes welcomed!
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] Security Score Cards?

[Ian Turton]

I've just read this article on assessing security risks -
https://opensource.com/article/23/3/open-source-security-scorecard - Might
be worth implementing as a git action for us.

Any thoughts?

Ian

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

Re: [Geoserver-devel] Time to drop the Marlin renderer dependency?

[Ian Turton]

Is that small backwards step important? If it was down to me I'd drop the
windows installer (and support) but I guess anything that makes windows
users lives easier is a good thing.

IAn

On Mon, 3 Apr 2023 at 08:43, Andrea Aime 
wrote:

> On Mon, Apr 3, 2023 at 9:40 AM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Of all the approaches, removing one dependency seems like the easiest
>> solution. According to this table
>> <https://github.com/bourgesl/marlin-renderer#release-history>, Java 11
>> contains a slightly newer version of Marlin
>>
>
> Whoops, I misread the table... contains a slightly  older version, 0.9.1
> in JDK vs 0.9.3 in our pom.xml
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] Versions of the documentation?

[Ian Turton]

Something seems amiss with our documentation releases on the web site -

latest -> 2.24.x
Stable -> 2.23.x
Maintenance -> 2.20.x

While the download page is saying

dev (latest?) -> 2.23.x
stable -> 2.22.2
maintenance -> 2.21.4

This leads to issues with (for example) the docker page (
https://docs.geoserver.org/latest/en/user/installation/docker.html)
pointing to a version which doesn't exist.

Is there a different config for the manual pages that isn't being updated
correctly? compared to the download pages?

Ian


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

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

[Ian Turton]

+1

On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, 
wrote:

> Hi all,
>
> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a
> new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
> /geoserver Github organization.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
> details, comment back and vote.
>
> Best regards,
> Gabriel.
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-216 GeoFence 4.0.x

[Ian Turton]

+1

Looks like a good plan to me

Ian

On Wed, 8 Mar 2023 at 02:34, Gabriel Roldan 
wrote:

> Hi list,
>
> I've just created a GSIP (216) with a proposal to make several
> improvements to GeoFence.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-216 for
> details.
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldán*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] GeoServer.org web site seems to have gone missing

[Ian Turton]

Is this related to today's releases? Is some one looking at it or should I
have a go?

Ian

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

Re: [Geoserver-devel] [JIRA] (GEOS-10840) 2.22.1 Maven and release artifacts pushed with SNAPSHOT dependencies

[Ian Turton]

No, there were no changes to GWC since 1.21.3 so we decided not to make a
new build of GWC

Ian

On Mon, 30 Jan 2023 at 14:55, Jody Garnett  wrote:

> Checking https://github.com/geoserver/geoserver/blob/2.22.1/src/pom.xml
>
> It has 1.21.3
>
> Should this be 1.22.0
> <https://github.com/GeoWebCache/geowebcache/blob/1.22.0/geowebcache/pom.xml>
>  ?
> --
> Jody Garnett
>
>
> On Fri, Jan 27, 2023 at 1:14 PM Ian Turton  wrote:
>
>> My fault, I knew I shouldn't mess with the settings with out reading the
>> source code :-(
>>
>> I'll run it again.
>>
>> Ian
>>
>> On Fri, 27 Jan 2023 at 12:11, Jody Garnett 
>> wrote:
>>
>>> I am glad we have an answer.
>>> Personally I understood those parameters only did a build when a
>>> revision was supplied; if an actual release tag is used no building is
>>> required?
>>>
>>> I understand that these were used to issue an emergency hotfix in the
>>> past. Now we tend to just make another geotools release if a critical fix
>>> is required.
>>>
>>> Perhaps these options could be removed?
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Fri, Jan 27, 2023 at 12:32 PM Andrea Aime <
>>> andrea.a...@geosolutionsgroup.com> wrote:
>>>
>>>> Hi, I've spent some time investigating what happened, I believe it's
>>>> user error caused by confusing parameters and a bug in the release 
>>>> script...
>>>> The build has these two parameters, that I normally don't touch, set to
>>>> "skip":
>>>>
>>>> [image: image.png]
>>>> I normally don't touch them due to lack of understanding, but the
>>>> description seems to suggest "skip GT build", which is indeed
>>>> something we don't need during a release, the upstream builds are done
>>>> already.
>>>> But looking at how they work in build_release.sh
>>>> <https://github.com/geoserver/geoserver/blob/main/build/build_release.sh#L156>,
>>>> they skip the build but also skip setting gt_tag and gwc_tag,
>>>> which then are used to update the version numbers in the pom files
>>>> <https://github.com/geoserver/geoserver/blob/main/build/build_release.sh#L199>
>>>> .
>>>>
>>>> Seems like a bug in the logic of the release script IMHO, but for now,
>>>> better not set those to "skip" and let them do the extra,
>>>> unnecessary builds.
>>>>
>>>> Cheers
>>>> Andrea
>>>>
>>>> ___
>>>> Geoserver-devel mailing list
>>>> Geoserver-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>> Ian Turton
>>
>

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

Re: [Geoserver-devel] [JIRA] (GEOS-10840) 2.22.1 Maven and release artifacts pushed with SNAPSHOT dependencies

[Ian Turton]

My fault, I knew I shouldn't mess with the settings with out reading the
source code :-(

I'll run it again.

Ian

On Fri, 27 Jan 2023 at 12:11, Jody Garnett  wrote:

> I am glad we have an answer.
> Personally I understood those parameters only did a build when a revision
> was supplied; if an actual release tag is used no building is required?
>
> I understand that these were used to issue an emergency hotfix in the
> past. Now we tend to just make another geotools release if a critical fix
> is required.
>
> Perhaps these options could be removed?
> --
> Jody Garnett
>
>
> On Fri, Jan 27, 2023 at 12:32 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi, I've spent some time investigating what happened, I believe it's user
>> error caused by confusing parameters and a bug in the release script...
>> The build has these two parameters, that I normally don't touch, set to
>> "skip":
>>
>> [image: image.png]
>> I normally don't touch them due to lack of understanding, but the
>> description seems to suggest "skip GT build", which is indeed
>> something we don't need during a release, the upstream builds are done
>> already.
>> But looking at how they work in build_release.sh
>> <https://github.com/geoserver/geoserver/blob/main/build/build_release.sh#L156>,
>> they skip the build but also skip setting gt_tag and gwc_tag,
>> which then are used to update the version numbers in the pom files
>> <https://github.com/geoserver/geoserver/blob/main/build/build_release.sh#L199>
>> .
>>
>> Seems like a bug in the logic of the release script IMHO, but for now,
>> better not set those to "skip" and let them do the extra,
>> unnecessary builds.
>>
>> Cheers
>> Andrea
>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] 2.21.1 - release artefacts available for testing now

[Ian Turton]

Please grab
https://build.geoserver.org/view/release/job/geoserver-release/95/artifact/distribution/2.22.1/
and test especially if you are on windows or a Mac

Cheers

Ian

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

[Geoserver-devel] 2.22.1 /1.22.1/28.1 Release train is starting

[Ian Turton]

Heads up, I'm going to kick off the 28.1 release of GeoTools this morning,
depending on how this goes Andrea will do GWC 1.22.1 (assuming there have
been changes) and then I will probably finish up GeoServer tomorrow morning.

Ian

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

Re: [Geoserver-devel] GeoServer 2.22.1 release volunteer needed

[Ian Turton]

Will do, thanks!

On Tue, 17 Jan 2023 at 14:25, Andrea Aime 
wrote:

> Hey thanks a lot Ian! I can help with GWC, throw me a note when ready.
>
> Cheers
> Andrea
>
> On Mon, Jan 16, 2023 at 7:51 PM Ian Turton  wrote:
>
>> I can do it if someone can help with GWC
>>
>> Ian
>>
>> On Mon, 16 Jan 2023, 16:04 Andrea Aime, <
>> andrea.a...@geosolutionsgroup.com> wrote:
>>
>>> Hi all,
>>> in theory we should be releasing 2.22.1 the 18th (in two days). But
>>> looking at the release page
>>> <https://github.com/geoserver/geoserver/wiki/Release-Schedule#volunteer-coordination>,
>>> we don't have a volunteer. Any takers?
>>>
>>> Cheers
>>> Andrea
>>>
>>> ==
>>> GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions Group
>>> phone: +39 0584 962313
>>>
>>> fax: +39 0584 1660272
>>>
>>> mob:   +39  339 8844549
>>>
>>> https://www.geosolutionsgroup.com/
>>>
>>> http://twitter.com/geosolutions_it
>>>
>>> ---
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>


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

Re: [Geoserver-devel] GeoServer 2.22.1 release volunteer needed

[Ian Turton]

I can do it if someone can help with GWC

Ian

On Mon, 16 Jan 2023, 16:04 Andrea Aime, 
wrote:

> Hi all,
> in theory we should be releasing 2.22.1 the 18th (in two days). But
> looking at the release page
> ,
> we don't have a volunteer. Any takers?
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-10825) Importer doesn't provide a way to set SSL on/off etc in postgis connection

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiM2I5ZmFmZGU0M2RmNDg3NzgzYTgzNmMwNGJiZDhlYzciLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10825?atlOrigin=eyJpIjoiM2I5ZmFmZGU0M2RmNDg3NzgzYTgzNmMwNGJiZDhlYzciLCJwIjoiaiJ9
 ) GEOS-10825 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10825?atlOrigin=eyJpIjoiM2I5ZmFmZGU0M2RmNDg3NzgzYTgzNmMwNGJiZDhlYzciLCJwIjoiaiJ9
 ) Importer doesn't provide a way to set SSL on/off etc in postgis connection ( 
https://osgeo-org.atlassian.net/browse/GEOS-10825?atlOrigin=eyJpIjoiM2I5ZmFmZGU0M2RmNDg3NzgzYTgzNmMwNGJiZDhlYzciLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.21.0, 2.22.0 Assignee: Unassigned 
Components: Importer Created: 13/Jan/23 3:59 PM Priority: Medium Reporter: Ian 
Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

If you have set up your postgis db to require SSL connections then you can’t 
use the importer extension to import data as it is not possible to change the 
SSL connection setting as it is with the normal PostGIS datastore.

Workaround - allow insecure logins to the database.

( 
https://osgeo-org.atlassian.net/browse/GEOS-10825#add-comment?atlOrigin=eyJpIjoiM2I5ZmFmZGU0M2RmNDg3NzgzYTgzNmMwNGJiZDhlYzciLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10825#add-comment?atlOrigin=eyJpIjoiM2I5ZmFmZGU0M2RmNDg3NzgzYTgzNmMwNGJiZDhlYzciLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- 
sha1:b03f6a4 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geowebcache-devel] osgeo budget request

[Ian Turton]

+0 on the org.opengis - I might have capacity to do that work later this
year but I can think of better things to do with the money.

+1 on the security issues fund (might be able to tap the EU for funds for
that)

Ian

On Wed, 4 Jan 2023 at 20:06, Jody Garnett  wrote:

> Good morning folks,
>
> OSGeo board put out their call for budget request; separately they have
> "todo" ticket for removing the org.opengis
> <https://git.osgeo.org/gitea/osgeo/todo/issues/142> package from the
> GeoTools codebase. And it is on the agenda for the next board meeting
> <https://wiki.osgeo.org/wiki/Board_Meeting_2023-01-30>.
>
> I have provided a technical debt wiki page on refactoring org.opengis
> packages (reversing the work we did to provide the interfaces to start the
> project) in order to get an idea on the work required and costs involved:
> https://github.com/geotools/geotools/wiki/Remove-OpenGIS
>
> Since this change provides no value to the geotools codebase I have no
> real interest in fundraising for the activity. I would expect a similar
> effort to the Java 11 split-package refactoring where the work can be done,
> and a script created and tested against downstream GeoWebCache and
> GeoServer codebases.
>
> For that activity sponsorship raised around $5k for a cross-project
> sprint. The in-kind contributions were 10-25k (staff time / travel / venue
> / fundraising).
>
> I am going to recommend putting in a budget request of 10k for geotools,
> and 5k for geowebcache, and 5k for geoserver to cover a similar
> undertaking. If successful we will still need to ask for in-kind
> participation for individuals and organizations (even if just to cover
> their risk).
>
> I do not think we have a meeting before their budget deadline; so if I can
> get a few +1 replies to this email I will make the request on our behalf.
>
> Also after last year I am going to separately suggest an OSGeo budget for
> "security issues" (as a cross project initiative similar to code sprints).
> Because 2022 sucked.
> --
> Jody Garnett
> ___
> Geowebcache-devel mailing list
> geowebcache-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geowebcache-devel
>


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

Re: [Geoserver-devel] Proposing Joseph Miller for commit rights

[Ian Turton]

+1

Ian

On Mon, 28 Nov 2022 at 17:23, Andrea Aime 
wrote:

> Hi all,
> Joseph has been working on a number of PRs lately, on a variety of
> different topics (request logging, database column descriptions, STAC,
> GetFeature output format control, and more, see also the proposal I'm
> making on the gt-devel side).
> He has patiently been applying all review feedback received.
>
> I'd like to propose Joseph for commit rights on the GeoServer project.
>
> What do you think?
>
> Cheers
> Andrea
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Release train starting for 2.21.x

[Ian Turton]

On Sat, 22 Oct 2022, 17:23 Jody Garnett,  wrote:

> We do not have a ticket for it (since we were not affected).
>

Well we do have a ticket, it just doesn't mention the cve. I've answered
one question on the security list and one on gis.se so people seem
worried about it.



> I think I am against reporting CVEs from dependencies where our software
> is not affected. It just adds "noise". I would prefer when we have a
> security vulnerability section that everyone take it seriously and
> upgrade
>
> What do you think?
>

Since we do use the effected jar it is probably worth mentioning in the
release notes.

Ian

>
> Jody
>
> On Sat, Oct 22, 2022 at 3:01 AM Ian Turton  wrote:
>
>> Do we want to mention the CVE-2022-42889
>> <https://nvd.nist.gov/vuln/detail/CVE-2022-42889> vulnerability, that
>> doesn't actually affect us and is now patched anyway?
>>
>> Ian
>>
>> On Sat, 22 Oct 2022 at 04:52, Jody Garnett 
>> wrote:
>>
>>> Here is draft blog post while we wait for build process:
>>> https://github.com/geoserver/geoserver.github.io/pull/135
>>>
>>> Okay, gather the bits for release:
>>>
>>>- Security hiding layer groups:
>>>https://github.com/geoserver/geoserver/pull/6290 (done)
>>>- Windows installer needs assembly changes backport
>>>https://github.com/geoserver/geoserver/pull/6291 (done)
>>>   - aside: Noticed many of the assembles try and gather
>>>   src/release/RELEASE_NOTES.txt
>>>   
>>> <https://github.com/geoserver/geoserver/blob/2.13.x/src/release/RELEASE_NOTES.txt>
>>>   ... which has not been present since 2.13.x
>>>- Did a round up of other backports, we should be good ...
>>>
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Thu, 20 Oct 2022 at 07:17, Jody Garnett 
>>> wrote:
>>>
>>>> With the RC out of the way; I still have some customers waiting on a
>>>> stable release for security improvements.
>>>>
>>>> Is it okay if I make a 2.21.x release? That way we still get a stable
>>>> release for October here.
>>>>
>>>> Jody
>>>> --
>>>> --
>>>> Jody Garnett
>>>>
>>> ___
>>
>>
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>> Ian Turton
>>
> --
> --
> Jody Garnett
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Release train starting for 2.21.x

[Ian Turton]

Do we want to mention the CVE-2022-42889
<https://nvd.nist.gov/vuln/detail/CVE-2022-42889> vulnerability, that
doesn't actually affect us and is now patched anyway?

Ian

On Sat, 22 Oct 2022 at 04:52, Jody Garnett  wrote:

> Here is draft blog post while we wait for build process:
> https://github.com/geoserver/geoserver.github.io/pull/135
>
> Okay, gather the bits for release:
>
>- Security hiding layer groups:
>https://github.com/geoserver/geoserver/pull/6290 (done)
>- Windows installer needs assembly changes backport
>https://github.com/geoserver/geoserver/pull/6291 (done)
>   - aside: Noticed many of the assembles try and gather
>   src/release/RELEASE_NOTES.txt
>   
> <https://github.com/geoserver/geoserver/blob/2.13.x/src/release/RELEASE_NOTES.txt>
>   ... which has not been present since 2.13.x
>- Did a round up of other backports, we should be good ...
>
> --
> Jody Garnett
>
>
> On Thu, 20 Oct 2022 at 07:17, Jody Garnett  wrote:
>
>> With the RC out of the way; I still have some customers waiting on a
>> stable release for security improvements.
>>
>> Is it okay if I make a 2.21.x release? That way we still get a stable
>> release for October here.
>>
>> Jody
>> --
>> --
>> Jody Garnett
>>
> _______
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Release train starting for 2.21.x

[Ian Turton]

+1 from me

Ian

On Thu, 20 Oct 2022 at 15:19, Jody Garnett  wrote:

> With the RC out of the way; I still have some customers waiting on a
> stable release for security improvements.
>
> Is it okay if I make a 2.21.x release? That way we still get a stable
> release for October here.
>
> Jody
> --
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Default logging profiles are not longer customizable

[Ian Turton]

Overwriting an existing file seems wrong to me. I for one would be
surprised if it happened to me.

Ian

On Fri, 7 Oct 2022, 18:20 Andrea Aime, 
wrote:

> Hi all,
> I'm bringing a discussion started in
> https://osgeo-org.atlassian.net/browse/GEOS-10700 here on list, because I
> believe it needs a wider audience.
>
> In summary, it's no longer possible to customize the logging profiles that
> ship with GeoServer (e..g, PRODUCTION_LOGGING.xml, as found in a
> vanilla GeoServer installation) because GeoServer would overwrite them on
> startup with the classpath version.
>
> The "intended" way would be to create a customized profile,
> "MY_PRODUCTION_LOGGING", that would sit alongside the one provided by
> GeoServer.
>
> Jody says it's a feature... I see it as surprising, and verbose
> configuration wise (why should one keep logging profiles they don't care to
> use as-is, and put another alongside with the same intended purpose?).
>
> Can we please restore the old behavior? If the admin customizes a built-in
> profile in XML form, it just stays that way. GeoServer should fill back in
> the logging profiles only if they have been deleted...
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] HTTPS certificate has expired for maven.geo-solutions.it

[Ian Turton]

On Mon, 3 Oct 2022 at 14:56, Jody Garnett  wrote:

> Can we please remove this repo from our build; it is already cached from
> osgeo repo. Listing multiple repositories just slows us down ...
>
>
We always welcome PRs for changes to the build process :-)

Ian

> --
> Jody Garnett
>
>
> On Mon, 3 Oct 2022 at 00:40, Alessandro Parma <
> alessandro.pa...@geosolutionsgroup.com> wrote:
>
>> Good Morning Ian,
>>
>> I'll take a look and fix it. Thanks for the heads up
>>
>> Regards,
>> Alessandro
>>
>> On Mon, Oct 3, 2022 at 9:30 AM Ian Turton  wrote:
>>
>>> I'm getting build failures on Github due to the certificate being
>>> expired.
>>>
>>> curl  "
>>> https://maven.geo-solutions.it/net/sf/json-lib/json-lib/2.4.2-geoserver/json-lib-2.4.2-geoserver.pom;
>>>
>>> curl: (60) SSL certificate problem: certificate has expired
>>> More details here: https://curl.haxx.se/docs/sslcerts.html
>>>
>>> curl failed to verify the legitimacy of the server and therefore could
>>> not
>>> establish a secure connection to it. To learn more about this situation
>>> and
>>> how to fix it, please visit the web page mentioned above.
>>>
>>> If someone can fix it I'd be grateful,
>>>
>>> cheers
>>>
>>> Ian
>>>
>>> --
>>> Ian Turton
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards, Alessandro Parma == GeoServer Professional Services from the
>> experts! Visit http://goo.gl/it488V for more information. == Alessandro
>> Parma DevOps Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054
>> Massarosa (LU) Italy phone: +39 340 4752467 fax: +39 0584 1660272
>> https://www.geosolutionsgroup.com https://twitter.com/geosolutions_it
>> --- Con riferimento
>> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
>> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
>> circostanza inerente alla presente email (il suo contenuto, gli eventuali
>> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
>> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
>> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
>> sarei comunque grato se potesse darmene notizia. This email is intended
>> only for the person or entity to which it is addressed and may contain
>> information that is privileged, confidential or otherwise protected from
>> disclosure. We remind that - as provided by European Regulation 2016/679
>> “GDPR” - copying, dissemination or use of this e-mail or the information
>> herein by anyone other than the intended recipient is prohibited. If you
>> have received this email by mistake, please notify us immediately by
>> telephone or e-mail.
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

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

Re: [Geoserver-devel] HTTPS certificate has expired for maven.geo-solutions.it

[Ian Turton]

Great, thanks!

All seems to be working now

Ian

On Mon, 3 Oct 2022 at 08:41, Alessandro Parma <
alessandro.pa...@geosolutionsgroup.com> wrote:

> It's fixed now
>
> Regards,
> Alessandro
>
>
>
> On Mon, Oct 3, 2022 at 9:32 AM Alessandro Parma <
> alessandro.pa...@geosolutionsgroup.com> wrote:
>
>> Good Morning Ian,
>>
>> I'll take a look and fix it. Thanks for the heads up
>>
>> Regards,
>> Alessandro
>>
>> On Mon, Oct 3, 2022 at 9:30 AM Ian Turton  wrote:
>>
>>> I'm getting build failures on Github due to the certificate being
>>> expired.
>>>
>>> curl  "
>>> https://maven.geo-solutions.it/net/sf/json-lib/json-lib/2.4.2-geoserver/json-lib-2.4.2-geoserver.pom;
>>>
>>> curl: (60) SSL certificate problem: certificate has expired
>>> More details here: https://curl.haxx.se/docs/sslcerts.html
>>>
>>> curl failed to verify the legitimacy of the server and therefore could
>>> not
>>> establish a secure connection to it. To learn more about this situation
>>> and
>>> how to fix it, please visit the web page mentioned above.
>>>
>>> If someone can fix it I'd be grateful,
>>>
>>> cheers
>>>
>>> Ian
>>>
>>> --
>>> Ian Turton
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards, Alessandro Parma == GeoServer Professional Services from the
>> experts! Visit http://goo.gl/it488V for more information. == Alessandro
>> Parma DevOps Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054
>> Massarosa (LU) Italy phone: +39 340 4752467 fax: +39 0584 1660272
>> https://www.geosolutionsgroup.com https://twitter.com/geosolutions_it
>> --- Con riferimento
>> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
>> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
>> circostanza inerente alla presente email (il suo contenuto, gli eventuali
>> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
>> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
>> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
>> sarei comunque grato se potesse darmene notizia. This email is intended
>> only for the person or entity to which it is addressed and may contain
>> information that is privileged, confidential or otherwise protected from
>> disclosure. We remind that - as provided by European Regulation 2016/679
>> “GDPR” - copying, dissemination or use of this e-mail or the information
>> herein by anyone other than the intended recipient is prohibited. If you
>> have received this email by mistake, please notify us immediately by
>> telephone or e-mail.
>>
>
>
> --
>
> Regards, Alessandro Parma == GeoServer Professional Services from the
> experts! Visit http://goo.gl/it488V for more information. == Alessandro
> Parma DevOps Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054
> Massarosa (LU) Italy phone: +39 340 4752467 fax: +39 0584 1660272
> https://www.geosolutionsgroup.com https://twitter.com/geosolutions_it
> --- Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.
>


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

[Geoserver-devel] HTTPS certificate has expired for maven.geo-solutions.it

[Ian Turton]

I'm getting build failures on Github due to the certificate being expired.

curl  "
https://maven.geo-solutions.it/net/sf/json-lib/json-lib/2.4.2-geoserver/json-lib-2.4.2-geoserver.pom;

curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

If someone can fix it I'd be grateful,

cheers

Ian

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

Re: [Geoserver-devel] Adding a new layer to the catalog for testing

[Ian Turton]

On Fri, 23 Sept 2022 at 20:46, Jody Garnett  wrote:

> Datastore is supposed to isolate the web service from individual files;
> but you can probable figure it out anyways.
>
> 1. Go through the dataStores looking at the connection parameters for the
> file name in question (probably represented as a file URL
> 2. Once located you can check the datastore for its resources (should be
> FeatureTypes, or CoverageTypes, or ...)
> 3. The resource name is the same as the layer name (we never did allow a
> resource to publish more than one layer although the separation is in the
> data model)
>
>
I'm not sure that works for what I'm trying to do.

I need to add a shapefile to the catalog so I can make a WFS request
against it. I can't find any tests that add more than a property file to
the catalog so I'm stuck.

Ian


> --
> Jody Garnett
>
>
> On Fri, 23 Sept 2022 at 04:32, Ian Turton  wrote:
>
>> I'm struggling to work out how I go from a DataStore (or just a file) to
>> a layer in the catalog I can make a WFS request from. The manual page will
>> voluminous doesn't currently mention this and I can't find an example of a
>> test doing it either which probably means I'm on the wrong path :-)
>>
>> Can anyone enlighten me?
>>
>> Ian
>>
>> --
>> Ian Turton
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

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

[Geoserver-devel] Adding a new layer to the catalog for testing

[Ian Turton]

I'm struggling to work out how I go from a DataStore (or just a file) to a
layer in the catalog I can make a WFS request from. The manual page will
voluminous doesn't currently mention this and I can't find an example of a
test doing it either which probably means I'm on the wrong path :-)

Can anyone enlighten me?

Ian

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

Re: [Geoserver-devel] Enhancement: WFS Simple Feature Response in new more compact JSON/JSONP format

[Ian Turton]

Sorry hit send too soon!

I would also prefer it if it was an extension rather than part of the core
GeoServer.

Ian


On Tue, 13 Sept 2022 at 12:52, Ian Turton  wrote:

> I would suggest calling it something other than GeoJSON since if it strays
> too far from the spec clients will become confused.
>
> Ian
>
> On Tue, 13 Sept 2022 at 12:07, Carsten Klein  wrote:
>
>> Hello everyone,
>>
>> I'd like to enhance WFS responses in JSON/JSONP format. In some of our
>> Web GIS Applications, one may download up to several thousand Simple
>> Features through WFS. Some Layers may have between 400 and 500 columns.
>>
>> Although JSON produces much smaller responses than XML/GML, such
>> responses quickly have sizes between 60 and 120 MB (uncompressed).
>>
>> The idea is to remove some redundancy from the GeoJSON format, which
>> provides a feature's attributes in a key/value map (JSON Object):
>>
>> {
>> "type":"FeatureCollection",
>> "features":[
>>{
>>   "type":"Feature",
>>   "id":"bugsites.3",
>>   "geometry":{
>>  "type":"Point",
>>  "coordinates":[
>> 590529,
>> 4914625
>>  ]
>>   },
>>   "geometry_name":"the_geom",
>>   "properties":{
>>  "cat":3,
>>  "str1":"Beetle site"
>>   }
>>},
>>{
>>   "type":"Feature",
>>   "id":"bugsites.4",
>>   "geometry":{
>>  "type":"Point",
>>  "coordinates":[
>> 590546,
>> 4915353
>>  ]
>>   },
>>   "geometry_name":"the_geom",
>>   "properties":{
>>  "cat":4,
>>  "str1":"Beetle site"
>>   }
>>}
>> ],
>> "totalFeatures":2,
>> "numberMatched":2,
>> "numberReturned":2,
>> "timeStamp":"2022-09-13T08:44:45.118Z",
>> "crs":{
>>"type":"name",
>>"properties":{
>>   "name":"urn:ogc:def:crs:EPSG::26713"
>>}
>> }
>> }
>>
>> Also, the "geometry_name" property is repeated for every feature returned.
>>
>> With lots of features and columns (the latter do not necessarily have
>> short names), this repeated schema information can quickly become the
>> dominating factor regarding the size of the response. (Of course, that
>> also depends on the type and complexity of the geometry.)
>>
>> Likely the repeated "type":"Feature" could be omitted as well. It's just
>> there in order to satisfy the GeoJSON specs. Maybe the "level of
>> compaction" could be specified for a request.
>>
>> By including schema information only once in the FeatureCollection
>> object, a more compact form of the JSON response may look like this:
>>
>> {
>> "type":"FeatureCollection",
>> "features":[
>>{
>>   "type":"Feature",
>>   "id":"bugsites.3",
>>   "geometry":{
>>  "type":"Point",
>>  "coordinates":[
>> 590529,
>> 4914625
>>  ]
>>   },
>>   "geometry_name":"the_geom",
>>   "properties":[
>>  3,
>>  "Beetle site"
>>   ]
>>},
>>{
>>   "type":"Feature",
>>   "id":"bugsites.4",
>>   "geometry":{
>>  "type":"Point",
>>  "coordinates":[
>> 590546,
>> 4915353
>>  ]
>>   },
>>   "properties":[
>>  4,
>>  "Beetle site"
>>   ]
>>}
>> ],
>> &quo

Re: [Geoserver-devel] Enhancement: WFS Simple Feature Response in new more compact JSON/JSONP format

[Ian Turton]

ma" object in the root "FeatureCollection" object
> contains the name of the geometry field as well as the names of the
> other properties as an array. The "properties" object in the "Feature"
> objects have become arrays as well, containing the property values only.
>
> Both arrays are "parallel", that is:
>
> Key: "schema"."properties"[0] => cat
> Val: features[N]."properties"[0]  => 3 or 4 (depending on N)
>
> Key: "schema"."properties"[1] => str1
> Val: features[N]."properties"[1]  => Beetle site
>
> In the above example with only two short-named fields savings are almost
> zero. However, with requests getting some thousand features, each having
> 300+ fields, savings may be quite significant.
>
> The new compact format is not GeoJSON, of course. However, what
> GeoServer currently returns is already not really compatible with
> GeoJSON specs, which, for example, only permit EPGS:4326 coordinates. In
> any case, that format is likely much smaller for requests described above.
>
> On the wire, these responses are typically compressed (deflate, brotli
> etc.). However, compressing smaller amounts of data typically results in
> smaller compressed junks. Also, it is not only about transferring the
> data; the data must be created and compressed by GeoServer and must be
> decompressed and parsed in the client. After all, smaller junks of data
> seem to be less resource consuming than larger ones.
>
> I'd like to add this new compact format directly into GeoServer's core
> WFS JSON code:
>
> gs-wfs: org.geoserver.wfs.json.GeoJSONGetFeatureResponse
>
> More or less, only method encodeSimpleFeatures must be modified in order
> to implement this new compact JSON format.
>
> However, that method iterates over a list of FeatureCollection objects
> (argument List resultsList). Could there be more than
> one FeatureCollection is the request returns simple features only?
> Shouldn't all simple features requested through WFS be of the same type?
> In other words, must I expect to deal with several distinct "schema"
> objects when requesting simple features? (don't think so)
>
> Since using this format, of course, is optional, I need a mechanism to
> tell the server whether to return compact JSON or not (and maybe the
> level of compaction it should use).
>
> One quite obvious option is to use vendor parameter "format_options".
> Here, a parameter like "json:compact" could trigger responding with
> compact JSON. This seems quite simple to implement.
>
> Another idea is to use different outputFormat MIME types or MIME types
> with additional parameters:
>
> application/json; type=compact; omitTypes=true
> text/javascript; type=compact
>
> Although distinguishing the format via the MIME type may be some more
> work to do, I do prefer this approach over the "format_options" way.
>
> What else do I have to consider?
>
> Many thanks in advance for your ideas on this :)
>
> Regards, Carsten
>
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GSIP-215 Drop Java 8

[Ian Turton]

+1

On both proposals

Ian

On Wed, 31 Aug 2022, 10:21 Jody Garnett,  wrote:

> Okay, updated proposal to target dropping Java 8 for GeoServer 2.23.0.
>
> Jody
>
> On Wed, Aug 31, 2022 at 10:34 AM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> +1 on switching to Java 11 only on main, I'm between a -0 and a -1 on
>> dropping on 2.22.0 too.
>>
>> Dropping Java 8 support in 2.22.0, as it would give the user base only 6
>> months before GeoServer stops supporting Java 8 altogether
>> (2.20.x is about to get its last release, 2.21.x will live only up to
>> March 2023).
>>
>> The 2.21.0 release already contained a warning
>> ,
>> quoting:
>> "This is likely to be the last release that supports Java 8 and we
>> encourage users to start to make the transition to Java 11 during the
>> lifetime of this branch."
>>
>> The message was too easy to ignore IMHO, I'd prefer to have a 2.22.0 with
>> a title stating in unequivocal terms "This is the last release supporting
>> Java 8, upgrade now".
>>
>> Cheers
>> Andrea
>>
>> On Tue, Aug 30, 2022 at 8:15 PM Jody Garnett 
>> wrote:
>>
>>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-215 for
>>> details, general idea is to drop Java 8 support so we can update
>>> dependencies and plan Jakarta migration.
>>>
>>> Thanks to foss4g code sprint and Euan Mitchell for initial pull request
>>> for docs:
>>> - https://github.com/geoserver/geoserver/pull/6137
>>>
>>> If this proposal is ready for the 2.22.0 release it would simplify the
>>> process of setting up build jobs for the new release cycle. Vote early,
>>> vote often...
>>> --
>>> Jody Garnett
>>>
>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards,
>>
>> Andrea Aime
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>>
> --
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Last minute proposal for GeoServer 2.22.0: GSIP 214

[Ian Turton]

Sounds like a good plan to me +1

Ian

On Wed, 3 Aug 2022, 18:07 Andrea Aime, 
wrote:

> Hi all,
> a quick last minute proposal to have more focused, and clear, REST API to
> reset specific resource caches:
>
> https://github.com/geoserver/geoserver/wiki/GSIP-214
>
> Please discuss and vote.
>
> Cheers
> Andrea
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Jira ticket assignment permissions

[Ian Turton]

+1

Ian


On Fri, 22 Jul 2022, 16:57 Andrea Aime, 
wrote:

> +1
>
> Cheers
> Andrea
>
> On Fri, Jul 22, 2022 at 4:20 PM Joseph Miller 
> wrote:
>
>> As discussed with Jody, I would like to be added as a user who can assign
>> himself tickets in Jira in order to avoif duplicate work conflicts.
>>
>> Thanks,
>> Joe Miller
>> @turingtestfail
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] New community module - ogcapi/moving-features

[Ian Turton]

Sounds good to me +1

Ian

On Wed, 13 Jul 2022 at 02:21, Brad Hards  wrote:
>
> As flagged in gitter, I am (virtually) attending the OGC Vector API code
> sprint. There is interest in supporting the OGC API for moving features within
> geoserver.
>
> The API specification is pretty early status, and I would like to see some
> changes. However there is no substitute for implementation to work out the
> issues, so sooner seems better (at least in some ways).
> The evolving specification can be found at
>
> https://github.com/opengeospatial/ogcapi-movingfeatures
>
> I request approval to add a community module under the existing ogcapi
> "umbrella" at
> geoserver/src/community/ogcapi/moving-features
> or at
> geoserver/src/community/ogcapi/ogcapi-moving-features
> if that is preferred for any reason.
>
> I have sent a corresponding request for the (unsupported) geotools module that
> would support this to geotools-devel.
>
> Brad
>
>
>
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel



-- 
Ian Turton


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

[Geoserver-devel] [JIRA] (GEOS-10565) Update JTS to 1.19.0

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZTE1YzQ2MDU1OGJiNDNlNzlkYTdjNjZkZDA4ODE3OGIiLCJwIjoiaiJ9
 ) / Task ( 
https://osgeo-org.atlassian.net/browse/GEOS-10565?atlOrigin=eyJpIjoiZTE1YzQ2MDU1OGJiNDNlNzlkYTdjNjZkZDA4ODE3OGIiLCJwIjoiaiJ9
 ) GEOS-10565 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10565?atlOrigin=eyJpIjoiZTE1YzQ2MDU1OGJiNDNlNzlkYTdjNjZkZDA4ODE3OGIiLCJwIjoiaiJ9
 ) Update JTS to 1.19.0 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10565?atlOrigin=eyJpIjoiZTE1YzQ2MDU1OGJiNDNlNzlkYTdjNjZkZDA4ODE3OGIiLCJwIjoiaiJ9
 )

Issue Type: Task Affects Versions: 2.21.0 Assignee: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) Created: 27/Jun/22 5:21 PM Priority: Medium Reporter: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

( 
https://osgeo-org.atlassian.net/browse/GEOS-10565#add-comment?atlOrigin=eyJpIjoiZTE1YzQ2MDU1OGJiNDNlNzlkYTdjNjZkZDA4ODE3OGIiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10565#add-comment?atlOrigin=eyJpIjoiZTE1YzQ2MDU1OGJiNDNlNzlkYTdjNjZkZDA4ODE3OGIiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100201- 
sha1:10a069b )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Propose a new community module: freemarker template editor

[Ian Turton]

Looks like a good idea +1

Ian

On Fri, 24 Jun 2022 at 20:09, Jean Pommier 
wrote:

> Hi dev list,
>
> I would like to propose a new community module : a web UI page for the
> edition of the FreeMarker templates.
>
> [image: edition-page.png]
>
> This is an old project of mine, that hadn't gone through the community
> module step and got buried at some point.
>
> Some people from the geOrchestra community have expressed a keen interest
> in this module and had me resurrect it. This is why I would like to bring
> it back to life and have it as community module.
>
> It is a simple UI, almost simplistic. The editor is a plain TextArea. But
> it allows to easily manage the templates' inheritance system (from default
> to workspace to store to layer) and have an easy view of where the current
> template files are taken from. On the authentication level, it is available
> for whomever has the admin rights on a workspace (no need to belong to
> admin group).
>
> It is working fine on master. The code is on my repo
> <https://github.com/pi-geosolutions/geoserver/tree/template-editor-extension/src/community/template-editor>,
> ready to be pulled in. I have written a documentation
> <https://github.com/pi-geosolutions/geoserver/blob/template-editor-extension/doc/en/user/source/community/template-editor/index.rst>
> page too. I already have signed an individual contributor licence
> agreement with OSGeo.
>
> I hope you will like it,
>
> Best,
>
> Jean
> --
>
> *Jean Pommier -- pi-Geosolutions*
>
> Ingénieur, consultant indépendant
>
> Tél. : (+33) 6 09 23 21 36
> E-mail : j...@pi-geosolutions.fr
> Web : www.pi-geosolutions.fr
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GSIP 213 CSS Cleanup

[Ian Turton]

+1 and +1 to Torben's suggestion

Ian

On Thu, 16 Jun 2022 at 16:11, Torben Barsballe 
wrote:

> This is definitely a part of GeoServer that could use cleanup.
>
> I would request that this effort include documentation of HTML/CSS best
> practices in the developer guide (matching the changes that were made).
> Probably somewhere in this subsection
> <https://docs.geoserver.org/latest/en/developer/programming-guide/web-ui/index.html>
> .
> This should help existing developers navigate the changes, and help keep
> future additions to the Web GUI in-line with the modernized structure.
>
> Cheers,
> Torben
>
> On Wed, Jun 15, 2022 at 6:25 AM Jody Garnett 
> wrote:
>
>> Jody and Michel here from the Bolsena code sprint with a proposal for
>> cleaning up the use of css:
>>
>> https://github.com/geoserver/geoserver/wiki/GSIP-213
>>
>> Scroll down to the bottom of the proposal for an example, feedback (and
>> encouragement) welcome.
>> --
>> Jody Garnett
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Early backport of stack of GUI trace utility

[Ian Turton]

+1 that sounds like it will save a lot of time when needed.

Ian

On Mon, 13 Jun 2022 at 18:18, Andrea Aime 
wrote:

> Hi all,
> I've just merged on main a PR adding a new tab in the status page, that
> allows admins to get a stack trace of the server.
> This is pretty handy in environments where getting a SSH connection is
> hard or just requires a lot of bureaucracy.
>
> I'm asking for an early backport on 2.21.x, and maybe even on 2.20.x,
> given its practical usefulness. I have got the backport bot to generate the
> PRs so you'll see them out there, but waiting for approval (or not) on this
> mail. The only way to make the bot generate the PRs, is to do so on merge,
> cannot make it do them later.
>
> Cheers
> Andrea
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] [JIRA] (GEOS-10535) WFS Update request throw NPE on bad namespace

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZTY1YmRjODBlOGRjNGVmMDg3ZmJjMTg4MGMxZTlkM2YiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10535?atlOrigin=eyJpIjoiZTY1YmRjODBlOGRjNGVmMDg3ZmJjMTg4MGMxZTlkM2YiLCJwIjoiaiJ9
 ) GEOS-10535 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10535?atlOrigin=eyJpIjoiZTY1YmRjODBlOGRjNGVmMDg3ZmJjMTg4MGMxZTlkM2YiLCJwIjoiaiJ9
 ) WFS Update request throw NPE on bad namespace ( 
https://osgeo-org.atlassian.net/browse/GEOS-10535?atlOrigin=eyJpIjoiZTY1YmRjODBlOGRjNGVmMDg3ZmJjMTg4MGMxZTlkM2YiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.19.5, 2.20.4, 2.21.0 Assignee: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) Components: WFS Created: 09/Jun/22 10:27 AM Priority: Medium Reporter: Ian 
Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

( 
https://osgeo-org.atlassian.net/browse/GEOS-10535#add-comment?atlOrigin=eyJpIjoiZTY1YmRjODBlOGRjNGVmMDg3ZmJjMTg4MGMxZTlkM2YiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10535#add-comment?atlOrigin=eyJpIjoiZTY1YmRjODBlOGRjNGVmMDg3ZmJjMTg4MGMxZTlkM2YiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100200- 
sha1:9199305 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-10534) a badly formed delete transaction will get a NPE instead of an informative error message

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiN2QwMjA1MGEwZjhmNGYwOThmZmUwZWRmZjg5MmFhNGEiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10534?atlOrigin=eyJpIjoiN2QwMjA1MGEwZjhmNGYwOThmZmUwZWRmZjg5MmFhNGEiLCJwIjoiaiJ9
 ) GEOS-10534 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10534?atlOrigin=eyJpIjoiN2QwMjA1MGEwZjhmNGYwOThmZmUwZWRmZjg5MmFhNGEiLCJwIjoiaiJ9
 ) a badly formed delete transaction will get a NPE instead of an informative 
error message ( 
https://osgeo-org.atlassian.net/browse/GEOS-10534?atlOrigin=eyJpIjoiN2QwMjA1MGEwZjhmNGYwOThmZmUwZWRmZjg5MmFhNGEiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.20.4, 2.21.0 Assignee: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) Components: WFS Created: 08/Jun/22 11:28 AM Priority: Medium Reporter: Ian 
Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

If a client sends an ill formed WFS transaction (e.g. malformed namespace) then 
GeoServer responds with a NPE

org.geoserver.wfs.WFSException: java.lang.NullPointerException
at org.geoserver.wfs.Transaction.transaction(Transaction.java:101)
at 
org.geoserver.wfs.DefaultWebFeatureService.transaction(DefaultWebFeatureService.java:154)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
org.geoserver.ows.util.RequestObjectLogger.invoke(RequestObjectLogger.java:51)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy58.transaction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:869)
at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:271)
at 
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
at 
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:52)
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1043)
at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1459)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
at 
org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1631)
at 
org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28)
at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
at 
org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1601)
at 
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:73)
at org.geoserver.ows.HTTPHeadersCollector.doFilter(HTTPHeadersCollector.java:48)
at 
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:70)
at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:167)
at 
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:70)
at 
org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:43)
at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
at 
org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1601)
at 
org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:39

Re: [Geoserver-devel] Fwd: Request body logging settings on the global settings page?

[Ian Turton]

Possibly, it's great work that for some reason I thought had been there
before and had been downgraded as a security fix or just broken over the
years.

Ian

On Fri, 3 Jun 2022 at 12:58, Joseph Miller  wrote:

> Ian,
> Perhaps a source of confusion was that this change was backported in
> combination with another, related change here:
> https://github.com/geoserver/geoserver/pull/5909 and here:
> https://github.com/geoserver/geoserver/pull/5897  ?
>
> Joe (https://github.com/turingtestfail)
>
> On Fri, Jun 3, 2022 at 7:36 AM Ian Turton  wrote:
>
>>
>>
>> Sorry originally sent to wrong list :-(
>>
>> > According to the manual -
>> https://docs.geoserver.org/main/en/user/configuration/globalsettings.html#enable-request-logging
>> and
>> https://docs.geoserver.org/main/en/user/production/troubleshooting.html#troubleshooting-requests
>> you can turn request body logging on via the global settings page. But you
>> can't - the only setting left from that is the size of the request body to
>> saved.
>> >
>> > Before I have a go at rewriting those sections to point to the web.xml
>> file I thought I'd check that we actually intended to remove the controls
>> from the global settings page or should I look instead at where they've
>> gone to?
>>
>> It looks like the documentation has got ahead of the implementation of
>> https://osgeo-org.atlassian.net/browse/GEOS-10469
>> https://github.com/geoserver/geoserver/pull/5829 which is where the
>> confuision is coming from.
>>
>>
>> Ian
>>
>> --
>> Ian Turton
>>
>>
>> --
>> Ian Turton
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

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

[Geoserver-devel] Fwd: Request body logging settings on the global settings page?

[Ian Turton]

Sorry originally sent to wrong list :-(

> According to the manual -
https://docs.geoserver.org/main/en/user/configuration/globalsettings.html#enable-request-logging
and
https://docs.geoserver.org/main/en/user/production/troubleshooting.html#troubleshooting-requests
you can turn request body logging on via the global settings page. But you
can't - the only setting left from that is the size of the request body to
saved.
>
> Before I have a go at rewriting those sections to point to the web.xml
file I thought I'd check that we actually intended to remove the controls
from the global settings page or should I look instead at where they've
gone to?

It looks like the documentation has got ahead of the implementation of
https://osgeo-org.atlassian.net/browse/GEOS-10469
https://github.com/geoserver/geoserver/pull/5829 which is where the
confuision is coming from.


Ian

-- 
Ian Turton


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

[Geoserver-devel] GeoServer 2.21.0 Release

[Ian Turton]

The GeoServer team is pleased to announce the release of the latest version
of GeoServer 2.21.0 which is made in conjunction with GeoTools 27.0 and
GeoWebCache 1.21.0. There are many improvements and fixes in this new
version and users are encouraged to upgrade as soon as possible.

Full details can be found at
https://geoserver.org/announcements/2022/05/24/geoserver-2-21-0-released.html
and the war can be downloaded from https://geoserver.org/release/stable/

Ian


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

Re: [Geoserver-devel] 2.20.x and 2.21.x early backport of [GEOS-10469] and [GEOS-10495]

[Ian Turton]

Happy to rerun the release if necessary, possibly this one and Andrea's css
vendor options one.

Ian

On Tue, 24 May 2022, 18:00 Jody Garnett,  wrote:

> Just went over this one in the meeting:
>
> If I can get it back ported before Ian makes the release I will do so :)
> --
> Jody Garnett
>
>
> On May 24, 2022 at 9:37:31 AM, Joseph Miller 
> wrote:
>
>> Hey All,
>> I'm writing to request permission for early backport to 2.20.x and 2.21.x
>> of
>> https://osgeo-org.atlassian.net/jira/core/projects/GEOS/issues/GEOS-10469
>> and
>> https://osgeo-org.atlassian.net/jira/core/projects/GEOS/issues/GEOS-10495
>> .  These improvements move request logging into the global settings page.
>> The changes to configuration files and code were done to preserve backwards
>> compatibility with previous default values maintained.
>>
>> Thanks,
>> Joe Miller
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Tags and release notes

[Ian Turton]

o some conflicts trying to sync tags between remote repos:
>>>>
>>>>  = [up to date]2.16.2  -> 2.16.2
>>>>
>>>>  ! [rejected]  2.16.3  -> 2.16.3  (would
>>>> clobber existing tag)
>>>>
>>>>  = [up to date]2.16.4  -> 2.16.4
>>>>
>>>> ...
>>>>
>>>>  = [up to date]2.20.2  -> 2.20.2
>>>>
>>>>  ! [rejected]  2.20.4  -> 2.20.4  (would
>>>> clobber existing tag)
>>>>
>>>>  = [up to date]2.3-RC1 -> 2.3-RC1
>>>>
>>>> I do not know if this is just me?  Not sure how they got out of sync?
>>>> --
>>>> Jody Garnett
>>>>
>>> ___
>>>> Geoserver-devel mailing list
>>>> Geoserver-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>
>>>
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Andrea Aime
>>>
>>> ==
>>> GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions Group
>>> phone: +39 0584 962313
>>>
>>> fax: +39 0584 1660272
>>>
>>> mob:   +39  333 8128928
>>>
>>> https://www.geosolutionsgroup.com/
>>>
>>> http://twitter.com/geosolutions_it
>>>
>>> ---
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail
>>>
>> --
>> --
>> Jody Garnett
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] [JIRA] (GEOS-10502) GML3 output is not pretty printed when pretty print is turned on in global settings.

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZjEyYzcwZWM4YjQ5NGViYTgwMmY1ODBkMDI4Y2IzODIiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10502?atlOrigin=eyJpIjoiZjEyYzcwZWM4YjQ5NGViYTgwMmY1ODBkMDI4Y2IzODIiLCJwIjoiaiJ9
 ) GEOS-10502 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10502?atlOrigin=eyJpIjoiZjEyYzcwZWM4YjQ5NGViYTgwMmY1ODBkMDI4Y2IzODIiLCJwIjoiaiJ9
 ) GML3 output is not pretty printed when pretty print is turned on in global 
settings. ( 
https://osgeo-org.atlassian.net/browse/GEOS-10502?atlOrigin=eyJpIjoiZjEyYzcwZWM4YjQ5NGViYTgwMmY1ODBkMDI4Y2IzODIiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.19.5, 2.20.4 Assignee: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) Components: WFS Created: 20/May/22 12:10 PM Priority: Medium Reporter: Ian 
Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

We need Geoserver's XML (WFS) responses to be formatted, or at least contain 
line breaks. The manual states that by enabling "Verbose messages" in the 
global settings, the XML output will be formatted. Unfortunately, turning this 
on did not change the WFS reponse formatting (tried with Geoserver 2.10 and 
2.20).

With a little further digging, I found a "verbose" option in the wfs.xml file. 
Enabling verbose here and restarting Geoserver resulted in formatted XML output.

Is this the expected behaviour? Is this the correct way to configure what we 
need? Is it reliable? (Should the manual be changed?)

Then I did some more research and found out that only WFS responses with the 
outputFormat=GML2 option are sent formatted (line breaks, indentations) when 
verbose is enabled in wfs.xml. GML3 is always sent without formatting. Is there 
a way to get the GML3-output also formatted?

( 
https://osgeo-org.atlassian.net/browse/GEOS-10502#add-comment?atlOrigin=eyJpIjoiZjEyYzcwZWM4YjQ5NGViYTgwMmY1ODBkMDI4Y2IzODIiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10502#add-comment?atlOrigin=eyJpIjoiZjEyYzcwZWM4YjQ5NGViYTgwMmY1ODBkMDI4Y2IzODIiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198- 
sha1:0f60739 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer 2.21.0 release manager

[Ian Turton]

Ok, thanks.

I can hold off until tomorrow if you want

Ian

On Thu, 19 May 2022 at 09:50, Jody Garnett  wrote:

> Ian I have not seen any solid down checks out of RC testing:
>
>- Andrea is checking if there is a regression on JAI logging
>- An issue is report GEOS-10487 with log location requiring an
>absolute path
>
>
> I have some time tomorrow to work on GEOS-10487, but I do not view it is a
> show-stopper.
> --
> Jody Garnett
>
>
> On May 11, 2022 at 12:13:35 AM, Ian Turton  wrote:
>
>> Haha, thanks!
>> Ian
>>
>> On Wed, 11 May 2022, 09:06 Jody Garnett,  wrote:
>>
>>> You are the release manager, you choose the day :)
>>> --
>>> Jody Garnett
>>>
>>>
>>> On May 10, 2022 at 10:55:48 AM, Ian Turton  wrote:
>>>
>>>> Actually I won't be able to start until 19th, I thought we always did
>>>> releases on Thursday.
>>>>
>>>> Let me know if this is a problem for anyone
>>>>
>>>> Ian
>>>>
>>>> On Tue, 10 May 2022, 19:51 Jody Garnett, 
>>>> wrote:
>>>>
>>>>> Thanks Ian, I can help with geowebcache.
>>>>> --
>>>>> Jody Garnett
>>>>>
>>>>>
>>>>> On May 10, 2022 at 10:48:00 AM, Ian Turton  wrote:
>>>>>
>>>>>> I can do the geotools and geoserver if someonecan help with
>>>>>> geowebcache.
>>>>>>
>>>>>> Ian
>>>>>>
>>>>>> On Tue, 10 May 2022, 18:54 Andrea Aime, <
>>>>>> andrea.a...@geosolutionsgroup.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> we are looking for a release manager for the 2.21.0, to be released
>>>>>>> tentatively May 18th 2022 (in 8 days).
>>>>>>>
>>>>>>> Any takers?
>>>>>>>
>>>>>>> Cheers
>>>>>>> Andrea
>>>>>>>
>>>>>>>
>>>>>>> ==
>>>>>>> GeoServer Professional Services from the experts!
>>>>>>>
>>>>>>> Visit http://bit.ly/gs-services-us for more information.
>>>>>>> ==
>>>>>>>
>>>>>>> Ing. Andrea Aime
>>>>>>> @geowolf
>>>>>>> Technical Lead
>>>>>>>
>>>>>>> GeoSolutions Group
>>>>>>> phone: +39 0584 962313
>>>>>>>
>>>>>>> fax: +39 0584 1660272
>>>>>>>
>>>>>>> mob:   +39  333 8128928
>>>>>>>
>>>>>>> https://www.geosolutionsgroup.com/
>>>>>>>
>>>>>>> http://twitter.com/geosolutions_it
>>>>>>>
>>>>>>> ---
>>>>>>>
>>>>>>> Con riferimento alla normativa sul trattamento dei dati personali
>>>>>>> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati 
>>>>>>> “GDPR”),
>>>>>>> si precisa che ogni circostanza inerente alla presente email (il suo
>>>>>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>>>>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>>>>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>>>>>> operazione è illecita. Le sarei comunque grato se potesse darmene 
>>>>>>> notizia.
>>>>>>>
>>>>>>> This email is intended only for the person or entity to which it is
>>>>>>> addressed and may contain information that is privileged, confidential 
>>>>>>> or
>>>>>>> otherwise protected from disclosure. We remind that - as provided by
>>>>>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of 
>>>>>>> this
>>>>>>> e-mail or the information herein by anyone other than the intended
>>>>>>> recipient is prohibited. If you have received this email by mistake, 
>>>>>>> please
>>>>>>> notify us immediately by telephone or e-mail
>>>>>>> ___
>>>>>>> Geoserver-devel mailing list
>>>>>>> Geoserver-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>>>>
>>>>>> ___
>>>>>> Geoserver-devel mailing list
>>>>>> Geoserver-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>>>
>>>>>

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

Re: [Geoserver-devel] GeoServer 2.21.0 release manager

[Ian Turton]

Haha, thanks!
Ian

On Wed, 11 May 2022, 09:06 Jody Garnett,  wrote:

> You are the release manager, you choose the day :)
> --
> Jody Garnett
>
>
> On May 10, 2022 at 10:55:48 AM, Ian Turton  wrote:
>
>> Actually I won't be able to start until 19th, I thought we always did
>> releases on Thursday.
>>
>> Let me know if this is a problem for anyone
>>
>> Ian
>>
>> On Tue, 10 May 2022, 19:51 Jody Garnett,  wrote:
>>
>>> Thanks Ian, I can help with geowebcache.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On May 10, 2022 at 10:48:00 AM, Ian Turton  wrote:
>>>
>>>> I can do the geotools and geoserver if someonecan help with geowebcache.
>>>>
>>>> Ian
>>>>
>>>> On Tue, 10 May 2022, 18:54 Andrea Aime, <
>>>> andrea.a...@geosolutionsgroup.com> wrote:
>>>>
>>>>> Hi all,
>>>>> we are looking for a release manager for the 2.21.0, to be released
>>>>> tentatively May 18th 2022 (in 8 days).
>>>>>
>>>>> Any takers?
>>>>>
>>>>> Cheers
>>>>> Andrea
>>>>>
>>>>>
>>>>> ==
>>>>> GeoServer Professional Services from the experts!
>>>>>
>>>>> Visit http://bit.ly/gs-services-us for more information.
>>>>> ==
>>>>>
>>>>> Ing. Andrea Aime
>>>>> @geowolf
>>>>> Technical Lead
>>>>>
>>>>> GeoSolutions Group
>>>>> phone: +39 0584 962313
>>>>>
>>>>> fax: +39 0584 1660272
>>>>>
>>>>> mob:   +39  333 8128928
>>>>>
>>>>> https://www.geosolutionsgroup.com/
>>>>>
>>>>> http://twitter.com/geosolutions_it
>>>>>
>>>>> ---
>>>>>
>>>>> Con riferimento alla normativa sul trattamento dei dati personali
>>>>> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati 
>>>>> “GDPR”),
>>>>> si precisa che ogni circostanza inerente alla presente email (il suo
>>>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>>>
>>>>> This email is intended only for the person or entity to which it is
>>>>> addressed and may contain information that is privileged, confidential or
>>>>> otherwise protected from disclosure. We remind that - as provided by
>>>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of 
>>>>> this
>>>>> e-mail or the information herein by anyone other than the intended
>>>>> recipient is prohibited. If you have received this email by mistake, 
>>>>> please
>>>>> notify us immediately by telephone or e-mail
>>>>> ___
>>>>> Geoserver-devel mailing list
>>>>> Geoserver-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>>
>>>> ___
>>>> Geoserver-devel mailing list
>>>> Geoserver-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>
>>>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer 2.21.0 release manager

[Ian Turton]

Actually I won't be able to start until 19th, I thought we always did
releases on Thursday.

Let me know if this is a problem for anyone

Ian

On Tue, 10 May 2022, 19:51 Jody Garnett,  wrote:

> Thanks Ian, I can help with geowebcache.
> --
> Jody Garnett
>
>
> On May 10, 2022 at 10:48:00 AM, Ian Turton  wrote:
>
>> I can do the geotools and geoserver if someonecan help with geowebcache.
>>
>> Ian
>>
>> On Tue, 10 May 2022, 18:54 Andrea Aime, <
>> andrea.a...@geosolutionsgroup.com> wrote:
>>
>>> Hi all,
>>> we are looking for a release manager for the 2.21.0, to be released
>>> tentatively May 18th 2022 (in 8 days).
>>>
>>> Any takers?
>>>
>>> Cheers
>>> Andrea
>>>
>>>
>>> ==
>>> GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions Group
>>> phone: +39 0584 962313
>>>
>>> fax: +39 0584 1660272
>>>
>>> mob:   +39  333 8128928
>>>
>>> https://www.geosolutionsgroup.com/
>>>
>>> http://twitter.com/geosolutions_it
>>>
>>> ---
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer 2.21.0 release manager

[Ian Turton]

I can do the geotools and geoserver if someonecan help with geowebcache.

Ian

On Tue, 10 May 2022, 18:54 Andrea Aime, 
wrote:

> Hi all,
> we are looking for a release manager for the 2.21.0, to be released
> tentatively May 18th 2022 (in 8 days).
>
> Any takers?
>
> Cheers
> Andrea
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Problems building GeoServer documentation

[Ian Turton]

t;>>> [INFO]
>>>>> 
>>>>> [INFO] Total time:  16.325 s
>>>>>
>>>>> These are the versions.
>>>>>
>>>>> python -V
>>>>> Python 2.7.18
>>>>> sphinx-build --version
>>>>> sphinx-build 3.5.2
>>>>>
>>>>> If the problem is with python2, I have tried to
>>>>> alias python=python3
>>>>> python -V
>>>>> Python 3.8.10
>>>>> and that also does not help.
>>>>>
>>>>> Attached is the full output from maven, if that helps.
>>>>>
>>>>> Can anyone guide me on what the problem might be, please?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Peter
>>>>> ___
>>>>> Geoserver-devel mailing list
>>>>> Geoserver-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>>
>>>> --
>>>> --
>>>> Jody Garnett
>>>> ___
>>>> Geoserver-devel mailing list
>>>> Geoserver-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>
>>>
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Andrea Aime
>>>
>>> == GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea
>>> Aime @geowolf Technical Lead
>>>
>>> GeoSolutions Group phone: +39 0584 962313
>>>
>>> fax: +39 0584 1660272
>>>
>>> mob:   +39  333 8128928
>>>
>>> https://www.geosolutionsgroup.com/
>>>
>>> http://twitter.com/geosolutions_it
>>>
>>> ---
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. 
>>> This
>>> email is intended only for the person or entity to which it is addressed
>>> and may contain information that is privileged, confidential or otherwise
>>> protected from disclosure. We remind that - as provided by European
>>> Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail
>>> or the information herein by anyone other than the intended recipient is
>>> prohibited. If you have received this email by mistake, please notify us
>>> immediately by telephone or e-mail
>>>
>>
>
> --
>
> Regards,
>
> Andrea Aime
>
> == GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea
> Aime @geowolf Technical Lead
>
> GeoSolutions Group phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. 
> This
> email is intended only for the person or entity to which it is addressed
> and may contain information that is privileged, confidential or otherwise
> protected from disclosure. We remind that - as provided by European
> Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail
> or the information herein by anyone other than the intended recipient is
> prohibited. If you have received this email by mistake, please notify us
> immediately by telephone or e-mail
>
>
> ___
> Geoserver-devel mailing 
> listGeoserver-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] [JIRA] (GEOS-10455) allow user to optionally turn off SLD parameter validation

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMmU0NmU0ZjBhMDA1NDNjZThjY2E4Mjk5YmE3NWFmZmQiLCJwIjoiaiJ9
 ) / Improvement ( 
https://osgeo-org.atlassian.net/browse/GEOS-10455?atlOrigin=eyJpIjoiMmU0NmU0ZjBhMDA1NDNjZThjY2E4Mjk5YmE3NWFmZmQiLCJwIjoiaiJ9
 ) GEOS-10455 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10455?atlOrigin=eyJpIjoiMmU0NmU0ZjBhMDA1NDNjZThjY2E4Mjk5YmE3NWFmZmQiLCJwIjoiaiJ9
 ) allow user to optionally turn off SLD parameter validation ( 
https://osgeo-org.atlassian.net/browse/GEOS-10455?atlOrigin=eyJpIjoiMmU0NmU0ZjBhMDA1NDNjZThjY2E4Mjk5YmE3NWFmZmQiLCJwIjoiaiJ9
 )

Issue Type: Improvement Affects Versions: 2.20.3 Assignee: Unassigned 
Components: WMS Created: 08/Apr/22 11:09 AM Priority: Medium Reporter: Ian 
Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

As this question ( 
https://gis.stackexchange.com/questions/428076/sld-ignoring-propertynames-case-or-using-if-then-else/428116#428116
 ) shows there are times when it would be useful to not carry out the 
validation of all the parameters in an SLD file.

( 
https://osgeo-org.atlassian.net/browse/GEOS-10455#add-comment?atlOrigin=eyJpIjoiMmU0NmU0ZjBhMDA1NDNjZThjY2E4Mjk5YmE3NWFmZmQiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10455#add-comment?atlOrigin=eyJpIjoiMmU0NmU0ZjBhMDA1NDNjZThjY2E4Mjk5YmE3NWFmZmQiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198- 
sha1:943baf4 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] proposals: promote metadata and csw-iso to extensions

[Ian Turton]

+1

Ian

On Mon, 4 Apr 2022 at 12:50, Niels Charlier via Geoserver-devel <
geoserver-devel@lists.sourceforge.net> wrote:

> Hello,
>
> I have written up two proposals to promote community modules "metadata"
> and "csw-iso" to extensions.
>
> https://github.com/geoserver/geoserver/wiki/GSIP-311
>
> https://github.com/geoserver/geoserver/wiki/GSIP-312
>
> I believe stability, test coverage, users, are all okay. Please discuss.
>
> One question about copyrights though: the metadata module was mostly
> written by me (who signed CLA) as part of a contract particular
> government department. I believe they technically have copyrights, and
> agreed to open source it. What would be required though? Should they
> sign CLA for businesses?
>
> Kind Regards
>
> Niels
>
>
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GSIP 210: graduate KML-PPIO to extension

[Ian Turton]

That sounds like a very good plan then.
Ian


On Mon, 4 Apr 2022 at 09:14, Andrea Aime 
wrote:

> On Sat, Apr 2, 2022 at 10:22 AM Ian Turton  wrote:
>
>> I was going to ask if this included promoting the GeoTools kml module to
>> supported but I see that it doesn't use it.
>>
>
> The kml unsupported module is a datastore. While a PPIO can use such a
> high level API, it has no need to.
> To draw a couple of parallels:
>
>- GeoJSONPPIO uses low level GeoJSONWriter and GeoJSONReader (it could
>be written against the stores, but it would be overkill, we just want to
>read features out of a stream, and encode them onto a stream)
>- ShapeZipPPIO uses a store, because it's not harder than using a
>lower level API, we still need to dump on local filesystem first to zip
>
>
> Is there a possibility to move the KML parsing and generating code back
>> into GeoTools at some point in the future?
>>
>
> The parsing is already using gt-xsd-kml just like the GeoTools KML
> unsupported code.
> The writing instead is using the GeoServer KML module, both for
> consistency and functionality. That code might not be
> that is easy to extract, as it was written with usage in GeoServer in mind
> (depends in a lot of places on WMSMapContext/GetMapRequest).
>
> The gt-xsd-kml module has also encoding support, but as most XSD modules,
> it's not symmetric (one has to write parsing and encoding
> as separate groups of methods, ability to parse does not equate to the one
> of writing, and vice versa).
> I see the module has encoding tests, but don't know how well it works... I
> recall Alessio had troubles making it work during the
> first write of kmlppio, and eventually switched to the GeoServer kml
> module instead.
>
> It's good to have consistent behavior between WFS and WPS output
> formats... the other possibility would be to rewrite the
> kml module to use gt-xsd-kml for encoding which... just gives me
> nightmares TBH!!!
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>


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

Re: [Geoserver-devel] GSIP 210: graduate KML-PPIO to extension

[Ian Turton]

I was going to ask if this included promoting the GeoTools kml module to
supported but I see that it doesn't use it. Is there a possibility to move
the KML parsing and generating code back into GeoTools at some point in the
future? It would be nice to have that functionality in a supported GeoTools
module and avoid it being implemented twice in GeoServer (is it?)

Otherwise +1

Ian

On Fri, 1 Apr 2022 at 15:07, Andrea Aime 
wrote:

> Hi all,
> I've prepared a GSIP to graduate the KML-PPIO module based on our
> discussion during the last PSC meeting, available here:
>
> https://github.com/geoserver/geoserver/wiki/GSIP-210
>
> Let me know what you think, and/or cast a vote if you're on the PSC.
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

[Geoserver-devel] Old orphaned pages in docs

[Ian Turton]

If you goto https://docs.geoserver.org/latest/en/user/community/scripting/
you find a set of 2.19.x pages (rather than 2.21.x that is latest) that are
not actually linked to anything (but they are still found in google) - is
there any way to delete them? and I guess update the build process to make
sure it builds into an empty directory.

Ian

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

[Geoserver-devel] Who minds the CSW code?

[Ian Turton]

I could do with a review of https://github.com/geoserver/geoserver/pull/5746
- which removes a test for a request with an empty escape character in a
Like filter. It was added 6 years ago by Ben and Rini and I don't see any
related issue so I'm not sure if this is a requirement for CSW to work? or
just a common error that people make?

I need to remove this test as it's blocking
https://github.com/geotools/geotools/pull/3824 which prevents people
breaking the server by passing in unwise patterns including empty escapes

cheers

Ian

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

[Geoserver-devel] [JIRA] (GEOS-10433) Fix tests that rely on poorly written like filters

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiM2RkMjgxMzA0ZWRjNGQyN2EyZDc1ODUzZjMyYmE4N2EiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10433?atlOrigin=eyJpIjoiM2RkMjgxMzA0ZWRjNGQyN2EyZDc1ODUzZjMyYmE4N2EiLCJwIjoiaiJ9
 ) GEOS-10433 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10433?atlOrigin=eyJpIjoiM2RkMjgxMzA0ZWRjNGQyN2EyZDc1ODUzZjMyYmE4N2EiLCJwIjoiaiJ9
 ) Fix tests that rely on poorly written like filters ( 
https://osgeo-org.atlassian.net/browse/GEOS-10433?atlOrigin=eyJpIjoiM2RkMjgxMzA0ZWRjNGQyN2EyZDc1ODUzZjMyYmE4N2EiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.19.5, 2.20.3 Assignee: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) Components: WCS Created: 25/Mar/22 5:43 PM Priority: Medium Reporter: Ian 
Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

As we harden our creation of regular expressions in 
https://osgeo-org.atlassian.net/browse/GEOT-7098 one of the CSW tests creates a 
like filter with no escape in it. This no longer works as GeoTools throws an 
exception for empty escapes.

( 
https://osgeo-org.atlassian.net/browse/GEOS-10433#add-comment?atlOrigin=eyJpIjoiM2RkMjgxMzA0ZWRjNGQyN2EyZDc1ODUzZjMyYmE4N2EiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10433#add-comment?atlOrigin=eyJpIjoiM2RkMjgxMzA0ZWRjNGQyN2EyZDc1ODUzZjMyYmE4N2EiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100197- 
sha1:46df9a5 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Do we still need the imageio and native JAI instructions in the manual

[Ian Turton]

For sometime the section (
https://docs.geoserver.org/latest/en/user/production/java.html#outdated-install-native-jai-and-imageio-extensions)
has been marked as outdated, is it time we deleted it as it still seems to
be confusing users
https://gis.stackexchange.com/questions/425858/how-can-i-install-native-jai-on-geoserver-2-20-x-geoserver-2-19-x

Ian

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

Re: [Geoserver-devel] 2.19.5 release artefacts available for testing

[Ian Turton]

I got waylaid by other work, but I hope to get to it on Thursday, unless
anyone else can do it earlier for me.

Ian

On Tue, 1 Mar 2022, 17:49 Andrea Aime, 
wrote:

> Hi Ian,
> we just noticed that the release has been published on SF, but not
> announced on
> the blog or web site. Do you have a PR incoming for that too?
>
> Cheers
> Andrea
>
> On Sun, Feb 20, 2022 at 12:54 PM Ian Turton  wrote:
>
>> get them from
>> https://build.geoserver.org/view/release/job/geoserver-release/42/artifact/
>>
>> If all is well I'll publish them tomorrow
>>
>> Ian
>>
>> --
>> Ian Turton
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] was GeoServer 2.20.2 built with Java 11?

[Ian Turton]

I looked in the manifest, so all should be good

Ian


On Mon, 21 Feb 2022 at 06:48, Jody Garnett  wrote:

> Thanks Ian, ... did you check the jar manifest, or just the logs?
> --
> Jody Garnett
>
>
> On Fri, 18 Feb 2022 at 04:14, Ian Turton  wrote:
>
>> Today's build of 25.5 seems to have been built with 1.8.0_212. I'll keep
>> an eye out as I proceed
>>
>> Ian
>>
>> On Fri, 18 Feb 2022 at 08:43, Mark Prins  wrote:
>>
>>> downloaded and extracted the war from the server, the manifest file in
>>> gt-main-26.2.jar says
>>>
>>> Manifest-Version: 1.0
>>>
>>> Created-By: Apache Maven 3.6.3
>>>
>>> Built-By: jenkins
>>>
>>> Build-Jdk: 11.0.13
>>>
>>> Class-Path: gt-referencing-26.2.jar ejml-ddense-0.34.jar ejml-core-0.34.
>>>
>>>   jar commons-pool-1.5.4.jar gt-metadata-26.2.jar gt-opengis-26.2.jar sys
>>>
>>>   tems-common-2.0.2.jar unit-api-2.0.jar indriya-2.0.2.jar uom-lib-common
>>>
>>>   -2.0.jar javax.inject-1.jar si-quantity-2.0.1.jar si-units-2.0.1.jar ja
>>>
>>>   karta.annotation-api-1.3.4.jar net.opengis.ows-26.2.jar org.w3.xlink-26
>>>
>>>   .2.jar org.eclipse.emf.common-2.15.0.jar org.eclipse.emf.ecore-2.15.0.j
>>>
>>>   ar org.eclipse.emf.ecore.xmi-2.15.0.jar jgridshift-core-1.3.jar Geograp
>>>
>>>   hicLib-Java-1.49.jar gt-http-26.2.jar jts-core-1.18.2.jar commons-text-
>>>
>>>   1.6.jar commons-lang3-3.8.1.jar jackson-core-2.10.5.jar jai_core-1.1.3.
>>>
>>>   jar
>>>
>>> Automatic-Module-Name: org.geotools.main
>>>
>>> Build-Timestamp: 23-Jan-2022 04:52
>>>
>>> Git-Revision: 64c409b2a537142993932e706c3f9c6e9efa7529
>>>
>>> Project-Version: 26.2
>>>
>>>
>>>
>>> which is identicat to the one from the geoserver.war I just downloaded
>>> from sourceforge:
>>>
>>> Manifest-Version: 1.0
>>>
>>> Automatic-Module-Name: org.geotools.main
>>>
>>> Build-Timestamp: 23-Jan-2022 08:56
>>>
>>> Built-By: jenkins
>>>
>>> Class-Path: gt-referencing-26.2.jar ejml-ddense-0.34.jar ejml-core-0.3
>>>
>>>   4.jar commons-pool-1.5.4.jar gt-metadata-26.2.jar gt-opengis-26.2.jar
>>>
>>>systems-common-2.0.2.jar unit-api-2.0.jar indriya-2.0.2.jar uom-lib-
>>>
>>>   common-2.0.jar javax.inject-1.jar si-quantity-2.0.1.jar si-units-2.0.
>>>
>>>   1.jar jakarta.annotation-api-1.3.4.jar net.opengis.ows-26.2.jar org.w
>>>
>>>   3.xlink-26.2.jar org.eclipse.emf.common-2.15.0.jar org.eclipse.emf.ec
>>>
>>>   ore-2.15.0.jar org.eclipse.emf.ecore.xmi-2.15.0.jar jgridshift-core-1
>>>
>>>   .3.jar GeographicLib-Java-1.49.jar gt-http-26.2.jar jts-core-1.18.2.j
>>>
>>>   ar commons-text-1.6.jar commons-lang3-3.8.1.jar jackson-core-2.10.5.j
>>>
>>>   ar jai_core-1.1.3.jar
>>>
>>> Project-Version: 26.2
>>>
>>> Git-Revision: 64c409b2a537142993932e706c3f9c6e9efa7529
>>>
>>> Created-By: Apache Maven 3.6.3
>>>
>>> Build-Jdk: 1.8.0_212
>>>
>>>
>>>
>>> On 17-02-2022 21:13, Jody Garnett wrote:
>>> > Can you check some of the gt and gs jars please, we should be able to
>>> > confirm:
>>> >
>>> > jar xvf gt-wfs-26.2.jar META-INF
>>> >
>>> > Or extract a class file and use javap -v  | grep major
>>>
>>> this wil tell you the class level, but not the compiler version.
>>> In fact both are the same:
>>>
>>> javap -v -classpath
>>> /tmp/___oigs/download/geoserver-2.20.2-war/WEB-INF/lib/gt-main-26.2.jar
>>> org.geotools.data.PrjFileReader | grep version
>>>
>>>minor version: 0
>>>major version: 52
>>>
>>>
>>> javap -v -classpath
>>> /tmp/___oigs/oigs-server/WEB-INF/lib/gt-main-26.2.jar
>>> org.geotools.data.PrjFileReader | grep version
>>>
>>>minor version: 0
>>>major version: 52
>>>
>>>
>>> checking for the problematic method call
>>>
>>> javap -v -classpath
>>> /tmp/___oigs/download/geoserver-2.20.2-war/WEB-INF/lib/gt-main-26.2.jar
>>> org.geotools.data.PrjFileReader | grep ByteBuffer.limit
>>>
>>> #12 = Methodref  #107.#109 //
>>> java/nio/ByteBuffer.limit:(I)Ljava/nio/Buffer;
>>>  53

[Geoserver-devel] 2.19.5 release artefacts available for testing

[Ian Turton]

get them from
https://build.geoserver.org/view/release/job/geoserver-release/42/artifact/

If all is well I'll publish them tomorrow

Ian

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

Re: [Geoserver-devel] was GeoServer 2.20.2 built with Java 11?

[Ian Turton]

eotools.data.PrjFileReader.(PrjFileReader.java:84)
> >  at
> > org.geotools.data.PrjFileReader.(PrjFileReader.java:64)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileSetManager.openPrjReader(ShapefileSetManager.java:152)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileFeatureSource.readAttributes(ShapefileFeatureSource.java:499)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileFeatureSource.buildFeatureType(ShapefileFeatureSource.java:454)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileFeatureStore.buildFeatureType(ShapefileFeatureStore.java:142)
> >  at
> >
>  
> org.geotools.data.store.ContentFeatureSource.getAbsoluteSchema(ContentFeatureSource.java:338)
> >  at
> >
>  
> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:307)
> >  at
> >
>  
> org.geotools.data.store.ContentFeatureStore.getWriter(ContentFeatureStore.java:116)
> >      at
> >
>  
> org.geotools.data.store.ContentDataStore.getFeatureWriter(ContentDataStore.java:381)
> >  at
> >
>  
> org.geotools.data.store.ContentDataStore.getFeatureWriter(ContentDataStore.java:412)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileDumper$StoreWriter.createStoreAndWriter(ShapefileDumper.java:92)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileDumper$StoreWriter.(ShapefileDumper.java:86)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileDumper.getStoreWriter(ShapefileDumper.java:460)
> >  at
> >
>  
> org.geotools.data.shapefile.ShapefileDumper.getStoreWriter(ShapefileDumper.java:420)
> >  at
> >
>  org.geotools.data.shapefile.ShapefileDumper.dump(ShapefileDumper.java:241)
> >  at
> >
>  org.geotools.data.shapefile.ShapefileDumper.dump(ShapefileDumper.java:185)
> >
> >
> > ___
> > Geoserver-devel mailing list
> > Geoserver-devel@lists.sourceforge.net
> > <mailto:Geoserver-devel@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> > <https://lists.sourceforge.net/lists/listinfo/geoserver-devel>
> >
>
>
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] Release managers needed for 2.19.5, 2.21-RC and 2.21.0.

[Ian Turton]

On Wed, 16 Feb 2022 at 16:58, Jody Garnett  wrote:

> We are heading into a busy time, and can really use some volunteers for
> the release schedule
> .
>
>- 2022-02-18 GeoServer 2.19.5 Release (yes this friday)
>
> I can take that one.


>
>-
>- 2022-03-04 GeoServer 2.21-RC Release Candidate (expect delay for
>GSIP-167)
>- 2022-03-18 GeoServer 2.21.0 Release
>
> Bonus:
>
> I would like to ask to make a 2.20.x release collecting recent fixes for a
> customer, even just to maven would be fine:
>
>- 2022-02-XX GeoServer 2.20.2-1 or 2.20.3
>
>
Sounds fine to me too +1

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

[Geoserver-devel] [JIRA] (GEOS-10392) Sending the contents of a tiff file to an "external.geotiff" endpoint in the REST API will crash GeoServer

[Ian Turton (JIRA)]

Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiODFkMWQ1N2VlZGQ0NDA5Y2E0YzVmNjM4NjYxMjQxNzciLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10392?atlOrigin=eyJpIjoiODFkMWQ1N2VlZGQ0NDA5Y2E0YzVmNjM4NjYxMjQxNzciLCJwIjoiaiJ9
 ) GEOS-10392 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10392?atlOrigin=eyJpIjoiODFkMWQ1N2VlZGQ0NDA5Y2E0YzVmNjM4NjYxMjQxNzciLCJwIjoiaiJ9
 ) Sending the contents of a tiff file to an "external.geotiff" endpoint in the 
REST API will crash GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS-10392?atlOrigin=eyJpIjoiODFkMWQ1N2VlZGQ0NDA5Y2E0YzVmNjM4NjYxMjQxNzciLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.20.2 Assignee: Unassigned Components: REST 
Created: 16/Feb/22 6:11 PM Priority: Medium Reporter: Ian Turton ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8d264a2b-8be0-40de-8b94-9442d49c4f6f
 )

If while creating a coverage store via REST using a remote file location (and 
you happen to be on the same machine) if you leave the @ sign in your CURL 
commandline, GeoServer receives the content of the tif as the URL location of 
the file and attempts to use it with out any checking. This causes what looks 
like a buffer overflow and kills the server. A very carefully constructed tif 
file could cause a security problem (in theory) and it does DOS the machine 
even if unintentionally.

It would be good if we carried out some basic checks before blindly changing it 
into a URL.

( 
https://osgeo-org.atlassian.net/browse/GEOS-10392#add-comment?atlOrigin=eyJpIjoiODFkMWQ1N2VlZGQ0NDA5Y2E0YzVmNjM4NjYxMjQxNzciLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10392#add-comment?atlOrigin=eyJpIjoiODFkMWQ1N2VlZGQ0NDA5Y2E0YzVmNjM4NjYxMjQxNzciLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100191- 
sha1:831671b )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-167 Log4j Update

[Ian Turton]

+1 from me

Ian

On Tue, 1 Feb 2022 at 18:13, Jody Garnett  wrote:

> Based on today's meeting: I would like to propose GSIP-167
>
> I will attach a quote for 5k to the above page; suggest remaining funds go
> to cite code sprint.
> --
> Jody Garnett
>
>
> On Tue, 11 Jan 2022 at 13:42, Jody Garnett  wrote:
>
>> I double checked what was needed for log4j update, and updated the
>> proposal to reflect log4 2 ability to load log4 1 configuration files:
>> https://github.com/geoserver/geoserver/wiki/GSIP-167
>>
>> While I am not sure I have capacity I hope the research is useful.
>> --
>> Jody Garnett
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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