Re: [Geoserver-devel] GeoServer releases: no more OSX installers?

[Andrea Aime]

On Fri, Feb 23, 2018 at 7:51 AM, Jody Garnett 
wrote:

> The GeoServer project does have some budget. We could also put in a
> request to SAC to host a Mac mini for us and provide Jenkins '/ shell
> access.
>

A OSGeo hosted mac holding the (preciou!) OSGeo certificate would seem
like a good match indeed :-)

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] GeoServer releases: no more OSX installers?

[Jody Garnett]

The GeoServer project does have some budget. We could also put in a request
to SAC to host a Mac mini for us and provide Jenkins '/ shell access.

--
Jody Garnett

On 22 February 2018 at 11:08, Torben Barsballe 
wrote:

> So, this topic has come up before, when the OS X build server was still
> usable but to be deprecated in "the near future". We didn't have too much
> luck on executing on a good solution then.
>
> My thoughts:
>
>- Dropping the installer would not be the end of the world, but should
>still be a last resort. The system independent binary runs fine on OS X
>(and Java is generally installed by default). If we go this route, we need
>to be sure to update the install instructions
>.
>- If we can get some OSGeo funding for a mac build server that
>definitely seems like the best option.
>- Someone manually building the installers seems like a good way to
>get a mac installer only on some releases and not on others (due to
>availability or lack thereof), which almost seems worse from a user
>perspective then not building the installer at all. I feel like we would
>want at least two volunteers if we were to seriously consider this option.
>
> I also have a suggestion for a fourth option:
>
>- If we are okay with an unsigned installer, I have heard there is a
>way of spinning up a OS X build box on demand via Travis CI; this might be
>a easy way of generating the OS X artifacts. I don't know much more about
>this, but this looks like it could be another option.
>
>
> Torben
>
>
> On Tue, Feb 20, 2018 at 1:08 AM, Andrea Aime  > wrote:
>
>> Hi,
>> after a chat on gitter yesterday it seems clear 2.11.5 and 2.13-beta will
>> not have a OSX installer.
>>
>> The OSX build server that was used to build the installers is gone, and
>> in order to build a signed
>> installer one needs to get a hold of OSGeo certificate, which requires
>> some procedure and control
>> to be given out.
>>
>> So, options coming to mind:
>>
>>- We simply drop the installer?
>>- Can we use OSGeo funding to get a build server going again? Looks
>>like the are some "reasonably" priced options here:
>>https://portal.macincloud.com/select/#/plans
>>
>>- Can we get a volunteer that will build the installer manually every
>>month? Can we go with an unsigned installer, or will we find someone 
>> that's
>>willing and trusted enough to get a hold of the OSGeo certificate?
>>
>> Ideas? Anyone interested in volunteering?
>>
>> 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 <+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.
>>
>>
>> 

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

[monitor]

See 


Changes:

[tbarsballe] Updated version to 2.14-SNAPSHOT, updated GeoTools dependency to

--
[...truncated 10.83 MB...]
Feb 20, 2018 10:32:49 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 20, 2018 10:32:50 PM org.geoserver.importer.Importer copyFromFeatureReader
INFO: load to target took 41
Feb 20, 2018 10:32:51 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 20, 2018 10:32:51 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 20, 2018 10:32:53 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 20, 2018 10:32:53 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.727 sec

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources) @ 
gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2.1:test-jar-no-fork (attach-sources) @ 
gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ gs-importer-web 
---
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT.pom
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-tests.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-sources.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] 
[INFO] Building GeoServer CAS Security Web Module 2.14-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gs-web-sec-cas ---
[INFO] Deleting 

[INFO] 
[INFO] --- git-commit-id-plugin:2.1.15:revision (default) @ gs-web-sec-cas ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
gs-web-sec-cas ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory 

[INFO] 
[INFO] --- 

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

[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] Bug Stomp Friday

[Torben Barsballe]

The last Friday of the month is upon us again, so it is time for the
GeoServer Bug Stomp. As a reminder, the 2.13-beta was just released
, so if
anyone wants to test/bugfix the beta, that is something that would be
appreciated.

Gitter: https://gitter.im/geoserver/geoserver

Sprint Jira issues:

[sprint tickets]
https://osgeo-org.atlassian.net/issues/?filter=11300

Most recent sprint tickets (Open or Reopened):
https://osgeo-org.atlassian.net/issues?jql=project%20in%20(G
EOS%2C%20GEOT)%20AND%20status%20in%20(Open%2C%20Reopened)%20
AND%20Triage%20%3D%20sprint%20ORDER%20BY%20created%20DESC
--
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-app-schema-online #1083

[monitor]

See 


Changes:

[tbarsballe] Update doc pom to 2.14-SNAPSHOT

[Alessio Fabiani]  - Remove verbose exception from notification community module

[tbarsballe] One more doc pom update to 2.14-SNAPSHOT

[Alessio Fabiani] [Notification comunity plugin] - Wrap NPE

--
[...truncated 859 B...]
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1384ed585d5c02597d030575dde552bc9b378107
 > git rev-list d1a9378bc354313a2a480b546dc1c2575cec62af # timeout=10
[geoserver-master-app-schema-online] $ /bin/sh -xe 
/tmp/jenkins7832436230736353314.sh
+ mkdir /var/jenkins/.geoserver
mkdir: cannot create directory `/var/jenkins/.geoserver': File exists
+ true
+ rm /var/jenkins/.geotools/postgis.properties
+ rm /var/jenkins/.geotools/oracle.properties
rm: cannot remove `/var/jenkins/.geotools/oracle.properties': No such file or 
directory
+ true
+ rm /var/jenkins/.geoserver/postgis.properties
+ rm /var/jenkins/.geoserver/oracle.properties
rm: cannot remove `/var/jenkins/.geoserver/oracle.properties': No such file or 
directory
+ true
+ set +x
CREATE FUNCTION
CREATE FUNCTION
DELETE 0
INSERT 0 1
 srid 
--
 4979
(1 row)

[geoserver-master-app-schema-online] $ mvn -f src/extension/app-schema/pom.xml 
-B -Dtest.maxHeapSize=1024m -Dtest.maxPermSize=128m -fae 
-Papp-schema-online-test -pl !app-schema-oracle-test,!app-schema-mongo-test 
-Djava.io.tmpdir=/mnt/memtmp clean test
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Application Schema Support
[INFO] Application Schema Integration Test
[INFO] Sample DataAccess Integration Test
[INFO] Application Schema Integration Online Test with Postgis Database
[INFO] 
[INFO] 
[INFO] Building Application Schema Support 2.14-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gs-app-schema ---
[INFO] 
[INFO] --- git-commit-id-plugin:2.1.15:revision (default) @ gs-app-schema ---
[INFO] 
[INFO] 
[INFO] Building Application Schema Integration Test 2.14-SNAPSHOT
[INFO] 
[INFO] Downloading: 
https://repo.boundlessgeo.com/main/org/geoserver/gs-main/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://download.osgeo.org/webdav/geotools/org/geoserver/gs-main/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://maven.geo-solutions.it/org/geoserver/gs-main/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
https://repo.boundlessgeo.com/main/org/geoserver/gs-main/2.14-SNAPSHOT/gs-main-2.14-SNAPSHOT.pom
[INFO] Downloading: 
http://download.osgeo.org/webdav/geotools/org/geoserver/gs-main/2.14-SNAPSHOT/gs-main-2.14-SNAPSHOT.pom
[INFO] Downloading: 
http://maven.geo-solutions.it/org/geoserver/gs-main/2.14-SNAPSHOT/gs-main-2.14-SNAPSHOT.pom
[WARNING] The POM for org.geoserver:gs-main:jar:2.14-SNAPSHOT is missing, no 
dependency information available
[WARNING] The POM for org.geoserver:gs-main:jar:tests:2.14-SNAPSHOT is missing, 
no dependency information available
[INFO] Downloading: 
https://repo.boundlessgeo.com/main/org/geoserver/gs-wfs/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://download.osgeo.org/webdav/geotools/org/geoserver/gs-wfs/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://maven.geo-solutions.it/org/geoserver/gs-wfs/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
https://repo.boundlessgeo.com/main/org/geoserver/gs-wfs/2.14-SNAPSHOT/gs-wfs-2.14-SNAPSHOT.pom
[INFO] Downloading: 
http://download.osgeo.org/webdav/geotools/org/geoserver/gs-wfs/2.14-SNAPSHOT/gs-wfs-2.14-SNAPSHOT.pom
[INFO] Downloading: 
http://maven.geo-solutions.it/org/geoserver/gs-wfs/2.14-SNAPSHOT/gs-wfs-2.14-SNAPSHOT.pom
[WARNING] The POM for org.geoserver:gs-wfs:jar:2.14-SNAPSHOT is missing, no 
dependency information available
[INFO] Downloading: 
https://repo.boundlessgeo.com/main/org/geoserver/gs-wms/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://download.osgeo.org/webdav/geotools/org/geoserver/gs-wms/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://maven.geo-solutions.it/org/geoserver/gs-wms/2.14-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
https://repo.boundlessgeo.com/main/org/geoserver/gs-wms/2.14-SNAPSHOT/gs-wms-2.14-SNAPSHOT.pom
[INFO] Downloading: 
http://download.osgeo.org/webdav/geotools/org/geoserver/gs-wms/2.14-SNAPSHOT/gs-wms-2.14-SNAPSHOT.pom
[INFO] Downloading: 

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

[monitor]

See 


Changes:

[Alessio Fabiani] [Notification comunity plugin] - Wrap NPE

--
[...truncated 542.17 KB...]
[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] 
[INFO] Skipping GWC 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 Web Coverage Service 2.0 Earth Observation GUI 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] 

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

[Torben Barsballe]

PR's for the associated doc changes here:

   - https://github.com/geotools/geotools/pull/1811
   - https://github.com/geoserver/geoserver/pull/2763

We also have a release process diagram which includes the freeze. While not
critical, that could be updated - does anyone have the source files for it?

Torben

On Mon, Feb 19, 2018 at 8:14 AM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:

>
>
> On Fri, Feb 16, 2018 at 8:47 AM, Jody Garnett 
> wrote:
>
>> 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.
>>
>
> Unless I am misunderstanding you, this is what we do currently - branch on
> the RC. What are you actually suggesting here?
>
> Torben
>
>
>
>> 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
>> 

Re: [Geoserver-devel] GeoServer releases: no more OSX installers?

[Torben Barsballe]

So, this topic has come up before, when the OS X build server was still
usable but to be deprecated in "the near future". We didn't have too much
luck on executing on a good solution then.

My thoughts:

   - Dropping the installer would not be the end of the world, but should
   still be a last resort. The system independent binary runs fine on OS X
   (and Java is generally installed by default). If we go this route, we need
   to be sure to update the install instructions
   .
   - If we can get some OSGeo funding for a mac build server that
   definitely seems like the best option.
   - Someone manually building the installers seems like a good way to get
   a mac installer only on some releases and not on others (due to
   availability or lack thereof), which almost seems worse from a user
   perspective then not building the installer at all. I feel like we would
   want at least two volunteers if we were to seriously consider this option.

I also have a suggestion for a fourth option:

   - If we are okay with an unsigned installer, I have heard there is a way
   of spinning up a OS X build box on demand via Travis CI; this might be a
   easy way of generating the OS X artifacts. I don't know much more about
   this, but this looks like it could be another option.


Torben


On Tue, Feb 20, 2018 at 1:08 AM, Andrea Aime 
wrote:

> Hi,
> after a chat on gitter yesterday it seems clear 2.11.5 and 2.13-beta will
> not have a OSX installer.
>
> The OSX build server that was used to build the installers is gone, and in
> order to build a signed
> installer one needs to get a hold of OSGeo certificate, which requires
> some procedure and control
> to be given out.
>
> So, options coming to mind:
>
>- We simply drop the installer?
>- Can we use OSGeo funding to get a build server going again? Looks
>like the are some "reasonably" priced options here: https://portal.
>macincloud.com/select/#/plans
>- Can we get a volunteer that will build the installer manually every
>month? Can we go with an unsigned installer, or will we find someone that's
>willing and trusted enough to get a hold of the OSGeo certificate?
>
> Ideas? Anyone interested in volunteering?
>
> 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 <+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
>
>

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

[monitor]

See 


Changes:

[tbarsballe] One more doc pom update to 2.14-SNAPSHOT

--
[...truncated 10.83 MB...]
Feb 22, 2018 6:42:36 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 22, 2018 6:42:36 PM org.geoserver.importer.Importer copyFromFeatureReader
INFO: load to target took 23
Feb 22, 2018 6:42:38 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 22, 2018 6:42:38 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 22, 2018 6:42:39 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 22, 2018 6:42:39 PM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.939 sec

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources) @ 
gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2.1:test-jar-no-fork (attach-sources) @ 
gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ gs-importer-web 
---
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT.pom
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-tests.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-sources.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] 
[INFO] Building GeoServer CAS Security Web Module 2.14-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gs-web-sec-cas ---
[INFO] Deleting 

[INFO] 
[INFO] --- git-commit-id-plugin:2.1.15:revision (default) @ gs-web-sec-cas ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
gs-web-sec-cas ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory 

[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 

Re: [Geoserver-devel] [Geowebcache-devel] Version missmatch

[Torben Barsballe]

GeoServer is supposed to be on 2.14 now, and depending on GWC 1.14. GWC
hasn't updated its version on master to match this yet.
We had a bit of a process change with the latest beta (branching on the
beta rather than the RC), and it appears this got left behind. I believe
Kevin is fixing that right now.

Torben

On Thu, Feb 22, 2018 at 6:02 AM, Ian Turton  wrote:

> Well, it does build if you knock GeoServer back to 1.13-SNAPSHOT but I
> don't want to commit that if GWC should have advanced.
>
> Ian
>
> On 22 February 2018 at 13:59, Andrea Aime 
> wrote:
>
>> Hi Ian,
>> I've reported the same problem yesterday on GeoServer's Gitter. Torben
>> inquired with Kevin, no response as of yet.
>> As far as I can see, we are in a un-buildable situation, because master
>> is still claiming version 1.13 right now:
>> https://github.com/GeoWebCache/geowebcache/blob/master/
>> geowebcache/pom.xml
>>
>> (live link, contents will change on updates)
>>
>> Cheers
>> Andrea
>>
>> On Thu, Feb 22, 2018 at 2:52 PM, Ian Turton  wrote:
>>
>>> I'm trying to build GeoServer on master today and it claims not to be
>>> able to find GeoWebCache jars of 1.14-SNAPSHOT vintage. No problem I
>>> thought I'll update GWC and build that, but GWC master is building
>>> 1.13-SNAPSHOT jars.
>>>
>>> So my question is which version number is correct?
>>>
>>> Ian
>>>
>>> --
>>> Ian Turton
>>>
>>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> Geowebcache-devel mailing list
>>> geowebcache-de...@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geowebcache-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 <+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.
>>
>>
>
>
> --
> Ian Turton
>
> 
> --
> 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
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 

Re: [Geoserver-devel] GeoServer 2.13-beta released

[Torben Barsballe]

Thanks for the additions.

Torben

On Thu, Feb 22, 2018 at 1:44 AM, Andrea Aime 
wrote:

> Hi all,
> several new features and improvements were missing from the announcement,
> I've updated it on the blog, please see here:
>
> http://blog.geoserver.org/2018/02/22/geoserver-2-13-beta-released/
>
> Cheers
> Andrea
>
>
> On Thu, Feb 22, 2018 at 1:52 AM, Torben Barsballe <
> tbarsba...@boundlessgeo.com> wrote:
>
>> We are happy to announce the release of GeoServer 2.13-beta
>> .
>> Downloads are available (zip
>> 
>> , war
>> 
>> , and exe
>> )
>> along with docs and extensions.
>>
>> This is a beta release of GeoServer made in conjunction with GeoTools
>> 19-beta.
>>
>> We want to encourage people to test the release thoroughly and report
>> back any issue found. With no further delay, let’s see what’s new, that is,
>> what is there to test!
>> Isolated Workspaces
>>
>> The concept of an “Isolated Workspaces” has been added to GeoServer, to
>> allow for reusing a namespace among multiple workspaces. In particular, an
>> isolated workspace allows reuse of a namespace already used by another
>> workspace, but its resources (layers, styles, etc …) can only be retrieved
>> when using that workspace’s virtual services and will only show up in those
>> virtual service capabilities documents.
>>
>> When reusing a namespace among workspaces, exactly one of those must be
>> non-isolated, and the rest must be isolated; i.e. isolated workspaces have
>> no restrictions in namespaces usage but the existing restrictions still
>> apply for non isolated workspaces.
>>
>> For more details, refer to the original proposal
>> 
>> .
>> GeoWebCache REST API
>>
>> Two new endpoints have been added to the GeoWebCache REST API:
>>
>>- /gwc/rest/blobstores:
>>   - GET /gwc/rest/blobstores for a list of the blobstores
>>   - GET /gwc/rest/blobstores/{blobStoreName} for details about a
>>   single blobstore
>>   - PUT /gwc/rest/blobstores/{blobStoreName} to create or update a
>>   blobstore
>>   - DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
>>- /gwc/rest/gridsets:
>>   - GET /gwc/rest/gridsets for a list of the gridsets
>>   - GET /gwc/rest/gridsets/{gridSetName} for details about a single
>>   gridset
>>   - PUT /gwc/rest/gridsets/{gridSetName} to create or update a
>>   gridset
>>   - DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset
>>
>> API docs for these endpoints will be added to the GeoServer documentation
>> shortly. Until then, the request body syntax for PUT requests closely
>> matched the equivalent structures in geowebcache.xml: BlobStores
>> 
>>  and GridSets
>> 
>> .
>>
>> The ArcGISCache backed layers are now also configurable via the REST API.
>>
>> This release sees a major reworking of the configuration system in
>> GeoWebCache that will allow for plugging in alternate configuration
>> persistence mechanisms in future. While these changes should be largely
>> invisible to users, it is a huge update that impacts all of GeoWebCache.
>> However, due to these changes, we ask that you *please test the embedded
>> GeoWebCache*.
>> UI Improvements
>>
>> Entering in URLs for data files has been improved with autocomplete – now
>> GeoServer will scan the path that has already been typed, and suggest
>> existing files within that path.
>> 
>>
>> In addition, autocomplete support has been added to a number of dropdowns
>> which contain a long list of values, such as stores or layers. You can now
>> start typing the name of an option, and the visible options will be
>> filtered to match.
>> 
>> Removed OS X installers
>>
>> Due to lack of resources and interest, the OS X dmg installers are no
>> longer being built. OS X users can still use
>> 
>>  the system-independent binary
>> 
>> .
>> New community modules
>>
>> The 2.13 series comes with a few new community modules, in particular:
>>
>>- Do you want to generate 

Re: [Geoserver-devel] [Geowebcache-devel] Version missmatch

[Ian Turton]

Well, it does build if you knock GeoServer back to 1.13-SNAPSHOT but I
don't want to commit that if GWC should have advanced.

Ian

On 22 February 2018 at 13:59, Andrea Aime 
wrote:

> Hi Ian,
> I've reported the same problem yesterday on GeoServer's Gitter. Torben
> inquired with Kevin, no response as of yet.
> As far as I can see, we are in a un-buildable situation, because master is
> still claiming version 1.13 right now:
> https://github.com/GeoWebCache/geowebcache/blob/master/geowebcache/pom.xml
>
> (live link, contents will change on updates)
>
> Cheers
> Andrea
>
> On Thu, Feb 22, 2018 at 2:52 PM, Ian Turton  wrote:
>
>> I'm trying to build GeoServer on master today and it claims not to be
>> able to find GeoWebCache jars of 1.14-SNAPSHOT vintage. No problem I
>> thought I'll update GWC and build that, but GWC master is building
>> 1.13-SNAPSHOT jars.
>>
>> So my question is which version number is correct?
>>
>> Ian
>>
>> --
>> Ian Turton
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Geowebcache-devel mailing list
>> geowebcache-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geowebcache-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 <+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.
>
>


-- 
Ian Turton
--
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] [Geowebcache-devel] Version missmatch

[Andrea Aime]

Hi Ian,
I've reported the same problem yesterday on GeoServer's Gitter. Torben
inquired with Kevin, no response as of yet.
As far as I can see, we are in a un-buildable situation, because master is
still claiming version 1.13 right now:
https://github.com/GeoWebCache/geowebcache/blob/master/geowebcache/pom.xml

(live link, contents will change on updates)

Cheers
Andrea

On Thu, Feb 22, 2018 at 2:52 PM, Ian Turton  wrote:

> I'm trying to build GeoServer on master today and it claims not to be able
> to find GeoWebCache jars of 1.14-SNAPSHOT vintage. No problem I thought
> I'll update GWC and build that, but GWC master is building 1.13-SNAPSHOT
> jars.
>
> So my question is which version number is correct?
>
> Ian
>
> --
> Ian Turton
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geowebcache-devel mailing list
> geowebcache-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geowebcache-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

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] Version missmatch

[Ian Turton]

I'm trying to build GeoServer on master today and it claims not to be able
to find GeoWebCache jars of 1.14-SNAPSHOT vintage. No problem I thought
I'll update GWC and build that, but GWC master is building 1.13-SNAPSHOT
jars.

So my question is which version number is correct?

Ian

-- 
Ian Turton
--
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 166 - Support for controlled nearest match on time dimension

[Alessio Fabiani]

+1

Regards,

Alessio Fabiani

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

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead


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

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.

2018-02-22 10:25 GMT+01:00 Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi>:

> Hi,
>
>
>
> Time dimension at least in image mosaics is not quite similar than for
> example spatial dimensions because it is not really continuous and it
> usually does not make sense for example to interpolate values from
> orthophotos which are acquired in different years. See an excerpt from
> DescribeCoverage
>
>
>
> 
>
> 
>
> 1985-01-01T00:00:00.000Z
>
> 
>
> 
>
> 1986-01-01T00:00:00.000Z
>
> 
>
> 1988-01-01T00:00:00.000Z
>
> 
>
>
>
> We have been thinking what should happen with an orthophoto coverage if
> WCS user is asking for a time range that does not include any TimeInstant,
> or if range covers many TimeInstants. The latest TimeInstant within the
> range, or the closest one in the past if nothing is found otherwise might
> suit for us. For some other kind of coverages like meteorological data that
> is not good approach but users probably want to get strictly what they ask
> as multilayer netCDF file or animated GIF or whatever.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] *Puolesta
> *Andrea Aime
> *Lähetetty:* 22. helmikuuta 2018 10:58
> *Vastaanottaja:* Rahkonen Jukka (MML)  >
> *Kopio:* Geoserver-devel 
>
> *Aihe:* Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest
> match on time dimension
>
>
>
> Hi Jukka,
>
> the proposal is targeted solely at WMS, but the code is being setup so
> that the same facilities
>
> can be reused for WCS as well, in case someone wants to.
>
> I'm not sure WCS has any way to advertise such support, and time is just
> another dimension there,
>
> e.g., is it treated the same as spatial ones.
>
>
>
> Cheers
>
> Andrea
>
>
>
>
>
>
>
> On Thu, Feb 22, 2018 at 9:35 AM, Rahkonen Jukka (MML)  maanmittauslaitos.fi> wrote:
>
> +1
>
>
>
> Will it work also with WCS 2.x for time positions and ranges?
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
> *Lähettäjä:* Andrea Aime [mailto:andrea.a...@geo-solutions.it]
> *Lähetetty:* 20. helmikuuta 2018 17:32
> *Vastaanottaja:* Geoserver-devel 
> *Aihe:* Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest
> match on time dimension
>
>
>
> Hi,
>
> the mailing list issues caused some delays, a few people already cast
> their vote directly
>
> on the GSIP and notified on gitter.
>
>
>
> Hopefully the list is back in working state, keep the feedback/votes
> coming :)
>
>
>
> Cheers
>
> Andrea
>
>
>
>
>
> On Mon, Feb 19, 2018 at 5:36 PM, Andrea Aime 
> wrote:
>
> Hi,
>
> as briefly suggested during a recent GSIP meeting, here is the proposal
> for adding WMS nearest match support on time dimension:

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

[monitor]

See 


Changes:

[Alessio Fabiani]  - Remove verbose exception from notification community module

--
[...truncated 10.84 MB...]
Feb 22, 2018 10:22:30 AM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionProvider', but ApplicationContext is unset.
Feb 22, 2018 10:22:30 AM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 22, 2018 10:22:32 AM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 22, 2018 10:22:32 AM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 22, 2018 10:22:33 AM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Feb 22, 2018 10:22:33 AM org.geoserver.catalog.ResourcePool getFeatureType
WARNING: Error while getting feature type, flushing cache and retrying: Failed 
to find the datastore factory for dummy, did you forget to install the store 
extension jar?
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.881 sec

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources) @ 
gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2.1:test-jar-no-fork (attach-sources) @ 
gs-importer-web ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ gs-importer-web 
---
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT.pom
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-tests.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-sources.jar
[INFO] Installing 

 to 
/var/jenkins/.m2/repository/org/geoserver/importer/gs-importer-web/2.14-SNAPSHOT/gs-importer-web-2.14-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] 
[INFO] Building GeoServer CAS Security Web Module 2.14-SNAPSHOT
[INFO] 
Feb 22, 2018 10:22:34 AM org.geoserver.importer.Importer copyFromFeatureReader
INFO: load to target took 28
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gs-web-sec-cas ---
[INFO] Deleting 

[INFO] 
[INFO] --- git-commit-id-plugin:2.1.15:revision (default) @ gs-web-sec-cas ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
gs-web-sec-cas ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing 

Re: [Geoserver-devel] new community module workflow

[Niels Charlier]

So going back to this proposal of last year. I contributed a first batch 
of code which is inside a new PR. Now this is a new community module 
that will be fully maintained by me (and fully documented soon as well) 
so I do not think I technically need approval for the code (although 
reviews/comments are always more then welcome!) but there are two small 
changes in the "main module" that I do need approval for. Would there 
someone will so kind to have a look at them (would only take a few minutes).


These are direct links to the changes in main:

https://github.com/geoserver/geoserver/pull/2759/commits/6945957a93b326ddaa39ee00c3ca4a707d663aee#diff-ed7269d9c2be90db1cbfde7d0f32d751

https://github.com/geoserver/geoserver/pull/2759/commits/6945957a93b326ddaa39ee00c3ca4a707d663aee#diff-5fac1624412cebb8475c6e0fee6fd17c

Kind Regards

Niels


On 30-05-17 16:20, Niels Charlier wrote:

What is your opinion on the dependency concern?

What do you think of having the new module be called "task manager" or 
something like that.


Although it will contain a quite a bit of task implementation that 
regards remote data management specifically. Should I add two new 
modules though :/


Regards

Niels


On 30-05-17 04:05, Ben Caradoc-Davies wrote:

On 30/05/17 00:55, Niels Charlier wrote:

Therefore, logically, it would be importer that needs be modified to be
built on top of my API rather than me building on top of importer.


This sounds like a great option. A modest investment in refactoring 
now will save us the future maintenance overhead introduced by 
duplication. (And I speak us someone currently fixing my own 
ill-considered DataUtilities duplication from five years ago.)


Kind regards,




-- 


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



--
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] GeoServer 2.13-beta released

[Andrea Aime]

Hi all,
several new features and improvements were missing from the announcement,
I've updated it on the blog, please see here:

http://blog.geoserver.org/2018/02/22/geoserver-2-13-beta-released/

Cheers
Andrea


On Thu, Feb 22, 2018 at 1:52 AM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:

> We are happy to announce the release of GeoServer 2.13-beta
> .
> Downloads are available (zip
> 
> , war
> 
> , and exe
> )
> along with docs and extensions.
>
> This is a beta release of GeoServer made in conjunction with GeoTools
> 19-beta.
>
> We want to encourage people to test the release thoroughly and report back
> any issue found. With no further delay, let’s see what’s new, that is, what
> is there to test!
> Isolated Workspaces
>
> The concept of an “Isolated Workspaces” has been added to GeoServer, to
> allow for reusing a namespace among multiple workspaces. In particular, an
> isolated workspace allows reuse of a namespace already used by another
> workspace, but its resources (layers, styles, etc …) can only be retrieved
> when using that workspace’s virtual services and will only show up in those
> virtual service capabilities documents.
>
> When reusing a namespace among workspaces, exactly one of those must be
> non-isolated, and the rest must be isolated; i.e. isolated workspaces have
> no restrictions in namespaces usage but the existing restrictions still
> apply for non isolated workspaces.
>
> For more details, refer to the original proposal
> 
> .
> GeoWebCache REST API
>
> Two new endpoints have been added to the GeoWebCache REST API:
>
>- /gwc/rest/blobstores:
>   - GET /gwc/rest/blobstores for a list of the blobstores
>   - GET /gwc/rest/blobstores/{blobStoreName} for details about a
>   single blobstore
>   - PUT /gwc/rest/blobstores/{blobStoreName} to create or update a
>   blobstore
>   - DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
>- /gwc/rest/gridsets:
>   - GET /gwc/rest/gridsets for a list of the gridsets
>   - GET /gwc/rest/gridsets/{gridSetName} for details about a single
>   gridset
>   - PUT /gwc/rest/gridsets/{gridSetName} to create or update a gridset
>   - DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset
>
> API docs for these endpoints will be added to the GeoServer documentation
> shortly. Until then, the request body syntax for PUT requests closely
> matched the equivalent structures in geowebcache.xml: BlobStores
> 
>  and GridSets
> 
> .
>
> The ArcGISCache backed layers are now also configurable via the REST API.
>
> This release sees a major reworking of the configuration system in
> GeoWebCache that will allow for plugging in alternate configuration
> persistence mechanisms in future. While these changes should be largely
> invisible to users, it is a huge update that impacts all of GeoWebCache.
> However, due to these changes, we ask that you *please test the embedded
> GeoWebCache*.
> UI Improvements
>
> Entering in URLs for data files has been improved with autocomplete – now
> GeoServer will scan the path that has already been typed, and suggest
> existing files within that path.
> 
>
> In addition, autocomplete support has been added to a number of dropdowns
> which contain a long list of values, such as stores or layers. You can now
> start typing the name of an option, and the visible options will be
> filtered to match.
> 
> Removed OS X installers
>
> Due to lack of resources and interest, the OS X dmg installers are no
> longer being built. OS X users can still use
> 
>  the system-independent binary
> 
> .
> New community modules
>
> The 2.13 series comes with a few new community modules, in particular:
>
>- Do you want to generate GHRSST compliant outputs from GHRSST inputs?
>Try out the new GHRSST NetCDF output community module.
>- There is also a new community module
>
> 

[Geoserver-devel] Fwd: Documentation not updating, yet doc build seems fine

[Andrea Aime]

This mail was probably not delivered due to the SF mailing list outage,
trying again:

-- Forwarded message --
From: Andrea Aime 
Date: Wed, Feb 14, 2018 at 7:18 PM
Subject: Documentation not updating, yet doc build seems fine
To: Geoserver-devel 


Hi,
the documentation does not seem to be updating anymore, at least for the
"latest" link.

For example, see this raw link to github, talking about a new ability in
the wps download process (community module):
https://github.com/geoserver/geoserver/blob/master/doc/en/
user/source/community/wps-download/rawDownload.rst#writing-parameters

and the documentation published on site (two links to try here):

http://docs.geoserver.org/latest/en/user/community/wps-
download/rawDownload.html
http://docs.geoserver.org/master/en/user/community/wps-
download/rawDownload.html

I went on the build server to have a look, the documentation build is
there, running, and seems to be
doing its job, too:
https://build.geoserver.org/view/geoserver/job/geoserver-
master-live-docs/1082/console

The change above is 8 days old, the last live docs build is 2 days old,
I've checked the revision number it's
getting, it was up to date, run the same build command on my machine and
that generates up to date
documentation.

The copying steps at the end also seem right. So... how come the file comes
back outdated on
the doc site?

Wondering if by any chance there is a caching accelerator in the middle
that is not seeing file updates?

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] GSIP 166 - Support for controlled nearest match on time dimension

[Rahkonen Jukka (MML)]

Hi,

Time dimension at least in image mosaics is not quite similar than for example 
spatial dimensions because it is not really continuous and it usually does not 
make sense for example to interpolate values from orthophotos which are 
acquired in different years. See an excerpt from DescribeCoverage



1985-01-01T00:00:00.000Z


1986-01-01T00:00:00.000Z

1988-01-01T00:00:00.000Z


We have been thinking what should happen with an orthophoto coverage if WCS 
user is asking for a time range that does not include any TimeInstant, or if 
range covers many TimeInstants. The latest TimeInstant within the range, or the 
closest one in the past if nothing is found otherwise might suit for us. For 
some other kind of coverages like meteorological data that is not good approach 
but users probably want to get strictly what they ask as multilayer netCDF file 
or animated GIF or whatever.

-Jukka Rahkonen-


Lähettäjä: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] Puolesta Andrea 
Aime
Lähetetty: 22. helmikuuta 2018 10:58
Vastaanottaja: Rahkonen Jukka (MML) 
Kopio: Geoserver-devel 
Aihe: Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest match on 
time dimension

Hi Jukka,
the proposal is targeted solely at WMS, but the code is being setup so that the 
same facilities
can be reused for WCS as well, in case someone wants to.
I'm not sure WCS has any way to advertise such support, and time is just 
another dimension there,
e.g., is it treated the same as spatial ones.

Cheers
Andrea



On Thu, Feb 22, 2018 at 9:35 AM, Rahkonen Jukka (MML) 
>
 wrote:
+1

Will it work also with WCS 2.x for time positions and ranges?

-Jukka Rahkonen-



Lähettäjä: Andrea Aime 
[mailto:andrea.a...@geo-solutions.it]
Lähetetty: 20. helmikuuta 2018 17:32
Vastaanottaja: Geoserver-devel 
>
Aihe: Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest match on 
time dimension

Hi,
the mailing list issues caused some delays, a few people already cast their 
vote directly
on the GSIP and notified on gitter.

Hopefully the list is back in working state, keep the feedback/votes coming :)

Cheers
Andrea


On Mon, Feb 19, 2018 at 5:36 PM, Andrea Aime 
> wrote:
Hi,
as briefly suggested during a recent GSIP meeting, here is the proposal for 
adding WMS nearest match support on time dimension:

https://github.com/geoserver/geoserver/wiki/GSIP-166

The proposal is limited to time due to resource limitations, but care will be 
taken not prevent/complicate future support
for elevation and custom dimensions.
The proposal is currently scheduled for 2.14.x, although a request for backport 
might happen at a later date.

Please discuss, or if you're happy with the proposal as is, cast a vote :-)

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 

Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest match on time dimension

[Andrea Aime]

Hi Jukka,
the proposal is targeted solely at WMS, but the code is being setup so that
the same facilities
can be reused for WCS as well, in case someone wants to.
I'm not sure WCS has any way to advertise such support, and time is just
another dimension there,
e.g., is it treated the same as spatial ones.

Cheers
Andrea



On Thu, Feb 22, 2018 at 9:35 AM, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> +1
>
>
>
> Will it work also with WCS 2.x for time positions and ranges?
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
> *Lähettäjä:* Andrea Aime [mailto:andrea.a...@geo-solutions.it]
> *Lähetetty:* 20. helmikuuta 2018 17:32
> *Vastaanottaja:* Geoserver-devel 
> *Aihe:* Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest
> match on time dimension
>
>
>
> Hi,
>
> the mailing list issues caused some delays, a few people already cast
> their vote directly
>
> on the GSIP and notified on gitter.
>
>
>
> Hopefully the list is back in working state, keep the feedback/votes
> coming :)
>
>
>
> Cheers
>
> Andrea
>
>
>
>
>
> On Mon, Feb 19, 2018 at 5:36 PM, Andrea Aime 
> wrote:
>
> Hi,
>
> as briefly suggested during a recent GSIP meeting, here is the proposal
> for adding WMS nearest match support on time dimension:
>
>
>
> https://github.com/geoserver/geoserver/wiki/GSIP-166
>
>
>
> The proposal is limited to time due to resource limitations, but care will
> be taken not prevent/complicate future support
>
> for elevation and custom dimensions.
>
> The proposal is currently scheduled for 2.14.x, although a request for
> backport might happen at a later date.
>
>
>
> Please discuss, or if you're happy with the proposal as is, cast a vote :-)
>
>
>
> 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 <+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.
>
>
>
>
>
>
>
> --
>
> 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 

Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest match on time dimension

[Rahkonen Jukka (MML)]

+1

Will it work also with WCS 2.x for time positions and ranges?

-Jukka Rahkonen-



Lähettäjä: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Lähetetty: 20. helmikuuta 2018 17:32
Vastaanottaja: Geoserver-devel 
Aihe: Re: [Geoserver-devel] GSIP 166 - Support for controlled nearest match on 
time dimension

Hi,
the mailing list issues caused some delays, a few people already cast their 
vote directly
on the GSIP and notified on gitter.

Hopefully the list is back in working state, keep the feedback/votes coming :)

Cheers
Andrea


On Mon, Feb 19, 2018 at 5:36 PM, Andrea Aime 
> wrote:
Hi,
as briefly suggested during a recent GSIP meeting, here is the proposal for 
adding WMS nearest match support on time dimension:

https://github.com/geoserver/geoserver/wiki/GSIP-166

The proposal is limited to time due to resource limitations, but care will be 
taken not prevent/complicate future support
for elevation and custom dimensions.
The proposal is currently scheduled for 2.14.x, although a request for backport 
might happen at a later date.

Please discuss, or if you're happy with the proposal as is, cast a vote :-)

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.




--

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 

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

[monitor]

See 


Changes:

[tbarsballe] Update doc pom to 2.14-SNAPSHOT

--
[...truncated 20.55 KB...]
[INFO] GeoServer Resource Browser
[INFO] GeoServer notification event system
[INFO] S3 Geotiff Support
[INFO] Application Schema Support
[INFO] Application Schema Integration Test
[INFO] Sample DataAccess Integration Test
[INFO] ArcSDE DataStore Extension
[INFO] SQL Server DataStore Extension
[INFO] Oracle DataStore Extension
[INFO] MySQL DataStore Extension
[INFO] DB2 DataStore Extension
[INFO] ImageMap Output Format
[INFO] ImageI/O-Ext GDAL Coverage Extension
[INFO] JP2K Coverage Extension
[INFO] OGR WFS
[INFO] OGR WPS
[INFO] Excel Output Format
[INFO] Chart external graphics support
[INFO] Feature Generalization Extension
[INFO] Image Mosaic JDBC Extension
[INFO] OWS request flow controller
[INFO] Web process status sharing with Hazelcast
[INFO] Web Processing Service GUI
[INFO] GeoServer Layer Querying filter functions
[INFO] Teradata DataStore Extension
[INFO] GeoServer Monitor Extensions
[INFO] Core Monitor Extension
[INFO] Monitor Hibernate Extension
[INFO] GeoServer Security Extension Modules
[INFO] GeoServer CAS Security Module
[INFO] GeoServer Security Extension Web Modules
[INFO] GeoServer CAS Security Web Module
[INFO] XLST based WFS output format
[INFO] GeoServer INSPIRE Extensions
[INFO] GeoServer CSS Styling
[INFO] Catalog Services for the Web parent
[INFO] Catalog Services for the Web interfaces
[INFO] Catalog Services for the Web - Simple CatalogStore implementation
[INFO] Catalog Services for the Web core module
[INFO] CSW UI Module
[INFO] DXF WFS output format and WPS PPIO
[INFO] DXF WFS output format
[INFO] DXF WPS PPIO
[INFO] Printing Module
[INFO] GeoServer WCS 2.0 Earth Observation Extensions
[INFO] Web Coverage Service 2.0 Earth Observation extensions
[INFO] Web Coverage Service 2.0 Earth Observation GUI extension
[INFO] GeoServer libjpeg-turbo Module
[INFO] Importer REST Api Module-ng
[INFO] Importer Berkley DB Persistence Module
[INFO] Importer Web UI Module
[INFO] Vector Tiles
[INFO] Ysld GeoServer Plugin
[INFO] GeoServer Release Module
[INFO] 
[INFO] 
[INFO] Building GeoServer 2.14-SNAPSHOT
[INFO] 
[WARNING] The POM for org.geowebcache:gwc-core:jar:1.14-SNAPSHOT is missing, no 
dependency information available
[INFO] 
[INFO] 
[INFO] Skipping GeoServer
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoServer .. FAILURE [  0.141 s]
[INFO] Core Platform Module ... SKIPPED
[INFO] Open Web Service Module  SKIPPED
[INFO] Main Module  SKIPPED
[INFO] GeoServer Security Modules . SKIPPED
[INFO] GeoServer Security Tests Module  SKIPPED
[INFO] GeoServer JDBC Security Module . SKIPPED
[INFO] GeoServer LDAP Security Module . SKIPPED
[INFO] Web Coverage Service Module  SKIPPED
[INFO] Web Coverage Service 1.0 Module  SKIPPED
[INFO] Web Coverage Service 1.1 Module  SKIPPED
[INFO] Web Coverage Service 2.0 Module  SKIPPED
[INFO] Web Feature Service Module . SKIPPED
[INFO] Web Map Service Module . SKIPPED
[INFO] KML support for GeoServer .. SKIPPED
[INFO] gs-rest  SKIPPED
[INFO] GeoWebCache (GWC) Module ... SKIPPED
[INFO] gs-restconfig .. SKIPPED
[INFO] gs-restconfig-wcs .. SKIPPED
[INFO] gs-restconfig-wfs .. SKIPPED
[INFO] gs-restconfig-wms .. SKIPPED
[INFO] GeoServer Web Modules .. SKIPPED
[INFO] Core UI Module . SKIPPED
[INFO] WMS UI Module .. SKIPPED
[INFO] GWC UI Module .. SKIPPED
[INFO] WFS UI Module .. SKIPPED
[INFO] Demos Module ... SKIPPED
[INFO] WCS UI Module .. SKIPPED
[INFO]