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 module (sounds like this is already taken care of) and then use $ mvn jetty:run -Pwps,rest to include wps in your trial run. It doesn't stick, so you need to do this each time you run it.
-David ps: for the record, the space is optional between -P and the profile list. Luca Morandini wrote: > 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 missing ? > > -------------------- > Luca Morandini > www.lucamorandini.it > -------------------- > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:4040,484315a2251231637810514! > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
