lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandre Rafalovitch <arafa...@gmail.com>
Subject Re: Where is a canonical SolrJ example(s)?
Date Wed, 29 Jan 2014 13:50:10 GMT
And then go back and also add servlets jar from examples/lib. And
maybe everything from dist/solrj-lib just because they are there, even
if they are duplicates to some (all?) of the above mentioned
libraries.

That's my point. A newbie would not know this. If there a script that
has all that on the classpath, they will copy that and go on. But ask
them to figure it out is a bit much.

Again, I am not saying it is impossible, just that we are making it
hard. And I am happy to help out with making it easier. I just don't
know what the right thing to do actually is here (e.g. with ESS).

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 8:41 PM, Michael Sokolov
<msokolov@safaribooksonline.com> wrote:
> If I were starting from a solr distribution (ie not maven), I would extract
> everything from the solr.war in WEB-INF/lib and WEB-INF/classes, and put
> that on my classpath.
>
> -Mike
>
>
> On 01/28/2014 06:29 PM, Alexandre Rafalovitch wrote:
>>
>> 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
>> <msokolov@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
>
>

Mime
View raw message