I saw a weird error related to the xerces, I think it was a class version problem. I'll try it again though to make sure.
On Wed, Jun 3, 2009 at 5:58 AM, Shai Erera <ser...@gmail.com> wrote: > Then perhaps as part of 1595 I can change it to use Java's XML parser, and > test the Enwiki file. If all goes well, we may not need the XERCES jar in > benchmark? Anyway, I'll check that too > > > On Wed, Jun 3, 2009 at 1:59 PM, Michael McCandless < > luc...@mikemccandless.com> wrote: > >> I also don't know why it's specifically using Xerces... >> >> Mike >> >> On Wed, Jun 3, 2009 at 4:26 AM, Shai Erera <ser...@gmail.com> wrote: >> > Grant, note that I'm changing the DocMakers in LUCENE-1595 including >> this >> > one. So whatever the decision is following your question, I can do it as >> > part of this issue, since that code will no longer be in EnwikiDocMaker. >> > >> > Regarding to your question, I don't know why it should depend on Xerces >> > (rather than the default Java XML parser I assume?) >> > >> > Shai >> > >> > On Wed, Jun 3, 2009 at 2:48 AM, Grant Ingersoll <gsing...@apache.org> >> wrote: >> >> >> >> Is there a reason the EnwikiDocMaker assumes Xerces for the SAX parser? >> >> Line 96. >> >> >> >> Thanks, >> >> Grant >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >
