Running unit tests is easy, once you set the right 'current directory' so that unit tests can find their resource files. I have found that if I get a full set of unit tests for something, I don't have to debug it in the full app.
Running the whole thing as a servlet has the whole servlet engine setup thing, which I avoid. Running as EmbeddedSolr might be easy, I haven't tried it. I usually make a separate empty Java project and import source and libs as needed. I do a lot of 'search everything for this string' so having the whole source tree in the project just slows me down. This does remove the ability to use the svn/git management, but I don't mind that. On Sat, Aug 21, 2010 at 5:27 AM, stockii <st...@shopgate.com> wrote: > > Hello.. > > Can anyone give me some tipps to debug the solr-code in Eclipse ? or do i > need apache-Ant to do this ? > > thhx =) > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-Debug-Sol-Code-in-Eclipse-tp1262050p1262050.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Lance Norskog goks...@gmail.com
