Return-Path: Mailing-List: contact general-help@xml.apache.org; run by ezmlm Delivered-To: mailing list general@xml.apache.org Received: (qmail 42143 invoked from network); 10 Aug 2000 17:54:46 -0000 Received: from mail3.iadfw.net (209.196.123.3) by locus.apache.org with SMTP; 10 Aug 2000 17:54:46 -0000 Received: from phoenix from [209.196.111.205] by mail3.iadfw.net (/\##/\ Smail3.1.30.16 #30.4) with smtp for sender: id ; Thu, 10 Aug 2000 12:55:14 -0500 (CDT) Message-ID: <019a01c002f4$c6bc9f60$0100a8c0@phoenix> From: "David Ramsey" To: Subject: Re: Nighly builds Date: Thu, 10 Aug 2000 12:59:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is a very common problem and one that makes using various Apache Java projects together problematical. I know that I, for one, spent too much time tracking down the jaxp.jar/xerces.jar/xml.jar org.w3c.node problem and that I am not the only one to have had to do so. This would go a long ways towards making setup and utilization of the various Apache Java projects much easier for people who want to *use* them rather than develop them. David Ramsey -----Original Message----- From: Sam Ruby To: general@xml.apache.org Date: Thursday, August 10, 2000 12:59 AM Subject: Re: Nighly builds >Mike Pogue wrote: >> >> I'd like to see a solution that works for our C++ projects, too. >> I don't think we want to require Java for those! > >While I would like to see that too, it is a matter of trying not to bite off >more than one can chew. I also believe that the classpath issues associated >with Java are unique and need a special focus. > >At the moment, there is a demonstrable problem with the Java projects in >that it seems rare that you can pick two Java projects and have them work >together out of the box. Typically, there is a mismatch in some dependency >or another. This problem is exacerbated by each project shipping their >dependencies. > >P.S. One of the most common complains it some method missing in >org.w3c.node, and no class in the classpath (based solely on its name) is >obviously associated with w3c... > > >--------------------------------------------------------------------- >In case of troubles, e-mail: webmaster@xml.apache.org >To unsubscribe, e-mail: general-unsubscribe@xml.apache.org >For additional commands, e-mail: general-help@xml.apache.org >