Hello, I noticed this last night, but just confirmed it again with a fresh build this morning.
After following the README info in the patch in https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel I see that I can successfully build and run Shindig using: +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? Is this a problem, or is there another simple way to get my code change picked up when I fire up the server? -Chris -- Chris Schalk, Google Developer Advocate
