Thanks Alex.. Actually I found that I have to jump up to /java and do rebuild (package):
mvn package (from /java) then cd to /java/server mvn jetty:run-war Maybe there's a more direct way, but this seems to be the fastest way I can find to see my code change take effect. -Chris On Fri, Apr 25, 2008 at 10:16 AM, Alexander Klimetschek <[EMAIL PROTECTED]> wrote: > mvn jetty:run-war doesn't rebuild the project, it only starts jetty and > assumes the war under target/whatever.war to be present (or it rebuilds the > war, but it definitely does not rebuild the current project's jar). To > rebuild, you should include the "package" goal, ie. try this: > > mvn package jetty:run-war > > That should do the trick. > > Alex > > Am 25.04.2008 um 18:35 schrieb Christian Schalk: > > +2) Build the source and start the server in debug mode >> + cd shindig/java >> + mvn install >> + cd server >> + mvndebug jetty:run-war >> >> However if I make a change to the code.. such as changing a class in the >> social-api area, >> >> (ex:social-api/src/main/java/org/apache/shindig/social/samplecontainer/...) >> I find that I have to do another "mvn install" at the top level to see my >> change ... which seems overkill since mvn jetty:run-war repackages the war >> anway? >> > > -- > Alexander Klimetschek > [EMAIL PROTECTED] > > >> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ << > > > > > -- Chris Schalk, Google Developer Advocate
