Figures... Once I wrote it down and sent my problem off, I manage to find the solution! I was digging through ANT docs and found a note that it needed a JAXP compliant parser. I realised that the standard installation of ANT included one, but I didn't need that one at all. It took a little work, but I managed to get both ANT and alexandria happy so they could both work. --Colin > -----Original Message----- > From: Colin Peart [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 31, 2001 2:21 PM > To: [EMAIL PROTECTED] > Subject: help! xerces version conflicts between ANT and Alexandria > > > I am having some trouble using Alexandria in an odd situation. > I can't find any way to solve it, so I was hoping someone > here might have a moment to think about it. > (for future reference, is there a archive of this list?) > > At any rate, here goes: > > We use an ant based system to check out and compile a large > number of sub > projects. After learning my way around Alexandria and > adjusting it to meet > my needs, I am trying to make Alexandria work with our build system. > > In our system, you manually check out a "Master Build" system > which contains > an ant build.xml, and a commonbuild.xml (which each of the subprojects > includes -- it provides common functionality). > > Then the master build system is used to checkout the > subproject and build > them. > > For my Alexandria set-up, I had figured out a way to get the > javadocs to be > fully crossed linked between Alexandria projects and external > sources such > as the java.sun.com copy of the API javadocs. Consequently, > for maximum > effect, I need to include a large number of jars (one from each of my > subprojects) so that javadoc can produce the proper > cross-linking. Hence, > instead of using <ant buildfile="..."> for my version of the > Alexandria > project, I had to use > > <java classname="org.apache.tools.ant.Main" ...> > <classpath>...</classpath> > <arg line="-buildfile Alexandria.xml"> > </java> > (with all the needed parameters and classes, that I omitted > for brevity) > > to launch the Alexandria process. > > Problem is that ant 1.3 uses Xerces 1.3.1 and Alexandria uses Xerces > 1.0.3... > > If I remove the 1.3.1 version from the class path, ant > complains it can't > find a parser. > If I remove the 1.0.3 version, Alexandria complains it can't find > org.apache.xerces.validators.XSchemaValidator > > (both show up as NoClassDefFoundException's). > > I have tried rearranging the order of the class path, etc. > but no luck. > It strikes me that this is a problem that might have shown up > for other > developers, so I thought maybe somebody already knew a work around. I > figure worst case scenario, I am told to bug off (which I > will politely do, > of course ;)) but perhaps there is a solution? > > --Thanks, > Colin Peart > Application Developer > Rogers iMedia > > > --------------------------------------------------------------------- > 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]
