Gabriel, sorry for the delay ... I will probably take a look at the branch
during the weekend, however I like the idea of adopting OGC filter as we
discussed in past emails on predicate; so in general I am favourable with
this choice.
Will report feedbacks as soon as possible. Thanks for you
Just to chime in that i echo Gabriel and Jody. With an emphasis on the most
important requirement for PSC members is trying to contribute to evaluating
proposals and other things that require voting when they are offered. So if
you think that is possible i am in full support of you continuing on
Nope, this makes sense. Actually the schema requires just a uri, not a url
so it should be perfectly valid to do this. ANy interest in taking this one
on Michael?
On Wed, Jul 25, 2012 at 9:16 PM, Gabriel Roldan grol...@opengeo.org wrote:
I personally have no objection in relaxing the URL
Gabriel
Yeah I can tackle this. I'm thinking the warning Gabriel mentioned but only if
the field value is not a full URL and the proxy URL is not set. This would
result in an inaccessible URL in the capabilities response.
Michael
On Jul 26, 2012, at 6:28 AM, Justin Deoliveira
GeoServer VERSION.txt contains information that is very useful in
identifying the GeoServer and GeoTools snapshots contained in a build:
version = 2.3-SNAPSHOT
git revision = f4823f9d60ec66ba64bde591ccd6b096fb0bc7ce
git branch = f4823f9d60ec66ba64bde591ccd6b096fb0bc7ce
build date = 20120727-0501
Thanks for letting us know, Mark. We look forward to your ongoing
contributions.
Kind regards,
Ben.
On 27/07/12 11:40, Mark Leslie wrote:
I'm sorry for missing the last meeting, but I fell ill and just
couldn't be online.
I've been having a hard look at my involvement on the PSC and while I
Hi Victor,
we should be good on the gwc side. Pegged 2.2.x to 1.3-RC4 and backported
the needed fixes to geoserver.
I'm waiting on the 2.2.x hudson build right now but it worked just fine on
my dev box with an empty mvn repository. Fingers crossed nonetheless.
Lets talk tomorrow (today?) Friday
