I've seen this in the past where Eclipse will reference the jar files in the classpath instead of the workspace. I don't have a specific answer for you. As I recall I ended up having to build/deploy from Eclipse to solve this particular issue. Another option may be to use remote debugging with.
You may also want to try running jetty:run from the java/server project instead of the top level 'run'. On Thu, Sep 30, 2010 at 1:56 AM, Rocks Wang <[email protected]> wrote: > Hi dear all, > > > > I am new to Shindig and trying to tame shindig for our SNS site. > > Thanks for the info in wiki now I have made shindig running so my second > attempt is making it debuggable via eclipse Helios. > > Here're my steps: > > 1. Import shindig into eclipse. I didn't follow the provided > instructions i.e. using "mvn eclipse:m2eclipse" to generate eclipse > projects, instead, I was using "Import > Maven > Existing Maven projects", > this will also import the top level POM for me > > 2. Use "Run As > Maven install" on top level project to build all > > 3. Create another "Maven build" debug configuration and specify "run" > as Profiles, then click "Debug", then I suppose shindig is running in Jetty > and being debuggable. > > 4. Set a breakpoint in > "org.apache.shindig.gadgets.servlet.GadgetRenderingServlet.render" > > 5. Open > http://localhost:8080/gadgets/ifr?url=http://osda.appspot.com/gadget/osda-0. > 8.xml > <http://localhost:8080/gadgets/ifr?url=http://osda.appspot.com/gadget/osda-0 > .8.xml&view=canvas> &view=canvas in browser > > 6. However it didn't behavior as expected to stop at my breakpoint, > instead, eclipse popped me a dialog complaining that it can not find > line-number info in the class. But as I checked > in<shindig>\target\work\webapp\WEB-INF\lib\shindig-gadgets-2.0.0.jar:org/apa > che/shindig/gadgets/servlet/GadgetRenderingServlet.class, the line-number > info is present. > > 7. My workaround is to add my workspace into source-lookup, then > eclipse can locate correct source file for the debugging class, I can do > stepping in source code and inspect variables as well. > > 8. However the problem is the source file eclipse opened for me is not > really "in" my workspace, namely it's just opened as a plain java file, I > cannot find declaration/references etc. in the source file, and when I hover > the cursor on a variable I cannot get its context as well. > > Anybody have a better solution to debug shindig in Eclipse? Thanks! > > > > Regards, > > Rocks > > -- Paul Lindner -- [email protected] -- linkedin.com/in/plindner
