On 1/25/06, Yoav Shapira <[EMAIL PROTECTED]> wrote: > Hi, > > > It doesn't even have an ant build file anymore. > > That'd be good to have, and I'm willing to help write it.
Great! I'm an ant novice (I'm much better at make), so we would probably get better results if someone else started it off. I was just going to copy the one from nutch and hack it until it worked. > +1 to solr rather than Solar, for consistency. I think I got all those cases now. > > Servlet: > > - Right now it must be ROOT (just due to URLs in the admin page I think). > > I assume people will want this changed (should be /solr I guess) > > Should be relative URLs so it works with any context path. But not urgent. That was my assumption, and I had tried it but it didn't work. Must have been my mistake somewhere. > Reliance on the operating system's current working directory is > dangerous. It can be used as a default perhaps, but solr should > provide a mechanism to indicate where the index directory should be. Definitely should be configurable. I do want some solution so that people can get started quickly though... just copy a generic solr.war into webapps, copy over a config directory, then start the appserver. So using cwd as a default would allow people to get up and running w/o configuration. Is there an easier/better way? When you do want to specify where config is, and where the index directory should be, what's the best way to do this? Is there any other good way rather than adding to web.xml as a context or servlet param? > > - We had a web.external.xml file that was included via an XML entity > > into the solr web.xml to allow changes and extensions w/o having > > to edit the solr one. This may have to go. > > It's not necessarily a bad thing, and should work more or less > universally Hmmm, OK. Must have been my mistake. Does the external file have to be in the webapp? What we had done with Resin was access outside it (../../conf/solar/web.external.xml). -Yonik
