Hi Martin,
I appreciate your patience, as you can see the python extension is still
pretty rough around the edges. That said this problem should be fixed now so
you can grab the latest nightly build [1] and try again.
The issue was how the jar was being built, the necessary files to enable it
to
Hi Justin, I really really apreciate all the help!
I now have a working Geoserver 2.1beta2 with Pyhon module running.
I intend to use it with the WPS extension. But it seems it doesen't read my
foo.py proces. A proces dir is not created when starting the
wps-querybuilder. It dosen't read the pro
Perhaps we could host the geoscript-python module in the OpenGeo maven
repository? I've taken this approach for the CSS module (also relies on a
library that lives in github) and it seems quite reliable compared to github
SVN.
--
David Winslow
OpenGeo - http://opengeo.org/
On Thu, Dec 16, 2010 a
I see Justin,
I'm working with geoserver + geotools and I agree with you that the API of
geoscript is really simple. I've worked with jython + geoscript and it's
really cool. :D
About the python extension, is it too complex to create 2 extensions? I
mean, one for only python and another for geosc
Sorry, Martin., I'm the one who kicked the python module out of the
build. Here is the problem we were seeing intermittently with githib:
http://jira.codehaus.org/browse/GEOS-4124
On 16/12/10 23:58, Justin Deoliveira wrote:
> Hi Martin,
>
> So as it turns out the python stuff is not actually hook
Hi Emilio, good question. You are technically correct in that you could use
the python extension without geoscript and just access geoserver/geotools
classes directly.
However the goal of the geoscript project is to provide a more script
friendly, and simpler api for geotools than the native geoto
Hi Martin,
So as it turns out the python stuff is not actually hooked up to the nightly
builds due to an issue with pulling in geoscript from github that i have yet
to fix. So long story short the changes were not pulled in.
I have put up a build manually that should work with any recent 2.1 nigh
Hmmm... i am sure it is just something else. I never tried with the actual
nightly build, just my development environment. I will try again when i get
a minute and report back.
On Tue, Dec 14, 2010 at 8:48 PM, Martin Jensen <
martin.martinjen...@gmail.com> wrote:
> I tried again today with no luc
I tried again today with no luck. Maybe I am missing something ? Does the
Pyhon module depend on something else?
/Martin
2010/12/9 Martin Jensen
> Thanks for the quick fix.
>
> I still get the error though. Today I tried to install a new GS and new
> python plug in from:
>
>
> http://gridlock.
Thanks for the quick fix.
I still get the error though. Today I tried to install a new GS and new
python plug in from:
http://gridlock.opengeo.org/geoserver/trunk/community-latest/geoserver-2.1-SNAPSHOT-python-plugin.zip
http://gridlock.opengeo.org/geoserver/trunk/geoserver-trunk-latest-war.zip
Hi Martin,
Thanks for the bug report, this was indeed an issue. I just committed a fix
and fired off a new nightly build [1] so if you grab the next extension to
pop out you should be good to go.
-Justin
[1] http://hudson.opengeo.org/hudson/job/geoserver-trunk-nightly/527
On Tue, Dec 7, 2010 at
Hi GS-list,
I am trying to install the python extension from
http://gridlock.openplans.org/geoserver/trunk/community-latest/geoserver-2.1-SNAPSHOT-python-plugin.zip
with GS 2.1-beta2 from
http://downloads.sourceforge.net/geoserver/geoserver-2.1-beta2-war.zip
GS can't start after copying these j
12 matches
Mail list logo
