You can also do this: cd java/server mvn jetty:run
This starts a jetty instance running on most resources in place (including content and webapp directories). After you do a build you can press enter to reload the server instance. On May 17, 2010, at 2:42 AM, franck tankoua wrote: > My guess is that the jar files get's loaded when the server starts. > So this is why you need to reboot the server. > > If I had consistent modification to do on the jar project , I would test > them via unittest classes to validate my changes. After this step, I would > then build the jar and reboot the server. > > > On Sat, May 15, 2010 at 10:50 AM, Evgeny Bogdanov > <[email protected]>wrote: > >> Thank you for the info (I do want the changes on jar projects) >> I seem to have found a solution. Though there is still one more problem. >> >> 1) My jetty server in eclipse points now to shindig/java/server >> 2) debugger is linked to this jetty server >> 3) I use "mvn" command to build the project >> >> Now for the changes to be taken I have to re-run all 3 command above. >> Here it sais that normally I have to only rebuild project, and don't have >> to restart jetty: >> >> >> http://shindig.apache.org/developers/java/build.html >> >> Is this the case for you? >> >> >> On 14/5/10 19:47, franck tankoua wrote: >> >>> Hi, >>> I am using "war:inplace: for my server project ( which replace the >>> shindig-server) >>> THis helps building automatically my code in eclipse and having my changes >>> ready to test. But if you are doing changes in on the jar projects >>> (gadgets, >>> social-api, common...) you will need to build them again as Han said. >>> >>> One example which comes to mind is : changing the container.js in >>> shindig-common will require running the mvn build command again to have >>> you >>> jar file updated. >>> >>> >>> On Fri, May 14, 2010 at 7:35 PM, Han Nguyen<[email protected]> wrote: >>> >>> >>> >>>> Evgeny, >>>> Shindig is a maven project, setting eclipse build automatically on is not >>>> enough. You will need to run the maven build again to update your >>>> changes. >>>> Hope that helps. >>>> Han >>>> >>>> >>>> >>>> From: Evgeny Bogdanov<[email protected]> >>>> To: "[email protected]"<[email protected]> >>>> Date: 05/14/2010 11:34 AM >>>> Subject: How to build in eclipse >>>> >>>> >>>> >>>> I am trying to debug a java version in eclipse ... no luck ( >>>> >>>> I set it up according to: >>>> http://shindig.apache.org/developers/java/build.html >>>> >>>> The debugger works as expected. >>>> However if I change the code, the changes are not taken. >>>> "Project -> Build automatically" is checked in eclipse >>>> >>>> "Right click on the project -> Run As.. -> Maven build " gives >>>> [INFO] Scanning for projects... >>>> [ERROR] The build could not read 1 project -> [Help 1] >>>> [ERROR] The project >>>> org.apache.shindig:shindig-gadgets:1.1-BETA6-SNAPSHOT >>>> (/Library/WebServer/Documents/shindig/java/gadgets/pom.xml) has 2 errors >>>> [ERROR] >>>> 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be >>>> unique: net.sourceforge.nekohtml:nekohtml:jar -> duplicate declaration >>>> of version (?) >>>> [ERROR] >>>> 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be >>>> unique: org.apache.shindig:shindig-common:test-jar -> duplicate >>>> declaration of version (?) >>>> [ERROR] >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>>> -e switch. >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>> [ERROR] >>>> [ERROR] For more information about the errors and possible solutions, >>>> please read the following articles: >>>> [ERROR] [Help 1] >>>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException >>>> >>>> Thanks in advance >>>> Evgeny >>>> PS: >>>> Eclipse Java EE IDE for Web Developers. >>>> Build id: 20100218-1602 >>>> Mac OSX 10.6.3 >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> > > > -- > Franck
