Re: [Geoserver-devel] [Geotools-devel] MVN repo.boundlessgeo having problems?

On Tue, Oct 27, 2015 at 10:03 AM, Ian Turton wrote: > OK I've reverted that PR but it builds on my machine so I assumed the > travis fail was due to the repo issue, I'll check some more later. > Thanks! Cheers Andrea -- == GeoServer Professional Services from the experts!

Re: [Geoserver-devel] [Geotools-devel] MVN repo.boundlessgeo having problems?

OK I've reverted that PR but it builds on my machine so I assumed the travis fail was due to the repo issue, I'll check some more later. Ian On 26 October 2015 at 20:49, Andrea Aime wrote: > On Mon, Oct 26, 2015 at 9:26 PM, Torben Barsballe < >

[Geoserver-devel] [JIRA] (GEOS-7279) Extend CSW DirectDownload link with support for vectorial stores

Title: Message Title Daniele Romagnoli created an issue

[Geoserver-devel] [JIRA] (GEOS-7277) W3DS capabilities do not take into account proxy url

Title: Message Title François Van Der Biest created an issue

[Geoserver-devel] [JIRA] (GEOS-7278) W3DS demos use external ressources

Title: Message Title François Van Der Biest created an issue

Re: [Geoserver-devel] Resources port

Jody, Small addition. With respect to point (1), I know about GeoServerResourceLoader.lookupGeoServerDataDirectory(servletContext), but then we are bypassing the ResourceStore API and missing some of its generic purpose. The point is if we're making a GeoServerResourceLoader from a

Re: [Geoserver-devel] Resources port

Hello Jody, Thanks for your email! That clarifies at least which direction we should be going with some of these issues. A few remaining important points: 1. Can you fill me in on a way to get the path to the DataDirectory without calling dir() ? I'll have to make a patch for that then, but

[Geoserver-devel] [JIRA] (GEOS-7280) Avoid catalog linear scans in GWC integration listeners

Title: Message Title Andrea Aime [Administrator] created an issue

Re: [Geoserver-devel] Jetty upgrade?

On Tue, Oct 27, 2015 at 5:15 PM, Jody Garnett wrote: > So review completed, merge when ready. Unless anyone else wants a crack at > it ... I'd say... merge :-p Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more

[Geoserver-devel] LayergroupInfo changes

Hi, I want to propose some minor API changes for the catalog, will make a proper proposal but just wanted to check already if I can expect this to be an issue or not. 1. Move property [AttributionInfo attribution] from LayerInfo to PublishedInfo, so that Layergroups can have this as well. 2.

Re: [Geoserver-devel] Jetty upgrade?

We are running GeoServer 2.7.2 on Jetty 9.2 and Java 8 in a production capacity, so far without issue (RHEL 6.6). Just thought I'd throw that in there. Jason Newmoyer Newmoyer Geospatial Solutions 843.606.0424 ja...@newmoyergeospatial.com On Mon, Oct 26, 2015 at 3:14 PM, Justin Deoliveira

Re: [Geoserver-devel] Jetty upgrade?

So review completed, merge when ready. Unless anyone else wants a crack at it ... On Tue, Oct 27, 2015 at 9:12 AM Jason Newmoyer wrote: > We are running GeoServer 2.7.2 on Jetty 9.2 and Java 8 in a production > capacity, so far without issue (RHEL 6.6). > > Just

Re: [Geoserver-devel] Jetty upgrade?

Thanks for the review guys. Pull request merged. I’ll keep an eye out for any unexpected issues that pop up. On Tue, Oct 27, 2015 at 10:21 AM, Andrea Aime wrote: > On Tue, Oct 27, 2015 at 5:15 PM, Jody Garnett > wrote: > >> So review

Re: [Geoserver-devel] LayergroupInfo changes

On Tue, Oct 27, 2015 at 6:53 PM, Jody Garnett wrote: > Good point Andrea, I wonder if it is worth making seperate pages for the > different kinds of layer group? Some of these options only make sense when > the layer group is named (and thus drawable) for example. > I

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

See -- [...truncated 9068 lines...] [exec] at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpression.java:551) [exec] at

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

See -- [...truncated 1313 lines...] all: build.script: build.script: data: webapp.scripts: [mkdir] Created dir:

Re: [Geoserver-devel] LayergroupInfo changes

Yeah okay I like that. I had a proposal a while back to organize our pages with consistent headings (like GetCapabilities for all the title, abstract, metadataish stuff). For now I would follow what is done for a layer - or at least use the same tab tiles for consistency. -- Jody Garnett On 27

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

See -- [...truncated 1385 lines...] war: [zip] Building zip: jar.realm: compile: [mkdir] Created

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

See -- [...truncated 1322 lines...] [mkdir] Created dir: webapp.script: [mkdir] Created

Re: [Geoserver-devel] Forwarding authentication headers to cascaded WFS store

Hey Jason, this question may be more suitable to the user list (the devel list is focused on working on the geoserver codebase itself). It is a bit tough to ask for public feedback on your custom data sources - perhaps you would like to check the support page for a

Re: [Geoserver-devel] LayergroupInfo changes

On Tue, Oct 27, 2015 at 5:32 PM, Niels Charlier wrote: > Hi, > > I want to propose some minor API changes for the catalog, will make a > proper proposal but just wanted to check already if I can expect this to > be an issue or not. > > 1. Move property [AttributionInfo

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

See Changes: [jdeolive] GEOS-4239, upgrading jetty to version 9.2. [jdeolive] GEOS-4239, updating assembly to accommodate jetty upgrade. [jdeolive] Locking down slf4j to 1.7.10 [jdeolive] GEOS-4329, updated mac installer for

Re: [Geoserver-devel] LayergroupInfo changes

There is an outstanding proposal that Kevin was putting together - that may be related. * https://github.com/geoserver/geoserver/wiki/GSIP-130 -- Jody Garnett On 27 October 2015 at 09:32, Niels Charlier wrote: > Hi, > > I want to propose some minor API changes for the

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

See -- [...truncated 3244 lines...] [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409) [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409)

Re: [Geoserver-devel] LayergroupInfo changes

Good point Andrea, I wonder if it is worth making seperate pages for the different kinds of layer group? Some of these options only make sense when the layer group is named (and thus drawable) for example. -- Jody Garnett On 27 October 2015 at 10:44, Andrea Aime

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wfs-1.0 #27

See -- [...truncated 3244 lines...] [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409) [exec] at

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

See -- ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wms-1.1 #27

See -- [...truncated 9003 lines...] [exec] at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpression.java:551) [exec] at

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wcs-1.0 #27

See -- [...truncated 1385 lines...] war: [zip] Building zip: jar.realm: compile: [mkdir]

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wcs-1.1 #27

See -- [...truncated 1313 lines...] all: build.script: build.script: data: webapp.scripts: [mkdir] Created dir:

[Geoserver-devel] [JIRA] (GEOS-7281) WPS - No Argument Process doesn't enter RUNNING state

Title: Message Title David Blasby created an issue

[Geoserver-devel] Community Script-Core: test cases problem

Hi, I created another pull request to fix the test case failure in community's Script-core module. This was a trivial whitespace problem in the comparison. PR : https://github.com/geoserver/geoserver/pull/1306 issue: https://osgeo-org.atlassian.net/browse/GEOS-7282 Thanks, dave

Re: [Geoserver-devel] Pulls for WPS changes and fixes

Thanks Dave, generally only message the list if you need specific review/feedback. There is no need to double up on email and pull request communication. You may also wish to add a comment to your pull request mentioning a specific party needed for a review (for example mentioning Mike for a

[Geoserver-devel] [JIRA] (GEOS-7282) Script-Core: test cases are not passing

Title: Message Title David Blasby created an issue

[Geoserver-devel] Pulls for WPS changes and fixes

I'm starting to put my pull requests up for a series of changes and fixes for WPS. Here's the first; PR:https://github.com/geoserver/geoserver/pull/1305 issue: https://osgeo-org.atlassian.net/browse/GEOS-7281 This is a very simple fix to resolve an issue shown by the Python Scripting