See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/204/changes
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/203/changes
Changes:
[jdeolive] changed gt-gml2 artifact id
[jdeolive] changed gt-wps artifact id
[jdeolive] setting svn:ignore
[jdeolive] change to geotools xsd artifact names
[jdeolive] guard around access to logs directory
I've been tripped up by this a fair bit as well. The jetty:run target
doesn't use the compiled war file but pulls in the dependencies declared
in the web module and does some magic to put them into a one-use jetty
instance. So make sure there's a profile in web/pom.xml that pulls in
the wps m
Hi Luca,
A couple of things:
I am not sure if its mandatory... but I think a space after the "-P". So:
mvn -P wps
This also needs to be done from the root, *not* the web directory. If
you don't do it from the root the wps module will never be built.
Also, replace "/geoserver/wps" -> "geoserve
Hi all,
Just a warning to anyone depending on any of the gtxml / xsd maven
artifacts they have indeed changed again, let us hope for the last time.
gt-core -> gt-xsd-core
gt-gml2 -> gt-xsd-gml2
gt-gml3 -> gt-xsd-gml3
gt-filter -> gt-xsd-filter
gt-kml -> gt-xsd-kml
gt-sld -> gt-xsd-kml
gt-wps ->
Could someone point me to a procedure for testing the WPS stuff on the
community schema ?
I tid the following:
mvn clean install -Dmaven.test.skip=true -Pwps,rest
(from the web directory)
And then issued:
mvn jetty:run
...but geoserver/wps?request=getCapabilities got me only a 404.
What am I
Hi Simone,
I noticed some recent commits to XmlConfigReader on trunk. You should
know that part of the recent configuration work makes XmlConfigReader
unused. So we should try to replicate the improvements in the new
configuration reader.
-Justin
--
Justin Deoliveira
The Open Planning Projec
Chris Holmes ha scritto:
> So one of the things I learned about at JavaOne was that there's a lot
> of really cool plugins for Hudson, that will generate reports on trends
> and reveal information about the code.
>
> Some of the more interesting ones were
> * JUnit integration, so you could see
