Okay, beyond that the next failure is: Transfer failed for > http://repo1.maven.org/maven2/org/geotools/gt-api/21-SNAPSHOT/gt-api-21-SNAPSHOT.pom > 501 HTTPS Required -> [Help 1]
The 21-SNAPSHOTS are indeed no longer published anywhere, and the gt-api module was refactored away. Geofence will need to update ... -- Jody Garnett On Sun, 11 Oct 2020 at 11:23, Jody Garnett <[email protected]> wrote: > With the nexus patch the other week the build server success rate has > improved greatly. I turned off the "repair" jobs last week and have no > additional reports of build failures. > > If this is really in the clear we can start to turn on the parallel builds > for each branch again. > > The one blip is geofence where all the jobs are failing, and jenkins does > not list any successful builds for these jobs. Checking the geofence-master > job, it has a failure on a missing 'geodb' jar: > > [ERROR] Failed to execute goal on project geofence-persistence: Could not > resolve dependencies for project > org.geoserver.geofence:geofence-persistence:jar:3.5-SNAPSHOT: Failed to > collect dependencies at > org.hibernatespatial:hibernate-spatial-h2-geodb:jar:1.1.3.1 -> > org.opengeo:geodb:jar:0.9: Failed to read artifact descriptor for > org.opengeo:geodb:jar:0.9: Could not transfer artifact > org.opengeo:geodb:pom:0.9 from/to spring-release ( > http://maven.springframework.org/release): Authorization failed for > http://maven.springframework.org/release/org/opengeo/geodb/0.9/geodb-0.9.pom > 403 Forbidden -> [Help 1] > > > Searching the repo this dependency is available: > https://repo.osgeo.org/#browse/search=keyword%3Dgeodb > > Digging into this the pom.xml has not been migrated from > repo.boundlessgeo.com. > > -- > Jody Garnett >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
