I've put a patch on bugzilla that fixes this issue for xindice. Quoting Vadim Gritsenko <[EMAIL PROTECTED]>:
> Hi All, > > It seems that Xalan XPath API has been changed [1] some time ago, this change > > was not backward compatible, and old method was not deprecated but removed > completely. This can be seen in Gump messages [2] (snippet below). > > Would it be possible to re-instate old API, you can make it deprecated, but > please provide smooth migration path for the downstream projects? > > Xindice depends on old API, and without deprecation messages it's not > possible > to see what is the proper migration path. > > Thanks, > Vadim > > [1] > http://cvs.apache.org/viewcvs.cgi/xml-xalan/java/src/org/apache/xpath/compiler/Compiler.java?r1=1.37&r2=1.38&diff_format=h > [2] http://marc.theaimsgroup.com/?t=109761492700003&r=1 > > > -------- Original Message -------- > Subject: [EMAIL PROTECTED]: Project xml-xindice (in module xml-xindice) failed > Date: Mon, 21 Feb 2005 02:17:47 PST > From: Sam Ruby <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > > To whom it may engage... > > [javac] > /home/gump/workspaces2/public/workspace/xml-xindice/java/src/org/apache/xindice/core/query/XPathQueryResolver.java:163: > > cannot resolve symbol > [javac] symbol : constructor Compiler > (org.apache.xml.utils.DefaultErrorHandler,<nulltype>) > [javac] location: class org.apache.xpath.compiler.Compiler > [javac] cmp = new Compiler(errorListener, null); > [javac] ^ > [javac] 1 error >
