[Geoserver-devel] Jenkins build is back to normal : geoserver-2.12.x #21

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___

Re: [Geoserver-devel] Missing Jenkins geowebcache-1.12.x breaks geoserver-2.12.x

FYI Torben has created the missing Jenkins job. It has completed and the geoserver-2.12.x job is now running. Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

Re: [Geoserver-devel] Missing Jenkins geowebcache-1.12.x breaks geoserver-2.12.x

Typo: should be: geoserver-2.12.x fails because it is building against the stale artifacts built when geowebcache master was 1.12-SNAPSHOT. On 07/10/17 11:50, Ben Caradoc-Davies wrote: geoserver-2.12.x fails because it is building against the stale artifacts built when geowebcache master was 2

[Geoserver-devel] Missing Jenkins geowebcache-1.12.x breaks geoserver-2.12.x

Torben, there is no Jenkins geowebcache-1.12.x on ares or apollo, so nothing to build GeoWebCache 1.12-SNAPSHOT artifacts containing the backport of GeoWebCache #546: https://github.com/GeoWebCache/geowebcache/pull/546 geoserver-2.12.x fails because it is building against the stale artifacts

[Geoserver-devel] Build failed in Jenkins: geoserver-2.12.x #20

See Changes: [tbarsballe] re-add gwc-s3 community module to the build -- [...truncated 17.17 MB...] [INFO] Deleting

[Geoserver-devel] [JIRA] (GEOS-8324) StackOverflow exception when comparing FeatureTypeInfo

Title: Message Title Torben Barsballe crea

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Most of JARs of 2.12.x are old. Some mess around with artifacts I'm afraid. 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 Montr

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

If you look at the executors, they are all named apollo; the URL is just build ;) [image: Inline image 1] On Fri, Oct 6, 2017 at 11:57 AM, Jody Garnett wrote: > I thought it was named "build" :) > > -- > Jody Garnett > > On 6 October 2017 at 10:02, Torben Barsballe > wrote: > >> Excellent. >>

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

I thought it was named "build" :) -- Jody Garnett On 6 October 2017 at 10:02, Torben Barsballe wrote: > Excellent. > > I believe it is named apollo internally. We just need to start using the > name, so that everyone knows what we are talking about when someone says > "apollo". > > Torben > > O

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Excellent. I believe it is named apollo internally. We just need to start using the name, so that everyone knows what we are talking about when someone says "apollo". Torben On Fri, Oct 6, 2017 at 9:55 AM, Ian Turton wrote: > OK I've pushed the release job on new build (we should name that mac

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again: version = 2.12-SNAPSHOT git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b git branch = origin/2.12.x build date = 06-Oct-2017 15:52 geotools version = 18-SNAPSHOT geotools revision = 3f5dbf6

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

OK I've pushed the release job on new build (we should name that machine) - I'll see how it goes Ian On 6 October 2017 at 17:54, Torben Barsballe wrote: > All 2.12.x cite tests now passing on ares. Jody posted the revision info > above, but here it is again: > > version = 2.12-SNAPSHOT > git re

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Ian Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for th

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Jody - I created, and ran a nightly build on ares about an hour ago; thats the only reason the cite tests are actually passing on ares right now (althought they are still in progress, all seem to be passing so far). On Fri, Oct 6, 2017 at 9:44 AM, Jody Garnett wrote: > It was not my intension to

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

It was not my intension to hold up the relesae by asking for a team to port cite jobs, goal is to shut of ares. Here are the revisions from ares: http://ares.boundlessgeo.com/jenkins/view/testing-cite/job/2.12-cite-wfs-1.0/lastSuccessfulBuild/ version = 2.12-SNAPSHOT git revision = bc18e09993a30c

[Geoserver-devel] Jenkins build is back to normal : 2.12-cite-wms-1.3 #2

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] Jenkins build is back to normal : 2.12-cite-wms-1.1 #2

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot __

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Thanks Torben I think all the cite tests on the new build server need is one jar installed Cheers Ian On 6 October 2017 at 17:27, Torben Barsballe wrote: > > On 6 October 2017 at 09:00, Torben Barsballe > wrote: > >> Running the cite tests on ares and the build on the new build server >> wo

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

On Fri, Oct 6, 2017 at 6:16 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > We ought to just be using context:component-scan everywhere (without > mvc:annotation-driven) if GWC is not doing that, then that is probably an > error. > I was just discussing it with Alessio this morning,

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

On 6 October 2017 at 09:00, Torben Barsballe wrote: > Running the cite tests on ares and the build on the new build server works > fine, from past experience. On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett wrote: > Can we run cite tests on ares to verify the revision numbers, and then > make t

[Geoserver-devel] Jenkins build is back to normal : 2.12-cite-wfs-1.0 #2

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot __

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ? -- Jody Garnett On 6 October 2017 at 09:00, Torben Barsballe wrote: > Hi Ian, > > It looks like the cite tests on the new build server still need a bit more > work before they are fu

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

I noticed that GWC still makes use of this annotation-driven support, is > there the possibility to get rid of it? Another issue I'm facing with this > customization is that at startup GeoServer do not automatically redirects > to the Wicket GUI but to the GWC homepage instead. We ought to just b

[Geoserver-devel] Jenkins build is back to normal : 2.12-cite-wcs-1.1 #2

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] Jenkins build is back to normal : 2.12-cite-wcs-1.0 #2

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot __

Re: [Geoserver-devel] [Geotools-devel] 18.x 2.12.x release blocked

Hi Ian, It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won't be in time for the release. Given that, best bet is probably to use ares. I was

Re: [Geoserver-devel] [Geotools-devel] Release 18.0 & 2.12.0

Okay docs are written and backported (amazing work Torben!) While we know a few areas that can be improved (remove warnings and add datastore examples) it is great to see docs making it in for the release. -- Jody Garnett On 5 October 2017 at 10:23, Jody Garnett wrote: > Thanks Ian, > > I thin

[Geoserver-devel] [JIRA] (GEOS-8323) Add logging to all JDBC Configuration queries

Title: Message Title Steve Ikeoka created

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

Update on GeoWebCache REST and Web Context conflicts... JVM needs to start with the following option -Dgwc.context.suffix=gwc Regards, Alessio Fabiani == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Alessio Fabiani @alfa7691 Fo

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

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] [JIRA] (GEOS-8322) Can't create a mosaic of ASCII Grid files

Title: Message Title Ian Turton created an

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

Needs the GeoTools changes to be in, but the build order was not the lucky one. Should get fixed once GeoTools managed to build Cheers Andrea On Fri, Oct 6, 2017 at 3:47 PM, wrote: > See 5127/changes> > > Changes: > > [andrea.aime]

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

See Changes: [andrea.aime] Follow up with GEOT-5842, first time the nodata in the water temp comes -- [...truncated 117649 lines...] Oct 06, 2017 1:47:25 PM com.hazelcast.initializer

[Geoserver-devel] [JIRA] (GEOS-8321) Monitoring plugin Path Exception

Title: Message Title Alessio Fabiani creat

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

This simple hack will fix the issue String resource = Paths.get(*URLEncoder.encode(request.getPathInfo(), "UTF-8")*).getFileName().toString(); Regards, Alessio Fabiani == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Alessio Fabiani

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

The GWC home page redirect issue still remains, by the way. 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

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

Ok, so, after further investigation I should have got the cause of the issue. Basically this happens when the Monitoring plugin is installed, in particular here https://github.com/geoserver/geoserver/blob/3518cdb07ec159c1ac365fc8583da7ff4b9da89b/src/extension/monitor/core/src/main/java/org/geoser

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

This is currently the customization causing that issue https://github.com/GeoNode/geoserver-geonode-ext I had to rewrite the community plugin by removing everywhere "", otherwise there wasn't the possibility to let it working. I noticed that GWC still makes use of this annotation-driven support,

Re: [Geoserver-devel] Spring MVC PathVariables cannot parse workspaces

Oh, maybe is this the cause? java.nio.file.InvalidPathException: Illegal char <:> at index 19: /sldservice/geonode:san_andres_y_providencia_administrative/attributes.xml at sun.nio.fs.*WindowsPathParser*.normalize(Unknown Source) Regards, Alessio Fabiani == GeoServer Professional Services fro

[Geoserver-devel] Build failed in Jenkins: 2.12-cite-wms-1.3 #1

See -- [...truncated 961 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.12-cite-wms-1.1 #1

See -- [...truncated 961 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] 18.x 2.12.x release blocked

As I said in another message the cite-tests currently don't run on the new build server. I just tried to run the cite tests on ares but that won't work as there is no geoserver-12.x build configured. I'm loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I'm

[Geoserver-devel] Build failed in Jenkins: 2.12-cite-wfs-1.0 #1

See -- [...truncated 1063 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.12-cite-wcs-1.1 #1

See -- [...truncated 964 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.12-cite-wcs-1.0 #1

See -- [...truncated 974 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

Re: [Geoserver-devel] Release 18.0 & 2.12.0

I'm running into an issue running the cite tests for 2.12.x, maven claims not to be able to fetch tomcat:catalina:jar:5.5.9 - I'm not sure if this is an error in the way I set the jobs up, though I just copied the 2.11 jobs over or an issue with the build server. Can some one with log in access ha