[Geoserver-devel] Jenkins build is back to normal : geoserver-master #5563

[monitor]

See 


--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-master #5562

[monitor]

See 

--
[...truncated 538.58 KB...]
[INFO] 
[INFO] Skipping GeoServer INSPIRE Extensions
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Ysld GeoServer Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer CSS Styling
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Application Schema Integration Test
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Core Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS NetCDF output Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI JDBC Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI LDAP Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer Security Extension Modules
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Catalog Services for the Web core module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Core Monitor Extension
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping OGR WPS
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web process status sharing with Hazelcast
[INFO] This project has been banned from the build due 

[Geoserver-devel] GWC API changes and beta release date

[Torben Barsballe]

We have been working on the GeoWebCache Configuration API changes and REST
improvements discussed here
 and here
 for the
last while, in an attempt to get them in before the code freeze.

We are now nearly done (GWC PR here:
https://github.com/GeoWebCache/geowebcache/pull/593 , GS PR pending ), but
discovered a last-minute error in the CompositeBlobStore behaviour. In
order to fix this and get it into the upcoming beta, we would like to *ask
to potentially push back the beta release date by up to a day* (So,
Tuesday, Feb 20th, rather than the 19th).

I'm the one who is actually releasing the beta; does anyone else have any
objections?

Torben
--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

[Torben Barsballe]

First of all, the change seems reasonable, so +1 there.

I have no issues with applying these changes right away for the beta
release next week, and we can do a GSIP later. I'll also update the release
docs while I do the release.

Torben

On Fri, Feb 16, 2018 at 8:30 AM, Andrea Aime 
wrote:

> On Fri, Feb 16, 2018 at 4:18 AM, Ben Caradoc-Davies 
> wrote:
>
>> +1. It does seem that we are not getting much benefit from waiting until
>> RC to branch, and any fix would be applied to master and the new stable
>> before the .0 release. We could drop the RC altogether. The current
>> procedure incurs not only a delay but also the work of an extra release
>> (the RC).
>>
>
> As far as I remember there are just Jukka (and sometimes Brad too?)
> testing betas/RC and providing timely feedback, so yeah,
> I guess that for a single person the beta should suffice :-)
>
> This is a larger change to the release procedures, I guess we need a
> GSIP... Torben, you are the release
> manager for the beta, how do you feel about a "shortcut", apply these
> changes right away if there are
> no complaints and do a GSIP later?
>
> 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 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
>
--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP 165 - Add isolated workspaces concept to GeoServer, quick vote :)

[Nuno Oliveira]

Hi all,

Thanks all for the feedback and quick voting, much appreciated :)

The pull requests has been reviewed and its suggestions applied:
https://github.com/geoserver/geoserver/pull/2746

Cheers,

Nuno Oliveira

On 02/13/2018 01:40 PM, Nuno Oliveira wrote:

Hi all,

You may remember a few discussions going on in the mailing list regarding 
isolated workspaces:

  * https://sourceforge.net/p/geoserver/mailman/message/35658017
  * https://sourceforge.net/p/geoserver/mailman/message/36097736

It seems that all concerns were addressed, to everyone's satisfaction. This 
change was also
discussed in GeoServer PSC meeting, Nov 14th 2017 and no major concerns were 
raised.

It stills not clear to me if this requires a formal proposal or not (bug fix \ 
new functionality ?)
but since this will be implemented in a core module of GeoServer I decided to 
go ahead
and create a formal proposal for it:

  * 
https://github.com/geoserver/geoserver/wiki/GSIP-165---Add-isolated-workspaces-concept-to-GeoServer

The changes are small, isolated and fully backward compatible. Users will not be affected by this 
unless they
use this functionally and external code depending on GeoServer (third parts modules, etc ...) will 
not be

affected by this either.

My apologies for writing the proposal late, I would like this change to land on the upcoming 
release (2.13-beta)

... and the code freeze is coming (February 18th), so I will gently ask for a 
quick vote on this one.

Wondering, isolated workspaces have already be deeply discussed in the mailing list so I don't 
expect any
major concern to be raised now, if the proposal don't get any -1 until the code freeze can the 
code be merged ?


Cheers,

Nuno Oliveira
--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visithttp://goo.gl/it488V  
for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:  +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne 
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di 
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro 
sistema. Conservare il messaggio stesso, divulgarlo anche in parte, 
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, 
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
  
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.



--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:  +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora 

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

[Andrea Aime]

On Fri, Feb 16, 2018 at 11:44 AM, Ian Turton  wrote:

> I agree we hardly ever see any feedback before the .0 release. Which is a
> shame but nothing we do seems to make a difference to customers.
>

Ah hem, "users" :-p

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

[Jody Garnett]

We could also cut the beta just to confirm master is releasable, and not
branch. Make the first release candidate the branch to achieve the same
effect.

It has the advantage of less moving parts, but we do not get a code freeze
to focus on bugs. But as you point out that is not happening so much.
On Fri, Feb 16, 2018 at 2:45 AM Ian Turton  wrote:

> I agree we hardly ever see any feedback before the .0 release. Which is a
> shame but nothing we do seems to make a difference to customers.
>
> So +1 for me
>
> Ian
>
> On 16 February 2018 at 09:32, Nuno Oliveira <
> nuno.olive...@geo-solutions.it> wrote:
>
>> I don't have any voting power, just want to express my +1 towards that
>> change ... and indeed I don't see the advantage of the RC release.
>> If users don't provide feedback, bug fix doesn't happen ... what are the
>> advantages of having the RC release ?
>>
>>
>> On 02/16/2018 03:18 AM, Ben Caradoc-Davies wrote:
>>
>>> +1. It does seem that we are not getting much benefit from waiting until
>>> RC to branch, and any fix would be applied to master and the new stable
>>> before the .0 release. We could drop the RC altogether. The current
>>> procedure incurs not only a delay but also the work of an extra release
>>> (the RC).
>>>
>>> Kind regards,
>>> Ben.
>>>
>>> On 14/02/18 22:58, Andrea Aime wrote:
>>>
 Hi (apologies for the cross post),
 I would like to hear opinions on changing the release procedures
 slightly,
 and cutting the stable
 branch directly on the beta release.

 The reason for not doing the cut on beta but on RC originally was to
 push
 devs to concentrate
 on bug fixing.
 However, since then we have shortened the beta life to just two weeks,
 we
 are not getting significant
 feedback from users (which typically starts flowing in on .0 or even .1
 releases), and the bug fixing activity
 is rather small (I try to do it anyways, but find myself fixing old
 bugs,
 not new ones).

 I've also noticed that I routinely created short lived forks of master
 to
 keep on working on my daily job.
 Wondering, am I the only one?

 If not, or if others don't mind anyways, wouldn't it be better to just
 cut
 the stable branch on beta instead?

 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

 AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

 Le informazioni contenute in questo messaggio di posta elettronica e/o
 nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
 loro utilizzo è consentito esclusivamente al destinatario del messaggio,
 per le finalità indicate nel messaggio stesso. Qualora riceviate questo
 messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
 darcene notizia via e-mail e di procedere alla distruzione del messaggio
 stesso, cancellandolo dal Vostro sistema. Conservare il messaggio
 stesso,
 divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
 utilizzarlo per finalità diverse, costituisce comportamento contrario ai
 principi dettati dal D.Lgs. 196/2003.

 The information in this message and/or attachments, is intended solely
 for
 the attention and use of the named addressee(s) and may be confidential
 or
 proprietary in nature or covered by the provisions of privacy act
 (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
 Code).Any use not in accord with its purpose, any disclosure,
 reproduction,
 copying, distribution, or either dissemination, either whole or
 partial, is
 strictly forbidden except previous formal approval of the named
 addressee(s). If you are not the intended recipient, please contact
 immediately the sender by telephone, fax or e-mail and delete the
 information in this message that has been received in error. The sender
 does not give any warranty or accept liability as the content, accuracy
 or
 completeness of sent messages and accepts no responsibility  for changes
 made after they were sent or for other risks which arise as a result of
 e-mail transmission, viruses, etc.




 --
 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
 

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

[Andrea Aime]

On Fri, Feb 16, 2018 at 4:18 AM, Ben Caradoc-Davies 
wrote:

> +1. It does seem that we are not getting much benefit from waiting until
> RC to branch, and any fix would be applied to master and the new stable
> before the .0 release. We could drop the RC altogether. The current
> procedure incurs not only a delay but also the work of an extra release
> (the RC).
>

As far as I remember there are just Jukka (and sometimes Brad too?) testing
betas/RC and providing timely feedback, so yeah,
I guess that for a single person the beta should suffice :-)

This is a larger change to the release procedures, I guess we need a
GSIP... Torben, you are the release
manager for the beta, how do you feel about a "shortcut", apply these
changes right away if there are
no complaints and do a GSIP later?

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GeoServer Importer maximum running jobs

[Lorenzo Pini]

Dear all,
I'm using the GeoServer importer and I noticed I can start as many sessions
I want without receiving an error. Some of the sessions will simply go back
to a "ready" state without having effect.

After a little digging I foung this class:
https://github.com/geoserver/geoserver/blob/master/src/extension/importer/core/src/main/java/org/geoserver/importer/job/JobQueue.java

If I understand it correctly, the queue it's not actually queueing
anything, it's a direct handoff, so the jobs will be executed immediatly
until the thread pool reaches its maximum size.
And since the maximum pool size is Integer.MAX_VALUE I guess I should not
start too many sessions at once.

If my findings are correct I'm going to open a JIRA to make the maximum
number of concurrent jobs configurable.

What do you think?

Thank you

Regards,
Lorenzo Pini
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Lorenzo Pini
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:  +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel