Thanks Mike, Sounds like Maven approach worked, I haven't tried that. But without Maven, it is much harder. Like I said (in the second email of the thread) the relevant jars are all over the distribution including some inside the .war file. And the only way to figure it out is to run the client over and over again and keep adding jars until exceptions go away. And huntings jars is fairly complicated for a beginner.
Perhaps the instruction should just say, use Maven and stop at that. I can live with that, especially if we do that as a bundled example, so non-Maven people don't have to figure the way to build those poms themselves. Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Wed, Jan 29, 2014 at 5:35 AM, Michael Sokolov <msoko...@safaribooksonline.com> wrote: > > On 01/28/2014 11:55 AM, Alexandre Rafalovitch wrote: >> >> As to ESS, like I mentioned, the classpath issue seem to be quite a >> challenge. Again, perhaps not something that shows up during the >> testing because the directory layout during testing is rather >> different from the end-user's layout. >> > I'm not sure what "the classpath issue" is? We use ESS in our tests; it's > very nice not to have spin up a separate process in order to run unit tests > that require solr. To do this, we include the solr and solrj maven > artifacts as dependencies, and everything works. No classpath issues. I > wouldn't say the classpath is "minimal" -- I am sure there are classes, even > whole jars, that we could strip out, but is that really a major concern? > > -Mike
