[Geotools-devel] Jenkins build is back to normal : geotools-15.x #12

See -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM r

[Geotools-devel] GeoTools / GeoServer Meeting 2016-05-17

GeoTools / GeoServer Meeting 2016-05-17 === Attending - Ben Caradoc-Davies Jody Garnett Torben Barsballe Jukka Rahkonen Jim Hughes Apologies - Brad Hards Andrea Aime Ian Turton Kevin Smith Agenda -- - Skype upgrade - Boundless artifactor

[Geotools-devel] Build failed in Jenkins: geotools-14.x #134

See Changes: [nuno.oliveira] [GEOT-5419] Fix NetCDFImageReaderSpi file dispose -- [...truncated 11704 lines...] [INFO] Installing

Re: [Geotools-devel] Copyright header policy

I do not think option D can work with a distributed version control system. I think this option is unimplementable with git. If we eliminate D, then C is the winner. Kind regards, Ben. On 18/05/16 07:05, Ben Caradoc-Davies wrote: > Instant runoff voting give a win for D: > https://en.wikipedia.

Re: [Geotools-devel] Copyright header policy

Instant runoff voting give a win for D: https://en.wikipedia.org/wiki/Instant-runoff_voting Round 1: A eliminated Round 2: B eliminated Round 3: D wins with 3/5 votes Kind regards, Ben. On 18/05/16 01:21, Justin Deoliveira wrote: > Thanks for kicking this one Andrea. > > Using a simple weighted

Re: [Geotools-devel] Copyright header policy

Hi, I'm not a PSC so I'm not voting, but when taking a look at the options just out of curiosity, I had the same doubt reported by Justin in relation to D. Wondering If with approach D, the auto-change on commit, you are basically always out of sync? Cheers, Daniele On Tue, May 17, 2016 at 3:21 P

Re: [Geotools-devel] Copyright header policy

Thanks for kicking this one Andrea. Using a simple weighted scoring where first pick gets 4 points, second 3, etc… the current votes come out to: A: 5 B: 12 C: 12 D: 11 Which means a tie between methods B and C… so ideally the other PSC members could get there votes in on this one so things can

[Geotools-devel] Jenkins build is back to normal : geotools-master #1097

See -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM rest

Re: [Geotools-devel] Builds failing due to repository authorizations

Hi Christian, I've kicked another one, let's see Cheers Andrea On Tue, May 17, 2016 at 2:16 PM, Christian Del Pino < cdelp...@boundlessgeo.com> wrote: > Hi Andrea, > > Not sure about the doc deploy, since that seems to be going to OSGeo. > Maybe coincidence? > > Regards, > Chris > > On Tue, May

Re: [Geotools-devel] Builds failing due to repository authorizations

Hi Christian, this one looks like it managed to get the deploy on the repo, and then failed on the documentation deploy on OSGeo: + scp index.zip geotools.org:/home/geotools/latest + ssh geotools.org svn up update_site.sh && ./update_site.sh latest Updating 'update_site.sh': svn: E000104: Unable t

[Geotools-devel] Build failed in Jenkins: geotools-master #1096

See -- [...truncated 58434 lines...] adding: unsupported/geometry/ (stored 0%) adding: unsupported/geometry/index.html (deflated 66%) adding: unsupported/geometry/build.html (deflated 77%

Re: [Geotools-devel] Builds failing due to repository authorizations

Sure, kicked a new one now: http://ares.boundlessgeo.com/jenkins/job/geotools-master/1096/ It's going to take a while, before it builds everything with tests, and only later it pushes the artifacts to the repos Cheers Andrea On Tue, May 17, 2016 at 12:27 PM, Christian Del Pino < cdelp...@boundles

[Geotools-devel] Build failed in Jenkins: geotools-master #1095

See -- [...truncated 19327 lines...] [INFO] Vector grids [INFO] Validation Processor and Framework [INFO] Web Map Server client [INFO] KML XML Support [INFO] WCS XML Support [INFO] WPS XML Supp

Re: [Geotools-devel] Builds failing due to repository authorizations

Hi Christian, unfortunately not, I did not setup the deploy jobs... I believe you should be able to find it in a settings.xml file inside the maven repository, e.g. I have something like this in my /home//.m2/settings.xml: boundless *aUserNameHere* *aTokenHere*

[Geotools-devel] Build failed in Jenkins: geotools-14.x #133

See Changes: [andrea.aime] [GEOT-5420] Performance regression creating image mosaic reader against databases with thousands of tables -- [...truncated 11755 lines...] [INFO] Deleting

[Geotools-devel] Builds failing due to repository authorizations

Hi, it seems the geootools builds are failing in the deploy phase due to authorization issues: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project geotools: Failed to deploy artifacts: Could not transfer artifact org.geotools:geotools:

[Geotools-devel] Build failed in Jenkins: geotools-15.x #11

See Changes: [andrea.aime] [GEOT-5420] Performance regression creating image mosaic reader against databases with thousands of tables -- [...truncated 19248 lines...] [INFO] Vector grids

[Geotools-devel] Build failed in Jenkins: geotools-master #1094

See Changes: [andrea.aime] [GEOT-5420] Performance regression creating image mosaic reader against databases with thousands of tables -- [...truncated 19309 lines...] [INFO] Vector gr