Whoops, that's right, you did say that.
Okay, I took those examples, did some copyediting on them and fixed the Sphinx
errors, and added them to the pull request. If it looks good to you, I'll
commit on 2.2.x, master, and the newly-created 2.3.x.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo
Mike,
Ok looks good, but still missing the curl examples, don't know if you want
to include them; if so, take a look here:
/en/user/source/restconfig/rest-config-examples/rest-config-examples-curl.rst
https://github.com/ccancellieri/geoserver/commit/d437d1544d389030d2c375b47a837cc71095ef4d
Thank y
Great, I think I have all my questions answered now. Please see
https://github.com/geoserver/geoserver/pull/126. If no changes are necessary,
please accept and port to master as well (or I can do that). Thanks!
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
On 1/29/2013 2:26 AM, carlo can
Hi Mike,
see inline.
I have a few additional questions, but they may be answered when I actually
> try out the software, but I can't seem to find where it is. Some questions
> that come to mind:
>
> * When entering rest/about/manifest.xml?..., what happens when the key
> value pair is omitted? T
Mike,
I agree with you. Note that I also added some cURL examples.
Carlo
2013/1/25 Mike Pumphrey
> Thanks. I will add back in the About content.
>
> After some conversation a while back, I made the decision to remove the
> representation files from the docs as part of this update. Reasons bein
Also, what version does this about/manifest functionality work against? I've
got 2.2.4 installed, and I don't seem to have that endpoint at all. Commands
like this:
http://localhost:8080/geoserver/rest/about/manifest.xml?key=GeoServerModule&value=extension
don't respond with anything other than
Thanks. I will add back in the About content.
After some conversation a while back, I made the decision to remove the
representation files from the docs as part of this update. Reasons being that
they are an administrative hassle to keep correct (there were dozens of them,
and many of them were
Mike,
I'm not excellent at figuring out diffs manually, but looking at that
> commit, I see that the primary difference is the "About" section. Did I
> miss something else? Please let me know, and I'll copy the section(s) back
> in.
We are lucky, I used a different commit only for docs.
Looking
Hello Carlo. My apologies, I'm sorry to have overwritten your work. That does
explain the strange conflicts I found when I tried to merge.
I'm not excellent at figuring out diffs manually, but looking at that commit, I
see that the primary difference is the "About" section. Did I miss something
Hi Mike,
I think we have missed (cutted off) some pieces of documentation during
this "Improved / corrected REST documentation (see GEOS-5595)" refactoring
(regarding the about/version about/manifest improvements):
please take a look to:
on branch 2.2.x - the commit "619156c0e2a0946b58ea0e3877dfda
I think you should be fine here Mike. I think jody is going to be trying a
2.3 release again tonight but this shouldn't conflict.
On Tue, Jan 22, 2013 at 11:44 AM, Mike Pumphrey wrote:
> This pull request updates /corrects the REST API documentation. I know
> that we are in the middle of a rel
This pull request updates /corrects the REST API documentation. I know that we
are in the middle of a release process, so I just wanted to ask (specifically
Andrea) if it's okay if I go ahead and merge it in, or whether I should wait.
https://github.com/geoserver/geoserver/pull/111
Thanks,
12 matches
Mail list logo
