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

Intermittent failure unrelated to this change: [GEOS-8038] Intermittent build failure in gs-restconfig CoverageStoreTest.testDeletePurgeAllAfterConfigure https://osgeo-org.atlassian.net/browse/GEOS-8038 On 11/04/17 17:07, moni...@boundlessgeo.com wrote: > See

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

See Changes: [emerkle] Re-enable GeoGig plugin in communityRelease module -- [...truncated 161346 lines...] Running org.geoserver.security.cas.CasAuthenticationTest Apr 11, 2017

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

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] Removed doc and geogig Git polling exclusions on geoserver-master Jenkins

For docs at least, there was an effort to separate the doc build and the code build so if a doc change was made we would only build the docs, and if a code change was made we would only build the code. Consequently, the docs are excluded from the polling for the main builds. See the *-live-docs

[Geoserver-devel] Build failed in Jenkins: geoserver-2.9.x #416

See Changes: [emerkle] Re-enable GeoGig plugin in communityRelease module -- [...truncated 652 lines...] [INFO]

Re: [Geoserver-devel] Removed doc and geogig Git polling exclusions on geoserver-master Jenkins

I removed the exclusions on 2.9.x as well, even though it is unsupported. On 11/04/17 11:07, Ben Caradoc-Davies wrote: > I have removed the exclusions for 2.11.x > and 2.10.x, even though they have not yet caused trouble. This gives us > consistency between the builds. -- Ben Caradoc-Davies

Re: [Geoserver-devel] Removed doc and geogig Git polling exclusions on geoserver-master Jenkins

Erik, thanks for pointing that out. I have removed the exclusions for 2.11.x and 2.10.x, even though they have not yet caused trouble. This gives us consistency between the builds. I do not know the precise circumstances that cause a build flood, but it seems that removing the exclusions

Re: [Geoserver-devel] Removed doc and geogig Git polling exclusions on geoserver-master Jenkins

Unknown. I have not found a bug report that matches our situation. As I mentioned in my previous email, I do not see why we are excluding commits to docs and geogig in the first place. Shall we just leave them in? Kind regards, Ben. On 11/04/17 08:53, Jody Garnett wrote: > Is this something

Re: [Geoserver-devel] Removed doc and geogig Git polling exclusions on geoserver-master Jenkins

Is this something fixed with newer versions of Jenkins? -- Jody Garnett On 9 April 2017 at 17:56, Ben Caradoc-Davies wrote: > I have removed the doc and geogig Git polling exclusions on > geoserver-master Jenkins. As discussed last year (see below), Git polling > exclusions

Re: [Geoserver-devel] GSIP-157 - Track change state in CatalogPostModifyEvent

It's bee a while too, no objections, so yeah (imho, but I don't remember the rules by heart) Cheers Andrea On Mon, Apr 10, 2017 at 6:40 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > Now that this has gotten at least 50% +1's, are we good to merge? PR is > here:

Re: [Geoserver-devel] GSIP-157 - Track change state in CatalogPostModifyEvent

Now that this has gotten at least 50% +1's, are we good to merge? PR is here: https://github.com/geoserver/geoserver/pull/2101 Torben On Tue, Apr 4, 2017 at 10:30 AM, Kevin Smith wrote: > On 2017-03-20 09:09 AM, Torben Barsballe wrote: > > This was initially proposed just

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

Hi Andrea, On 04/10/2017 03:06 PM, Andrea Aime wrote: > Hi, > sorry I lost track of the subject. So, to close up, and approach where the > envelope is reported as "lat lon" and the "i j" raster space > axis would map pairwise, so i pointing north-wards and j east-wards, would be > considered

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

Hi all, why not simply check against the compliance tests of WCS 2 and maybe a reference implementation? Might be the easiest for answering all such questions. cheers, Peter On 04/10/2017 04:23 PM, Even Rouault wrote: > > On lundi 10 avril 2017 15:57:03 CEST Andrea Aime wrote: > > > Hi Even,

Re: [Geoserver-devel] Removed doc and geogig Git polling exclusions on geoserver-master Jenkins

Ben, Thanks for the info, I wasn't aware of the issues. It seems the exclusions are still in place for the other builds (2.11.x, 2.10.x and 2.9.x). I can remove them on those builds too, unless it is desired to keep them. Erik Merkle Software Engineer | Boundless

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

Hi, Even wrote: However I'm not sure in which way GDAL is involved in this discussion :-) I am preparing for the future when GDAL will have a support for WCS 2.0.1 and it will try to read EPSG:4326 coverage data from GeoServers witch describe coverage like this:

[Geoserver-devel] [JIRA] (GEOS-8082) Parameters extractor plugin and integrated GWC issues

Title: Message Title Davor Racic created

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

On lundi 10 avril 2017 15:57:03 CEST Andrea Aime wrote: > Hi Even, > in CIS 1.1 they state: > > Coverages are assumed to have a 1:1 correlation between the axis names > given in axis-Labels and gridLabels, i.e.: they shall relate pairwise, > given by their sequence position. For example,

[Geoserver-devel] [JIRA] (GEOS-8081) WCS 2.0 does not support vendor CQL_FILTER parameter like WCS 1.0 and 1.1 do

Title: Message Title Andrea Aime

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

Hi Even, in CIS 1.1 they state: Coverages are assumed to have a 1:1 correlation between the axis names given in axis-Labels and gridLabels, i.e.: they shall relate pairwise, given by their sequence position. For example, axisLabels=“Lat Long h date” and gridLabels={i j k l} implies a

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

On lundi 10 avril 2017 15:06:55 CEST Andrea Aime wrote: > Hi, > sorry I lost track of the subject. So, to close up, and approach where the > envelope is reported as "lat lon" and the "i j" raster space > axis would map pairwise, so i pointing north-wards and j east-wards, would > be considered

Re: [Geoserver-devel] [gdal-dev] GML lat-lon coverages and interoperability

Hi, sorry I lost track of the subject. So, to close up, and approach where the envelope is reported as "lat lon" and the "i j" raster space axis would map pairwise, so i pointing north-wards and j east-wards, would be considered valid? E.g., if one rescaling says "i is going to be 200 pixels" it

[Geoserver-devel] [JIRA] (GEOS-8080) geoserver does not differ between global styles and standard workspace styles

Title: Message Title Tobias Warneke