Suggestion, another ant target that creates an example dir outside of the tree?
I was a little bit surprised by the following scenario: 1) svn co 2) ant example 3) edit schema.xml 4) svn st In the future, I'll run cp -r before I start messing with the example. I'm +1 for the work directory. I'd also like to understand how the classpaths are managed. How does solr/lib get into the classpath structure? Is it in the system classpath for jetty or the webapp class path for the solr webapp? On Fri, Mar 7, 2008 at 8:58 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > Jetty unpacks the war in a sub-dir of /tmp by default (which can get > cleaned by other things). > > https://issues.apache.org/jira/browse/SOLR-118 > > devs: any reason we shouldn't create example/work and make sure it > gets in the distributions? > > -Yonik > > On Fri, Mar 7, 2008 at 7:19 AM, Doug Steigerwald > <[EMAIL PROTECTED]> wrote: > > Came in this morning to find some alerts that the admin interface has > basically died. Everything > > was fine until about 4am. No updates or queries going on at that time > (this is a QA machine). > > Anyone know why it might die like this? > > > > Solr 1.3 trunk build from Jan 23rd, 4GB heap size, 4x3.2GHz Xeon, 8GB > RAM total, RHEL 5.1, 64bit. > > > > Mar 7, 2008 5:42:46 AM org.apache.solr.common.SolrException log > > SEVERE: org.apache.jasper.JasperException: PWC6117: File > "/admin/ping.jsp" not found > > at org.apache.jasper.compiler.DefaultErrorHandler.jspError( > DefaultErrorHandler.java:60) > > at org.apache.jasper.compiler.ErrorDispatcher.dispatch( > ErrorDispatcher.java:346) > > at org.apache.jasper.compiler.ErrorDispatcher.jspError( > ErrorDispatcher.java:140) > > at org.apache.jasper.compiler.JspUtil.getInputStream( > JspUtil.java:881) > > at org.apache.jasper.xmlparser.XMLEncodingDetector.getEncoding( > XMLEncodingDetector.java:114) > > at > > org.apache.jasper.compiler.ParserController.determineSyntaxAndEncoding( > ParserController.java:347) > > at org.apache.jasper.compiler.ParserController.doParse( > ParserController.java:181) > > at org.apache.jasper.compiler.ParserController.parse( > ParserController.java:111) > > at org.apache.jasper.compiler.Compiler.generateJava( > Compiler.java:169) > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java > :387) > > at org.apache.jasper.JspCompilationContext.compile( > JspCompilationContext.java:579) > > at org.apache.jasper.servlet.JspServletWrapper.service( > JspServletWrapper.java:344) > > at org.apache.jasper.servlet.JspServlet.serviceJspFile( > JspServlet.java:464) > > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java > :358) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > > > > This happened a few weeks ago, but someone just restarted Solr to get > the admin interface back. > > They said that updates and queries were still working fine. > > > > Thanks. > > Doug > > >
