Re: [Geoserver-devel] GeoServer 2.16.1 release train reminder

2019-11-27 Thread Andrea Aime 
Hi Jody,
that works fine for me

Cheers
Andrea


On Wed, Nov 27, 2019 at 8:33 AM Jody Garnett  wrote:

> How does this sound:
>
> *Note: Our builds detected a change in Oracle JDK 8u221 URL handling, this
> release was made with 8u202 as a result. Future releases will be made using
> OpenJDK.*
> --
> Jody Garnett
>
>
> On Wed, 27 Nov 2019 at 06:35, Jody Garnett  wrote:
>
>> Thanks Jukka,
>>
>> The application runs fine of macOS.
>>
>> Given the build problems about OpenJDK vs OracleJDK and discussion in
>> yesterday's meeting I think I should add a comment to the release
>> announcement about Java 8u221 changing the handling of URLs.
>>
>>
>> On Tue, Nov 26, 2019 at 11:57 AM Rahkonen Jukka (MML) <
>> jukka.rahko...@maanmittauslaitos.fi> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> Bin-zip tested on Windows, runs and sends GetCapabilities for all the
>>> services and layer preview is OK.
>>>
>>>
>>>
>>> -Jukka-
>>>
>>>
>>>
>>> *Lähettäjä:* Jody Garnett 
>>> *Lähetetty:* maanantai 25. marraskuuta 2019 6.30
>>> *Vastaanottaja:* Gabriel Roldan 
>>> *Kopio:* GeoServer ; Andrea Aime
>>> 
>>> *Aihe:* Re: [Geoserver-devel] GeoServer 2.16.1 release train reminder
>>>
>>>
>>>
>>> Once again ask folks to review blog post, and test the release artifacts
>>> above.
>>>
>>> (I will be in a position to test mid-week)
>>>
>>> --
>>>
>>> Jody Garnett
>>>
>>>
>>>
>>>
>>>
>>> On Thu, 21 Nov 2019 at 17:58, Jody Garnett 
>>> wrote:
>>>
>>> Initial release artifacts are reading for testing:
>>>
>>>
>>>
>>>
>>> https://build.geoserver.org/view/release/job/geoserver-release/261/artifact/distribution/2.16.1
>>>
>>>
>>>
>>> I expect to release Friday (after folks have had a chance to try out the
>>> above and review the blog posts)
>>>
>>> --
>>>
>>> Jody Garnett
>>>
>>>
>>>
>>>
>>>
>>> On Wed, 20 Nov 2019 at 21:37, Jody Garnett 
>>> wrote:
>>>
>>> I am currently working on the geotools build, here are the details for
>>> the upcoming release.
>>>
>>>
>>>
>>> GeoServer* 2.16.1*
>>>
>>>- revision: 3d2f9ae04399e37dd8ba381436707d8eb85cafa0
>>>- jira:
>>>
>>> https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=1&version=16769
>>>- blog:
>>>http://blog.geoserver.org/wp-admin/post.php?post=3074&action=edit
>>>
>>> Blog draft is ready for review, I have included stock headings for
>>> security updates / community updates / About 2.16 Series sections which I
>>> hope we can recycle each time.
>>>
>>> --
>>>
>>> Jody Garnett
>>>
>>>
>>>
>>>
>>>
>>> On Wed, 20 Nov 2019 at 11:27, Gabriel Roldan 
>>> wrote:
>>>
>>> Jody, let it slip till next release, don't even waste your time.
>>>
>>>
>>>
>>> (btw, the npe was a newly introduced issue of my own, the clean up of
>>> null checks is good and verified they were testing for nulls that couldn't
>>> happen inside the internal code, not user input of any kind)
>>>
>>>
>>>
>>> On Wed, 20 Nov 2019 at 14:59, Jody Garnett 
>>> wrote:
>>>
>>> Gabriel my testing was fine, but I admit to being somewhat hesitant
>>> given fernando's recent trouble.
>>>
>>>
>>>
>>> I understand you wanting to clean up code. The strategy of removing null
>>> checks that should not happen is always risky (for when they happen).
>>>
>>> --
>>>
>>> Jody Garnett
>>>
>>>
>>>
>>>
>>>
>>> On Mon, 18 Nov 2019 at 10:34, Jody Garnett 
>>> wrote:
>>>
>>> I will test myself locally and get back to you.
>>>
>>> --
>>>
>>> Jody Garnett
>>>
>>>
>>>
>>>
>>>
>>> On Mon, 18 Nov 2019 at 06:20, Gabriel Roldan 
>>> wrote:
>>>
>>> Hi all,
>>>
>>>
>>>
>>> re-issued GEOS-9191 pr[1] with new test cases to cover the issue that
>>> forced us to revert the other one.
>>>
>>> I'll leave it to you, Jody, to decide whether to include the 2.16.x
>>> backport on this release. IMHO it should be safe, and I tested manually
>>> with a data directory that has no gwc-layers directory with and without the
>>> fix commit and it seems all good.
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Gabriel
>>>
>>>
>>>
>>> [1] https://github.com/geoserver/geoserver/pull/3909
>>>
>>> [2]
>>> https://github.com/geoserver/geoserver/pull/3909/commits/65cc9227b7a9138edb9313784d53e4c718158958
>>>
>>>
>>>
>>>
>>>
>>> On Mon, 18 Nov 2019 at 05:16, Andrea Aime 
>>> wrote:
>>>
>>> Reminder 2, 2.16.1 is a stable series release, so careful about what you
>>> backport
>>>
>>> only a few days before the release
>>>
>>>
>>>
>>> Cheers
>>>
>>> Andrea
>>>
>>>
>>>
>>> On Mon, Nov 18, 2019 at 6:38 AM Jody Garnett 
>>> wrote:
>>>
>>> The GeoServer 2.16.2 release is scheduled
>>>  for this
>>> week. If you have any fixes or pull requests this is your reminder :)
>>>
>>> --
>>>
>>> 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://goo.gl/it488V for

Re: [Geoserver-devel] GeoServer 2.16.1 release train reminder - blog login

2019-11-27 Thread Peter Smythe 
Hi guys

I'm not sure that my previous email was received by the list, so I'm asking
again, hoping to find the WordPress administrator for the GeoServer blog -
who would that be?

> How can I get a WP login, so that I can help to review the blog post?

Regards

Peter


On Mon, 25 Nov 2019 at 10:56, Peter Smythe  wrote:

> Hi Jody
>
> How can I get a WP login, so that I can help to review the blog post?
>
> Regards
>
> On Mon, 25 Nov 2019 at 06:32, Jody Garnett  wrote:
>
>> Once again ask folks to review blog post, and test the release artifacts
>> above.
>> (I will be in a position to test mid-week)
>> --
>> Jody Garnett
>>
>>
>> On Thu, 21 Nov 2019 at 17:58, Jody Garnett 
>> wrote:
>>
>>> Initial release artifacts are reading for testing:
>>>
>>>
>>> https://build.geoserver.org/view/release/job/geoserver-release/261/artifact/distribution/2.16.1
>>>
>>>
>>> I
>>> expect to release Friday (after folks have had a chance to try out the
>>> above and review the blog posts)
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Wed, 20 Nov 2019 at 21:37, Jody Garnett 
>>> wrote:
>>>
 I am currently working on the geotools build, here are the details for
 the upcoming release.

 GeoServer* 2.16.1*

- revision: 3d2f9ae04399e37dd8ba381436707d8eb85cafa0
- jira:

 https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=1&version=16769
- blog:
http://blog.geoserver.org/wp-admin/post.php?post=3074&action=edit

 Blog draft is ready for review, I have included stock headings for
 security updates / community updates / About 2.16 Series sections which I
 hope we can recycle each time.
 --
 Jody Garnett


 On Wed, 20 Nov 2019 at 11:27, Gabriel Roldan 
 wrote:

> Jody, let it slip till next release, don't even waste your time.
>
> (btw, the npe was a newly introduced issue of my own, the clean up of
> null checks is good and verified they were testing for nulls that couldn't
> happen inside the internal code, not user input of any kind)
>
> On Wed, 20 Nov 2019 at 14:59, Jody Garnett 
> wrote:
>
>> Gabriel my testing was fine, but I admit to being somewhat hesitant
>> given fernando's recent trouble.
>>
>> I understand you wanting to clean up code. The strategy of removing
>> null checks that should not happen is always risky (for when they 
>> happen).
>> --
>> Jody Garnett
>>
>>
>> On Mon, 18 Nov 2019 at 10:34, Jody Garnett 
>> wrote:
>>
>>> I will test myself locally and get back to you.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Mon, 18 Nov 2019 at 06:20, Gabriel Roldan <
>>> gabriel.rol...@gmail.com> wrote:
>>>
 Hi all,

 re-issued GEOS-9191 pr[1] with new test cases to cover the issue
 that forced us to revert the other one.
 I'll leave it to you, Jody, to decide whether to include the 2.16.x
 backport on this release. IMHO it should be safe, and I tested manually
 with a data directory that has no gwc-layers directory with and 
 without the
 fix commit and it seems all good.

 Cheers,
 Gabriel

 [1] https://github.com/geoserver/geoserver/pull/3909
 [2]
 https://github.com/geoserver/geoserver/pull/3909/commits/65cc9227b7a9138edb9313784d53e4c718158958


 On Mon, 18 Nov 2019 at 05:16, Andrea Aime <
 andrea.a...@geo-solutions.it> wrote:

> Reminder 2, 2.16.1 is a stable series release, so careful about
> what you backport
> only a few days before the release
>
> Cheers
> Andrea
>
> On Mon, Nov 18, 2019 at 6:38 AM Jody Garnett <
> jody.garn...@gmail.com> wrote:
>
>> The GeoServer 2.16.2 release is scheduled
>> 
>> for this week. If you have any fixes or pull requests this is your 
>> reminder
>> :)
>> --
>> 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://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
> ---

[Geoserver-devel] [JIRA] (GEOS-9413) Support MBTiles with vector tiles, for rendering purposes

2019-11-27 Thread Andrea Aime (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
  Andrea Aime  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9413  
 
 
  Support MBTiles with vector tiles, for rendering purposes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 27/Nov/19 12:05 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Andrea Aime   
 

  
 
 
 
 

 
 New ability in the mbtiles module, extra docs and a separate assembly that does involve the wms output format and WPS process, both dangerous for the server stability (no limits).  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS 
  
 
 
 This message was sent by Atlassian Jira (v

Re: [Geoserver-devel] Considering scrapping the GeoServer mbtiles community module, or making a separate assembly just for the store

2019-11-27 Thread Andrea Aime 
On Mon, Nov 25, 2019 at 10:13 PM Jody Garnett 
wrote:

> Can I ask who the maintainer is? The pom.xml does not say, checking
> history I see Niels and Justin as some of the initial commits.
>
> I would recommend a separate community module.
>

So I've created a separate assembly for the store, updated docs, and added
warnings about using the WMS or WPS outputs,
as they cannot be currently time limited:

https://github.com/geoserver/geoserver/pull/3918

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.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-9414) web-app jar is larger than expected

2019-11-27 Thread Jody Garnett (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
  Jody Garnett  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9414  
 
 
  web-app jar is larger than expected   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.16.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 web-app  
 
 
Created: 
 27/Nov/19 12:30 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Jody Garnett   
 

  
 
 
 
 

 
 web-app was changed from a WAR to a JAR in part to save space in our repository and provide a small dependency for those making a custom application. 
 
https://repo.boundlessgeo.com/artifactory/release/org/geoserver/web/gs-web-app/2.16.0/ 
 However the jar appears to contain more than is expected and is 105 MB. 
 
META-INF/ 
WEB-INF/dispatcher-servlet.xml 
WEB-INF/web.xml 
WEB-INF/lib - contains all dependencies 
data/ contains release data directory 
 Questions: 
 
Q: Is the lib folder required? The pom already lists these dependencies 
Q: Is the data folder required?

[Geoserver-devel] [JIRA] (GEOS-9415) Importer is not able to ingest correctly KML geometries anymore

2019-11-27 Thread Alessio Fabiani (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
  Alessio Fabiani  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9415  
 
 
  Importer is not able to ingest correctly KML geometries anymore   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.15.2, 2.15.3, 2.16.0, 2.16.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Importer  
 
 
Created: 
 27/Nov/19 4:23 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Alessio Fabiani   
 

  
 
 
 
 

 
 Trying to import a plain KML file through the GeoServer Importer, results on an empty layer and, therefore, an empty BBOX.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

Re: [Geoserver-devel] GeoServer 2.16.1 release train reminder

2019-11-27 Thread Jody Garnett 
It looks like I can add you, thanks for offering to review.
--
Jody Garnett


On Mon, 25 Nov 2019 at 09:56, Peter Smythe  wrote:

> Hi Jody
>
> How can I get a WP login, so that I can help to review the blog post?
>
> Regards
>
> On Mon, 25 Nov 2019 at 06:32, Jody Garnett  wrote:
>
>> Once again ask folks to review blog post, and test the release artifacts
>> above.
>> (I will be in a position to test mid-week)
>> --
>> Jody Garnett
>>
>>
>> On Thu, 21 Nov 2019 at 17:58, Jody Garnett 
>> wrote:
>>
>>> Initial release artifacts are reading for testing:
>>>
>>>
>>> https://build.geoserver.org/view/release/job/geoserver-release/261/artifact/distribution/2.16.1
>>>
>>>
>>> I
>>> expect to release Friday (after folks have had a chance to try out the
>>> above and review the blog posts)
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Wed, 20 Nov 2019 at 21:37, Jody Garnett 
>>> wrote:
>>>
 I am currently working on the geotools build, here are the details for
 the upcoming release.

 GeoServer* 2.16.1*

- revision: 3d2f9ae04399e37dd8ba381436707d8eb85cafa0
- jira:

 https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=1&version=16769
- blog:
http://blog.geoserver.org/wp-admin/post.php?post=3074&action=edit

 Blog draft is ready for review, I have included stock headings for
 security updates / community updates / About 2.16 Series sections which I
 hope we can recycle each time.
 --
 Jody Garnett


 On Wed, 20 Nov 2019 at 11:27, Gabriel Roldan 
 wrote:

> Jody, let it slip till next release, don't even waste your time.
>
> (btw, the npe was a newly introduced issue of my own, the clean up of
> null checks is good and verified they were testing for nulls that couldn't
> happen inside the internal code, not user input of any kind)
>
> On Wed, 20 Nov 2019 at 14:59, Jody Garnett 
> wrote:
>
>> Gabriel my testing was fine, but I admit to being somewhat hesitant
>> given fernando's recent trouble.
>>
>> I understand you wanting to clean up code. The strategy of removing
>> null checks that should not happen is always risky (for when they 
>> happen).
>> --
>> Jody Garnett
>>
>>
>> On Mon, 18 Nov 2019 at 10:34, Jody Garnett 
>> wrote:
>>
>>> I will test myself locally and get back to you.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Mon, 18 Nov 2019 at 06:20, Gabriel Roldan <
>>> gabriel.rol...@gmail.com> wrote:
>>>
 Hi all,

 re-issued GEOS-9191 pr[1] with new test cases to cover the issue
 that forced us to revert the other one.
 I'll leave it to you, Jody, to decide whether to include the 2.16.x
 backport on this release. IMHO it should be safe, and I tested manually
 with a data directory that has no gwc-layers directory with and 
 without the
 fix commit and it seems all good.

 Cheers,
 Gabriel

 [1] https://github.com/geoserver/geoserver/pull/3909
 [2]
 https://github.com/geoserver/geoserver/pull/3909/commits/65cc9227b7a9138edb9313784d53e4c718158958


 On Mon, 18 Nov 2019 at 05:16, Andrea Aime <
 andrea.a...@geo-solutions.it> wrote:

> Reminder 2, 2.16.1 is a stable series release, so careful about
> what you backport
> only a few days before the release
>
> Cheers
> Andrea
>
> On Mon, Nov 18, 2019 at 6:38 AM Jody Garnett <
> jody.garn...@gmail.com> wrote:
>
>> The GeoServer 2.16.2 release is scheduled
>> 
>> for this week. If you have any fixes or pull requests this is your 
>> reminder
>> :)
>> --
>> 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://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 “

Re: [Geoserver-devel] reminder: geoserver cite automation proposals due next week

2019-11-27 Thread Gabriel Roldan 
Hey all,

just an FYI I've all intents to send a proposal as an independent
contractor, just waiting until next week once I'm more relieved from my
current project, since it looks I'd need to gather some more insights on
the current state of affairs and think of what a possible solution could be.

Cheers,
Gabriel.

On Sun, 24 Nov 2019 at 20:52, Jody Garnett  wrote:

> Interested parties are asked to send their proposal to geoserver-devel
> email list next week.
>
> For more information: CITE Test Automation Request for Proposal
> 
>
> Thanks again to Gaia3D, OSGeo:UK and everyone who has sponsored or donated
> to make this activity possible.
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] reminder: geoserver cite automation proposals due next week

2019-11-27 Thread Andrea Aime 
Hi Jody,
busy times around here, we hope to send a proposal mid next week

Cheers
Andrea


On Mon, Nov 25, 2019 at 12:53 AM Jody Garnett 
wrote:

> Interested parties are asked to send their proposal to geoserver-devel
> email list next week.
>
> For more information: CITE Test Automation Request for Proposal
> 
>
> Thanks again to Gaia3D, OSGeo:UK and everyone who has sponsored or donated
> to make this activity possible.
> --
> 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://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.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-9416) Use OpenJDK for release builds instead of Oracle

2019-11-27 Thread Torben Barsballe (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
  Torben Barsballe  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9416  
 
 
  Use OpenJDK for release builds instead of Oracle   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 27/Nov/19 10:10 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Torben Barsballe   
 

  
 
 
 
 

 
 GeoServer has historically used Oracle Java for building release artifacts.  There have been some recent issues with the availability of certain version of Oracle Java on Jenkins, possibly due to [https://issues.jenkins-ci.org/browse/JENKINS-57090JENKINS-57090) This, coupled with the increasing popularity OpenJDK over Oracle suggests we should use OpenJDK instead (or at least use it as the default - we can still keep the Oracle installer and have it as an option). Tasks: 
 
Update release scripts / defaults to match OpenJDK 8 version numbers 
Update Jenkins config for release jobs with correct version numbers 
  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment