Yeah, it's usually pretty daunting to know where to start, the codebase is kinda big. Even "start from junit test" is often daunting, there are a lot of them too.
Others have given you good places to start, good luck! Erick On Fri, Sep 19, 2014 at 12:23 AM, Bernd Fehling <bernd.fehl...@uni-bielefeld.de> wrote: > Just start at the UpdateHandler and follow it down the line. > > I would start at org/apache/solr/update/UpdateHandler.java > > If you already know if it is add, delete or update then start with > AddUpdateCommand.java, DeleteUpdateCommand.java or UpdateCommand.java. > > Just follow the red line :-) > > Regards > Bernd > > > Am 19.09.2014 um 08:47 schrieb Anurag Sharma: >> Thanks Bernd for your insight. >> As of now, I am focussing to fix the issue in the updater but not able to >> localize which code to look in for it. >> >> Regards, >> Anurag >> >> On Fri, Sep 19, 2014 at 12:09 PM, Bernd Fehling < >> bernd.fehl...@uni-bielefeld.de> wrote: >> >>> It depends on what you are going to do. >>> >>> If you are adding/modifying code and Junit tests use Junit test cases. >>> If you are debugging runtime problems under load use remote debugging. >>> If you are going for in deep debugging (even into Jetty and Java) use >>> RunJettyRun for Eclipse. >>> >>> Regards >>> Bernd >>> >>> >>> Am 18.09.2014 um 20:50 schrieb Anurag Sharma: >>>> Dear Solr users, >>>> >>>> I am new to Solr dev community and trying to setup eclipse to debug a >>>> running solr server. Please suggest if anyone of you have tried doing the >>>> same. >>>> >>>> Once above is done. Also suggest the entry point in code where breakpoint >>>> can be placed. >>>> >>>> Thanks >>>> Anurag >>>> >>> >>> >>
