Re: [Geotools-devel] [Geoserver-devel] GeoTools / GeoServer PMC meeting - 2019-05-28
I have used the https://letsencrypt.org for my personal websites. The downside to using it is the 90 expiration dates. I had to install and configure the certbot on my ubuntu servers to automatically renew the certificates when they get within 30 days of expiration. I like it, but it does take that little bit extra to setup. Chris Snider Senior Software Engineer [pa-logo-email] From: Andrea Aime Sent: Friday, May 31, 2019 10:35 AM To: Torben Barsballe ; Jody Garnett Cc: geoserver-devel ; GeoTools Developers list Subject: Re: [Geoserver-devel] [Geotools-devel] GeoTools / GeoServer PMC meeting - 2019-05-28 On Fri, May 31, 2019 at 6:29 PM Torben Barsballe mailto:tbarsba...@federal.planet.com>> wrote: I haven't touched the nightlies in a couple days, so it may have just been them trickling through the build. Glad its working again though. I'll ask about https again. Planet Federal ought to have a cert for build.geoserver.org<http://build.geoserver.org>, I just don't have access to it. If it's just a matter of getting a hold of a valid certificate, why not use a https://letsencrypt.org/ one? I guess some users will get broken if the certificate is not the same as it was before, bust I'm guessing most should work fine. I found run.sh for the cite tests, and have added a PR to the geoserver-cite-tools repo containing it, so that it is in version control. If you want to take a look at that, and try and get the cite tests working, that would be great. I also included my notes from last time I looked at the cite tests in a comment at the top of the file - that should help get this working. The PR is here: https://github.com/geoserver/geoserver-cite-tools/pull/8 I can have a look at it yes (think I'm going to have a bad weekend :-D ) The other option would be to look at the release jobs, and see what changes need to be made there to get them working again, although I think Jody mentioned he might be doing that soon. Let's hear from Jody. A windows build box is on the way, someone else at Planet Federal is looking into it. One other thing on my radar (but lower priority that everything else) is the geowebcache nightlies, which aren't configured to use git, and need to be updated before they'll work again. I think that Jody was looking into it yesterday? Cheers Andrea -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] [Geoserver-devel] GeoTools PR reviews and downstream builds
Is any part of the build chain Jenkins? I know Jenkins can call a build script from another branch of the same repository, but it may also work to call a build job from a different repository. I plan on investigating this process for our in-house builds for a project I moved to. Might be worth someone with access to the build servers to investigate cross-repository builds? Chris Snider Senior Software Engineer [pa-logo-email] From: Andrea Aime Sent: Monday, May 13, 2019 10:37 AM To: Geotools-Devel list ; Geoserver-devel Subject: Re: [Geoserver-devel] GeoTools PR reviews and downstream builds On Mon, May 13, 2019 at 5:29 PM Andrea Aime mailto:andrea.a...@geo-solutions.it>> wrote: Was wondering if this could be delegated to the build server, rough idea: * Add a entry in the build matrix that runs a custom shell script * The script build geotools without tests (the other builds cover that) in order to have fresh local GT jars in the maven repository * The script then check out GeoServer sources, and builds it with tests * Repeat the above steps for GWC as well However, I have no idea if a build matrix entry is even allowed to do the above. Has anyone experiences trying to do anything similar Another possibility would be to run the custom script on another build platform. Has anyone experience for example with circle-ci? I see they provide 4 build containers to open source projects: https://circleci.com/open-source/ Open to other free alternatives too, bring them in. Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Line endings checks on Jenkins and Travis CI
Andrea, Ian, This is the .gitattributes I have on my Windows ™ box for our geo-spatial services. * text eol=lf *.sql eol=lf *.jpg binary *.png binary *.tif binary *.gz binary *.zip binary *.FPT binary This helps GIT understand what we want done with files locally. I also set my git attributes to leave files alone and stop helping with LF > CRLF > LF transitions. Chris Snider Senior Software Engineer [cid:image001.png@01D2E6A5.9104F820] From: Andrea Aime [mailto:andrea.a...@geo-solutions.it] Sent: Friday, June 29, 2018 7:13 AM To: Ian Turton Cc: Geoserver-devel ; Geotools-Devel list Subject: Re: [Geotools-devel] Line endings checks on Jenkins and Travis CI On Fri, Jun 29, 2018 at 3:10 PM, Ian Turton mailto:ijtur...@gmail.com>> wrote: I think if we set it to auto it should spot for them and convert back. I'd need to resurrect my windows machine to check though, And we'd need to work out all the binary file endings we'd need to protect. Is there a way to list the ones we want the setting to act on instead? The list would seem more simple/obvious (java, rst, txt, sld, xml, ftl, maybe jfl) Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] [Geoserver-devel] API changes to add AutoCloseable for try-with-resources
Ben, Something to potentially consider regarding interfaces; While changing the signatures of existing interfaces will break the API, you could do one of two things: 1. copy the current interface wholesale and change the name to include a digit i.e. MyInterface => MyInterface1 Where the new interface name has the updated signature/implements. Implementations of the interface can then change to implement the newly name one, while existing implementations continue to work against the original interface. The original interface can be marked as "@Deprecated use interface " and eventually removed altogether. 2. create a new interface that extends the original interface adding the additional changes. This also uses the same process for implementation classes, but has the downside of NOT being able to deprecate/remove the original names if desired. Anyway, something to consider. Chris Snider Senior Software Engineer -Original Message- From: Ben Caradoc-Davies [mailto:b...@transient.nz] Sent: Monday, June 04, 2018 5:25 PM To: GeoTools Devel ; Geoserver-devel Subject: [Geoserver-devel] API changes to add AutoCloseable for try-with-resources Many interfaces in GeoTools and GeoServer use the Dispose pattern, often with a dispose() method, but do not implement AutoCloseable, preventing their use in a try-with-resources statement. Examples range from ImageReader to DataStore/DataAccess. Some interfaces like FeatureReader already implement Closeable and thus AutoCloseable, but many do not. Java 7 try-with-resources improves code quality because it simplifies code by automating common boilerplate: https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html https://docs.oracle.com/javase/8/docs/api/java/lang/AutoCloseable.html Adding AutoCloseable to an interface is an API-breaking change because third-party subclasses that do not implement a close() method will no longer compile. Any change would be applied only to master and would target GeoTools 20.0 and GeoServer 2.14.0. - Should we add AutoCloseable to interfaces, and if so which ones? We could make a list. - Do we make the change one interface at a time or try to do them all at once? - Should we rename dispose() to close() in implementers and add a deprecated dispose() that wraps close(), or just add a close() that wraps dispose()? - As we are breaking the API anyway, should we get rid of dispose() entirely by renaming it to close() without adding a deprecated wrapper? - I thought of updating only interfaces and overrides. A more ambitious scope would find every deprecated dispose() and refactor to use try-with-resources. The alternative is to refactor incrementally over time. How do we wish to pay off our technical debt? - Who is interested in participating in this work? Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited <https://transient.nz/> New Zealand -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Geoserver-devel mailing list geoserver-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] subscribe
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
