I took a look today and couldn't reproduce - everything had a manifest that
looked like the following:

Manifest-Version: 1.0
Automatic-Module-Name: org.geotools.epsg_hsql
Build-Timestamp: 16-Jul-2019 14:45
Built-By: ubuntu
Class-Path: gt-referencing-22-SNAPSHOT.jar ejml-ddense-0.34.jar ejml-c
 ore-0.34.jar commons-pool-1.5.4.jar gt-metadata-22-SNAPSHOT.jar gt-op
 engis-22-SNAPSHOT.jar systems-common-java8-0.7.2.jar uom-se-1.0.8.jar
  unit-api-1.0.jar uom-lib-common-1.0.2.jar si-quantity-0.7.1.jar si-u
 nits-java8-0.7.1.jar commons-lang3-3.8.1.jar jgridshift-1.0.jar Geogr
 aphicLib-Java-1.49.jar hsqldb-2.4.1.jar jai_core-1.1.3.jar
Project-Version: 22-SNAPSHOT
Git-Revision: 4683776b590f23ccc5c67044b6b875905e76f770
Created-By: Apache Maven 3.6.0
Build-Jdk: 1.8.0_212

There is likely still be a persistent issue here, but it doesn't seem to
happen consistently - I'll take a look again in a couple days, and see if
there is any discrepancy then.

Torben

On Fri, Jul 12, 2019 at 1:32 AM Andrea Aime <[email protected]>
wrote:

> Hi,
> I wanted to ask on the user for volunteers list to test the EPSG 9.6
> upgrade, but before
> doing so, I checked the latest nightly build:
>
>
> https://build.geoserver.org/geoserver/master/geoserver-master-latest-bin.zip
>
> and found the database upgrade was not in there. In fact, the gt-hsql-epsg
> jar contained in there has the following manifest:
>
> Manifest-Version: 1.0
> Automatic-Module-Name: org.geotools.epsg_hsql
> *Build-Timestamp: 03-Jul-2019 15:47*
> Built-By: ubuntu
> Class-Path: gt-referencing-22-SNAPSHOT.jar ejml-ddense-0.34.jar ejml-c
>  ore-0.34.jar commons-pool-1.5.4.jar gt-metadata-22-SNAPSHOT.jar gt-op
>  engis-22-SNAPSHOT.jar systems-common-java8-0.7.2.jar uom-se-1.0.8.jar
>   unit-api-1.0.jar uom-lib-common-1.0.2.jar si-quantity-0.7.1.jar si-u
>  nits-java8-0.7.1.jar commons-lang3-3.8.1.jar jgridshift-1.0.jar Geogr
>  aphicLib-Java-1.49.jar hsqldb-2.4.1.jar jai_core-1.1.3.jar
> Project-Version: 22-SNAPSHOT
> Git-Revision: 1e0c0d814869b81f6ab8166a0726def041e2c5db
> Created-By: Apache Maven 3.6.0
> Build-Jdk: 1.8.0_212
>
> and still contains the 8.6 database. Checking another jar, a GeoServer
> one, the situation is the same:
>
> Manifest-Version: 1.0
> Application-Name:
> Implementation-Title: Web Coverage Service 1.1 Module
> Implementation-Version: 2.16-SNAPSHOT
> *Build-Timestamp: 03-Jul-2019 16:03*
> Archiver-Version: Plexus Archiver
> Built-By: ubuntu
> Specification-Vendor: Open Source Geospatial Foundation
> Specification-Title: Web Coverage Service 1.1 Module
> Implementation-Vendor-Id: org.geoserver
> GeoServerModule: core
> Project-Version: 2.16-SNAPSHOT
> Implementation-Vendor: Open Source Geospatial Foundation
> Iteration-Name:
> Git-Revision: ad7eb9041ff5dab135cba61798e8415c3b91097d
> Created-By: Apache Maven 3.6.0
> Build-Jdk: 1.8.0_212
> Specification-Version: 2.16-SNAPSHOT
>
> Looking at a timestamped bin zip  instead, e.g.:
>
>
> https://build.geoserver.org/geoserver/master/geoserver-master-2019-07-11-war.zip
>
> then the artifacts are up to date:
>
> Manifest-Version: 1.0
> Application-Name:
> Implementation-Title: REST UI Module
> Implementation-Version: 2.16-SNAPSHOT
> *Build-Timestamp: 11-Jul-2019 12:08*
> Archiver-Version: Plexus Archiver
> Built-By: ubuntu
> Specification-Vendor: Open Source Geospatial Foundation
> Specification-Title: REST UI Module
> Implementation-Vendor-Id: org.geoserver.web
> GeoServerModule: core
> Project-Version: 2.16-SNAPSHOT
> Implementation-Vendor: Open Source Geospatial Foundation
> Iteration-Name:
> Git-Revision: c54025e96071ed96f8aeb5392af1ed4a1d9255b5
> Created-By: Apache Maven 3.6.0
> Build-Jdk: 1.8.0_212
> Specification-Version: 2.16-SNAPSHOT
>
> So it seems there is an issue with managing the "latest" file/link?
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
> http://www.geo-solutions.it http://twitter.com/geosolutions_it
> ------------------------------------------------------- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to