Howdy,
> > > 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. I've just committed a starting version with the basic functionality. There are still some cleanup items needed: - lucene_extras should be named to something clearer, and the one Test class in it that depends on JUnit should be moved to the test subfolder - The XPP jar in the lib directory has an O (the letter oh) where a 0 (the digit zero) would make more sense in its name. Is the letter intentional? I wasn't sure, so I didn't want to change it. - I added a top-level license file as required by all ASF projects, but we probably need a NOTICE.txt file as well covering the XPP license, if we keep using XPP. > That was my assumption, and I had tried it but it didn't work. Must > have been my mistake somewhere. It may be in the servlet code, I'll take a look when I get a chance. > 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? Perhaps using the java.io.tmpdir system property or the servlet container's javax.servlet.context.tempdir context attribute. > 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? Putting them on the classpath using a classloader reference to look them up, or using a simple configuration file that's not tied to the servlet container. The web.xml approach is fine but it has at least one serious drawback in that it makes out-of-container testing much more difficult. > 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). I don't think so, but the user account running the server must have read permissions on the directory. -- Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com
