> : At start up of each container it said it can't find some solar.config files
> : and the they barfed.
> : Are people able to use solr today?
> : If so how?
> please take a look at the Tutorial and try out the example
> http://incubator.apache.org/solr/tutorial.html >
> ...Like many applications, Solr can't do anything without some basic
> configuration information.
On 10/29/06, netsql <[hidden email]> wrote:
> I take it that others can get it to work.
> I read the tutorial. (I did not see anything about solar config xml there).
> I did the post, that seemed to work.
> I then surfed to /admin and it gave me jsp errors on all 3 containers.
It is possible that you have a JRE installed instead of a JDK? Solr
requires the latter for the admin pages.
On 10/30/06, Otis Gospodnetic <[hidden email]> wrote:
> This is what I just stuck in my Solr SVN checkout, so I can build + deploy the app:
> This is not ideal though, as every time I make a change I need to run this, remove old files, build a war, deploy it, and wait a few seconds for Jetty to unpack it.
> How are people who are actively working on Solr doing this? Yonik, Hoss, Mike...? What's your setup like?
My setup is relatively primitive, since my Solr dev time is limited.
All of my changes have been developed using unit tests and the example
app. Make a change, 'ant -Dtestcase=... test' (with an occasional
'ant clean'). To test with the example, 'ant clean example', Ctrl-C
the open jetty process (in a terminal) and restart it (up-enter).
Our work usage of solr is a different beast altogether; I assume you
were talking mostly about developping Solr itself.
: My setup is relatively primitive, since my Solr dev time is limited.
: All of my changes have been developed using unit tests and the example
: app. Make a change, 'ant -Dtestcase=... test' (with an occasional
: 'ant clean'). To test with the example, 'ant clean example', Ctrl-C
: the open jetty process (in a terminal) and restart it (up-enter).
This is what i do as well when working on Solr internals. When working on
specific Solr applications at work, we have CNET specific RPMs containing
"blessed" Solr releases, and I just use those ... but we don't rev our
internal Solr RPMs very often