Erick, I think i know the problem: see https://issues.apache.org/jira/browse/SOLR-2303
perhaps the issue is somehow not "fixed" though. feel free to re-open it and we can try to get to the bottom of it... But i suspect it has to do with log4j jars being in ant's classpath, and somewhere in solr's build it must be adding ant's classpath to the junit runtime classpath... i know i cleared this up for lucene but perhaps i missed a spot for solr. On Tue, Jan 18, 2011 at 7:50 AM, Erick Erickson <[email protected]> wrote: > Yep, already tried a fresh checkout before sending the e-mail. At first > glance this looks like a classpath issue hopefully just on my machine, > but it was late last night and I wanted to give someone a chance to pipe > up with "Ooops, I was changing that and.....". Yes, I'm lazy when I can > be. Er... Efficient that is. > Erick > > On Tue, Jan 18, 2011 at 12:19 AM, Yonik Seeley <[email protected]> > wrote: >> >> On Mon, Jan 17, 2011 at 10:42 PM, Erick Erickson >> <[email protected]> wrote: >> > Hmmmm, a fresh, unmodified checkout of Solr will fail on my Windows7 box >> > if >> > I run "ant -Dtestcase=VelocityResponseWriterTest test". It succeeds on >> > my >> > Mac. Anyone got a clue? Or should I look into it? Of course it succeeds >> > in >> > IntelliJ. Siiiigggghhhh >> >> My windows laptop took a vacation (a permanent one) so I can't verify. >> But when I see NoSuchMethod runtime exceptions, I usually try a fresh >> checkout first. It's sometimes just stuff not getting cleaned up >> properly. >> >> -Yonik >> http://www.lucidimagination.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
