Re: [Geoserver-devel] style schema duplication (was color blending example not valid)

On Thu, Apr 9, 2015 at 12:28 AM, Jody Garnett wrote: > Kevin has tracked down the duplication for GEOS-6971 > (see #1010 > ) and patched the > geoserver copy of the schema file. > > We still have

Re: [Geoserver-devel] style schema duplication (was color blending example not valid)

Do you have the validator error handy? -- Jody Garnett On 8 April 2015 at 15:35, Kevin Smith wrote: > I noticed that and tried to pull in the GeoTools version of the schema but > ended up with a different validation error for my trouble. > > > https://github.com/geoserver/geoserver/blob/master/

Re: [Geoserver-devel] style schema duplication (was color blending example not valid)

I noticed that and tried to pull in the GeoTools version of the schema but ended up with a different validation error for my trouble. https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/vfny/geoserver/util/SLDValidator.java#L200 ---

[Geoserver-devel] style schema duplication (was color blending example not valid)

Kevin has tracked down the duplication for GEOS-6971 (see #1010 ) and patched the geoserver copy of the schema file. We still have duplication between the following two files: GeoServer: StyledLa

Re: [Geoserver-devel] Ticket default assignee in the new jira

-0 If a module has a contact point it should be up to them if they want issues auto-assigned. I recognize we have fallen out of the habit of having module maintainers (gradually relying on the PSC and then Andrea for maintenance). If leaving issues unassigned helps us to feel more comfortable fix

Re: [Geoserver-devel] Ticket default assignee in the new jira

On 9/04/2015 6:28 a.m., Ben Caradoc-Davies wrote: > Sounds good to me. The automatic assignment in the old Jira just gave > users false hope. :-) I agree! It is realistic and what we do with internal jira. Notice: This email and any attachments are confidential. If received in error please destro

Re: [Geoserver-devel] Ticket default assignee in the new jira

Sounds good to me. The automatic assignment in the old Jira just gave users false hope. :-) Kind regards, Ben. On 08/04/15 19:21, Andrea Aime wrote: > Hi, > the new Jira server defaults to have the newly created tickets assigned to > no-one. > I was planning to leave it that way, and when someo

[Geoserver-devel] Reducing the amount of datastore interactions for small GetFeature requests

Hi, in the current WFS architecture GeoServer is setup to "favour" large requests, with a fully streaming protocol that helps serving back basically limitless amount of GML without having to be memory bound... at most, we are disk bound in certain output formats (shape-zip, we have to write the sha

Re: [Geoserver-devel] GeoFence REST API -- Re: geofence geoserver integration

On Wed, Apr 8, 2015 at 3:40 PM, Emanuele Tajariol wrote: > Hi Niels, > > GeoFence used to provide a REST interface, > > https://github.com/geoserver/geofence/tree/master/src/services/modules/rest > but, after the last improvements and refactoring, it needs some review and > fixing. > You can find

[Geoserver-devel] GeoFence REST API -- Re: geofence geoserver integration

Hi Niels, GeoFence used to provide a REST interface, https://github.com/geoserver/geofence/tree/master/src/services/modules/rest but, after the last improvements and refactoring, it needs some review and fixing. You can find the (old) related doc here: http://goo.gl/NjkvGn (it was partial

Re: [Geoserver-devel] Branching GeoFence 2.2.x -- Re: geofence geoserver integration

Emanuele, Thanks! I have added the version updates to my pull request. Something else, I need to also make a REST API available on the integrated geofence. Of course I only need the Rules API. Do you have any recommendations on how to do that? You reckon I should make a new one in geoserver and

Re: [Geoserver-devel] Branching GeoFence 2.2.x -- Re: geofence geoserver integration

Hi Niels, > When the geofence 3.0 branch is there I will update On master branch the version has been updated to 3.0-SNAPSHOT: https://github.com/geoserver/geofence/blob/master/src/pom.xml#L15 The refactor branch has already been merged into master. Cheers, Emanuele Alle 12:55:36

Re: [Geoserver-devel] Branching GeoFence 2.2.x -- Re: geofence geoserver integration

Hello Emanuele, That sounds good. When the geofence 3.0 branch is there I will update the versions in the geoserver modules. Thanks! Let me know if you need anything else from me. Regards Niels On 07-04-15 12:40, Emanuele Tajariol wrote: > Hi Niels, > > ok, some changes in the geofence branches

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

See -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process

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

See Changes: [lago.88] GEOS-6960: Updating GS code after viewsManager cleanup (GEOT-5050) [andrea.aime] Some extra checks to better understand the random windows build failures in this area [lago.88] GSIP-128 JAIEXT int

Re: [Geoserver-devel] Ticket default assignee in the new jira

+1 Makes sense Cheers Christian On Wed, Apr 8, 2015 at 9:39 AM, Rahkonen Jukka (MML) < jukka.rahko...@maanmittauslaitos.fi> wrote: > Hi, > > > > +1 > > > > Assign to nobody reflects the reality. > > > > -Jukka- > > > > Andrea Aime wrote: > > > > Hi, > > the new Jira server defaults to have the

Re: [Geoserver-devel] Ticket default assignee in the new jira

Hi, +1 Assign to nobody reflects the reality. -Jukka- Andrea Aime wrote: Hi, the new Jira server defaults to have the newly created tickets assigned to no-one. I was planning to leave it that way, and when someone decides to pick on the ticket, they could assign it to themselves to show work

Re: [Geoserver-devel] Ticket default assignee in the new jira

+1 Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39

[Geoserver-devel] Ticket default assignee in the new jira

Hi, the new Jira server defaults to have the newly created tickets assigned to no-one. I was planning to leave it that way, and when someone decides to pick on the ticket, they could assign it to themselves to show work is ongoing (or is going to start soon), in the interest of avoiding duplicate w