+1 from me. This will as a side-effect work around Maven's brokenness
with snapshots from some repos (gwc is normally the one that bites me).
On 16/05/12 06:29, Gabriel Roldan wrote:
Hey all,
with gwc / geoserver integration settling down I'd like to adopt the
policy of always pegging
On Tue, May 15, 2012 at 11:51 PM, Chris Holmes chol...@opengeo.org wrote:
For this case in particular, if we want to move faster, I feel comfortable
approving the porting of all code done by OpenGeo employees on OpenGeo time
to GeoTools. It looks like Simone also did some of the work, so I'd
On Wed, May 16, 2012 at 6:16 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
I have encountered a decision point while fixing a bug in WFS 2.0 paging:
https://jira.codehaus.org/browse/GEOS-5085
WFS 2.0 paging is implemented by specifying startindex and count (like
maxFeatures in
On 16/05/12 14:07, Andrea Aime wrote:
In a nutshell, no, we need to grow a way to tell if paging was being
asked for or not.
Can't be done. The problem is you don't know if paging is being asked
for until you get the request for the next page.
First request: Hello, please give me 1000
Thanks, Chris, that sounds like an ideal solution.
On 16/05/12 05:26, Chris Holmes wrote:
I think the thing to do is have the PSC set a policy on migrating code from
GeoServer to GeoTools. I think it could set some threshold under which moving
code over is pre-approved, and that larger
I also found this stability requirement and a rather leading hint from
p41 of the WFS 2.0.0 spec (OGC 09-025r1 and ISO/DIS 19142).
**
7.9.2.5.4.4
Sort processing
A web feature service that receives an ad hoc query expression without a
sorting clause, shall generate a
response document in
Hi ,
I am currently working on geoserver 1.7.x and want to migrate to 2.2 beta
version ,I copied the data folder from 1.7.x version to the 2.2 as
mentioned in one of your blog still all the my layers/styles that i
created in older version (geoserver 1.7.x) is not showing up in geoserver
2.2
On Wed, May 16, 2012 at 8:14 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
On 16/05/12 14:07, Andrea Aime wrote:
In a nutshell, no, we need to grow a way to tell if paging was being
asked for or not.
Can't be done. The problem is you don't know if paging is being asked
for until
On 16/05/12 14:50, Andrea Aime wrote:
Ben, it's a 7 lines mail, how could you miss the second sentence?
less ideally a way to at least detect if maxFeatures was explicitly
provided (if we don't have that either,
it's definitely not paging)
-- you can know if client asked for paging
Andrea,
On Wed, May 16, 2012 at 8:56 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
On 16/05/12 14:50, Andrea Aime wrote:
Ben, it's a 7 lines mail, how could you miss the second sentence?
less ideally a way to at least detect if maxFeatures was explicitly
provided (if we don't have that
To do so it uses the jira rest api (which is nice btw). This is something I
would like feedback on.
Bleck - tough call.
We have a couple of options here on what to do with respect to jira.
1. don't do any checks against jira, and leave that a manual process
In my experience going
The second thing I would like to discuss is how we handle the README.
Currently when we release we update the README on the main branch (and not
the tag). I would kind of like to avoid committing anything to the main
branch in an automated process. For example what happens if we run the
Hey, apologies for a bit of a delay on response to this.
So for me TOPP is just the entity that holds copyright, and it's up to the
PSC to decide any changes to that copyright. So I don't think I'd feel
comfortable with any OpenGeo employee saying it's ok, unless it's the
express wish of the PSC.
Yup. Sorry for missing that email, sounds great.
On Wed, May 16, 2012 at 2:02 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Tue, May 15, 2012 at 11:51 PM, Chris Holmes chol...@opengeo.org
wrote:
For this case in particular, if we want to move faster, I feel
comfortable
approving
You were very fast Justin :)
Don't have time right now to take a deep look at the scripts but I will do
during the we as a personal interest.
Thanks for achieving this.
About JIRA, I also think option 3 is the best one.
Do you still need help to do something in order to close up this task?
+1
Regards,
Alessio.
---
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331
ok then, thanks for the prompt feedback.
I'll apply the change to the root poms on 2.1.x and 2.2.x right away.
Cheers,
Gabriel
On Wed, May 16, 2012 at 11:14 AM, Alessio Fabiani
alessio.fabi...@geo-solutions.it wrote:
+1
Regards,
Alessio.
Hey guys,
My take is more or less the same as Andrea, I think we should do the
following:
1. By default with no startIndex we don't sort
2. By default with startIndex=0 we do sort
3. If cite compliance is turned on we adhere strictly to the spec
Ben I share your disdain for hiding behaviour
Hi Manik,
This is a post more suitable for geoserver-us...@lists.sourceforge.net.
On Wed, May 16, 2012 at 12:29 AM, Manik Goyal manik.go...@rmsi.com wrote:
Hi ,
I am currently working on geoserver 1.7.x and want to migrate to 2.2 beta
version ,I copied the data folder from 1.7.x version to
On Wed, May 16, 2012 at 1:48 AM, Jody Garnett jody.garn...@gmail.comwrote:
To do so it uses the jira rest api (which is nice btw). This is something
I would like feedback on.
Bleck - tough call.
We have a couple of options here on what to do with respect to jira.
1. don't do any checks
On Wed, May 16, 2012 at 1:53 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Wed, May 16, 2012 at 7:55 AM, Justin Deoliveira jdeol...@opengeo.org
wrote:
The end result is all the artifacts wind up in a single directory
matching
the release name. For example:
On Wed, May 16, 2012 at 1:54 AM, Jody Garnett jody.garn...@gmail.comwrote:
The second thing I would like to discuss is how we handle the README.
Currently when we release we update the README on the main branch (and not
the tag). I would kind of like to avoid committing anything to the main
See http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/686/changes
Changes:
[dwinslow] Add lenient XML generation option - GEOS-5084
This adds an option allowing administrators to skip erroneous layers in
WMS, WFS, and WCS capabilities documents as well as WCS DescribeCoverage
and WFS
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/5125/changes
--
This message is automatically generated by Hudson.
For more information on Hudson, see: http://hudson-ci.org/
--
Live Security Virtual Conference
See http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/687/changes
--
This message is automatically generated by Hudson.
For more information on Hudson, see: http://hudson-ci.org/
--
Live Security Virtual Conference
25 matches
Mail list logo
