[Geoserver-devel] geogig build failures on 2.8.x

GeoServer GeoServer Developer
1

Reading the latest build failure, the 2.8.x branch is suffering some instability due to geogig development.

Changes

  1. Adapt GeoGig plugin to handle repository URI instead of parent/child File (detail)
  2. Organize top-level GeoGig WEB API routes to prevent conflicts. (detail)
  3. Stick geogig plugin to geogig 1.0-RC2 (detail)
  4. Return geogig repository URI directly from RepositoryInfo when resolving the repo URI. (detail)
  5. Replace boncecp by hikari connection pool in geogig plugin. (detail)
  6. Update GeoGig plugin to support PostgreSQL backend configuration (detail)
  7. Set geogig pg connection defaults (detail)
  8. Leverage existing UI components for GeoGig Repository configuration (detail)
  9. Add ability to import an existing PostgreSQL backed GeoGig repsoitory. (detail)
  10. fix typo (detail)
  11. Update geogig to latest from geogig dev branch (detail)
  12. Add explicit dependency on logback for geogig plugin (detail)
  13. Adds unit tests for GeoGig repository import and edit panels. (detail)
    Results in the following failure:
[ERROR] Failed to execute goal on project gs-geogig: Could not resolve dependencies for project org.geoserver.community:gs-geogig:jar:2.8-SNAPSHOT: The following artifacts could not be resolved: org.locationtech.geogig:geogig-cli:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-geotools:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-datastore:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-web-api:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-osm:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-postgres:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-core:jar:tests:1.0-SNAPSHOT, org.locationtech.geogig:geogig-cli:jar:tests:1.0-SNAPSHOT: Could not find artifact org.locationtech.geogig:geogig-cli:jar:1.0-20160518.024716-56 in boundless ([https://repo.boundlessgeo.com/main/](https://repo.boundlessgeo.com/main/)) -> [Help 1]
···

–
Jody Garnett

2

Jody, I’m looking into it. Not sure where 20160518.024716-56 is coming from, but that snapshot version does not seem to be deployed. I’ll reply back when i figure out what’s going on.

···

On Wed, May 18, 2016 at 11:53 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Reading the latest build failure, the 2.8.x branch is suffering some instability due to geogig development.

Changes

  1. Adapt GeoGig plugin to handle repository URI instead of parent/child File (detail)
  2. Organize top-level GeoGig WEB API routes to prevent conflicts. (detail)
  3. Stick geogig plugin to geogig 1.0-RC2 (detail)
  4. Return geogig repository URI directly from RepositoryInfo when resolving the repo URI. (detail)
  5. Replace boncecp by hikari connection pool in geogig plugin. (detail)
  6. Update GeoGig plugin to support PostgreSQL backend configuration (detail)
  7. Set geogig pg connection defaults (detail)
  8. Leverage existing UI components for GeoGig Repository configuration (detail)
  9. Add ability to import an existing PostgreSQL backed GeoGig repsoitory. (detail)
  10. fix typo (detail)
  11. Update geogig to latest from geogig dev branch (detail)
  12. Add explicit dependency on logback for geogig plugin (detail)
  13. Adds unit tests for GeoGig repository import and edit panels. (detail)
    Results in the following failure:
[ERROR] Failed to execute goal on project gs-geogig: Could not resolve dependencies for project org.geoserver.community:gs-geogig:jar:2.8-SNAPSHOT: The following artifacts could not be resolved: org.locationtech.geogig:geogig-cli:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-geotools:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-datastore:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-web-api:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-osm:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-postgres:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-core:jar:tests:1.0-SNAPSHOT, org.locationtech.geogig:geogig-cli:jar:tests:1.0-SNAPSHOT: Could not find artifact org.locationtech.geogig:geogig-cli:jar:1.0-20160518.024716-56 in boundless ([https://repo.boundlessgeo.com/main/](https://repo.boundlessgeo.com/main/)) -> [Help 1]

–
Jody Garnett

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

​ ​
Erik Merkle

3

I think the GeoGig artifacts and Artifactory have been cleared up. The nightly build for 2.8.x should hopefully be back to normal next time around.

···

On Wed, May 18, 2016 at 2:50 PM, Erik Merkle <emerkle@anonymised.com> wrote:

Jody, I’m looking into it. Not sure where 20160518.024716-56 is coming from, but that snapshot version does not seem to be deployed. I’ll reply back when i figure out what’s going on.

​ ​
Erik Merkle

​ ​
Erik Merkle

On Wed, May 18, 2016 at 11:53 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Reading the latest build failure, the 2.8.x branch is suffering some instability due to geogig development.

Changes

  1. Adapt GeoGig plugin to handle repository URI instead of parent/child File (detail)
  2. Organize top-level GeoGig WEB API routes to prevent conflicts. (detail)
  3. Stick geogig plugin to geogig 1.0-RC2 (detail)
  4. Return geogig repository URI directly from RepositoryInfo when resolving the repo URI. (detail)
  5. Replace boncecp by hikari connection pool in geogig plugin. (detail)
  6. Update GeoGig plugin to support PostgreSQL backend configuration (detail)
  7. Set geogig pg connection defaults (detail)
  8. Leverage existing UI components for GeoGig Repository configuration (detail)
  9. Add ability to import an existing PostgreSQL backed GeoGig repsoitory. (detail)
  10. fix typo (detail)
  11. Update geogig to latest from geogig dev branch (detail)
  12. Add explicit dependency on logback for geogig plugin (detail)
  13. Adds unit tests for GeoGig repository import and edit panels. (detail)
    Results in the following failure:
[ERROR] Failed to execute goal on project gs-geogig: Could not resolve dependencies for project org.geoserver.community:gs-geogig:jar:2.8-SNAPSHOT: The following artifacts could not be resolved: org.locationtech.geogig:geogig-cli:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-geotools:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-datastore:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-web-api:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-osm:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-postgres:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-core:jar:tests:1.0-SNAPSHOT, org.locationtech.geogig:geogig-cli:jar:tests:1.0-SNAPSHOT: Could not find artifact org.locationtech.geogig:geogig-cli:jar:1.0-20160518.024716-56 in boundless ([https://repo.boundlessgeo.com/main/](https://repo.boundlessgeo.com/main/)) -> [Help 1]

–
Jody Garnett

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

4

Thanks Erik, I hope we do not get too many more snapshot glitches as part of the repo DNS changeover.

We should pay careful attention to the live snapshots being produced for GeoTools, GeoServer etc… and see if downstream projects are pulling the correct details.

···

On 18 May 2016 at 15:12, Erik Merkle <emerkle@anonymised.com> wrote:

I think the GeoGig artifacts and Artifactory have been cleared up. The nightly build for 2.8.x should hopefully be back to normal next time around.

–
Jody Garnett

​ ​
Erik Merkle

On Wed, May 18, 2016 at 2:50 PM, Erik Merkle <emerkle@anonymised.com> wrote:

Jody, I’m looking into it. Not sure where 20160518.024716-56 is coming from, but that snapshot version does not seem to be deployed. I’ll reply back when i figure out what’s going on.

​ ​
Erik Merkle

On Wed, May 18, 2016 at 11:53 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Reading the latest build failure, the 2.8.x branch is suffering some instability due to geogig development.

Changes

  1. Adapt GeoGig plugin to handle repository URI instead of parent/child File (detail)
  2. Organize top-level GeoGig WEB API routes to prevent conflicts. (detail)
  3. Stick geogig plugin to geogig 1.0-RC2 (detail)
  4. Return geogig repository URI directly from RepositoryInfo when resolving the repo URI. (detail)
  5. Replace boncecp by hikari connection pool in geogig plugin. (detail)
  6. Update GeoGig plugin to support PostgreSQL backend configuration (detail)
  7. Set geogig pg connection defaults (detail)
  8. Leverage existing UI components for GeoGig Repository configuration (detail)
  9. Add ability to import an existing PostgreSQL backed GeoGig repsoitory. (detail)
  10. fix typo (detail)
  11. Update geogig to latest from geogig dev branch (detail)
  12. Add explicit dependency on logback for geogig plugin (detail)
  13. Adds unit tests for GeoGig repository import and edit panels. (detail)
    Results in the following failure:
[ERROR] Failed to execute goal on project gs-geogig: Could not resolve dependencies for project org.geoserver.community:gs-geogig:jar:2.8-SNAPSHOT: The following artifacts could not be resolved: org.locationtech.geogig:geogig-cli:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-geotools:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-datastore:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-web-api:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-osm:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-postgres:jar:1.0-SNAPSHOT, org.locationtech.geogig:geogig-core:jar:tests:1.0-SNAPSHOT, org.locationtech.geogig:geogig-cli:jar:tests:1.0-SNAPSHOT: Could not find artifact org.locationtech.geogig:geogig-cli:jar:1.0-20160518.024716-56 in boundless ([https://repo.boundlessgeo.com/main/](https://repo.boundlessgeo.com/main/)) -> [Help 1]

–
Jody Garnett

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

5

On Wed, May 18, 2016 at 8:04 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Thanks Erik, I hope we do not get too many more snapshot glitches as part
of the repo DNS changeover.

We should pay careful attention to the live snapshots being produced for
GeoTools, GeoServer etc... and see if downstream projects are pulling the
correct details.

Agreed. FWIW I've created a Jenkins build that builds only the geogig
geoserver plugin [1] whenever geogig is built so these kind of issues are
catch up immediatly instead of crossing fingers for the nightly build to
pass