Return-Path: Delivered-To: apmail-jakarta-alexandria-dev-archive@apache.org Received: (qmail 60233 invoked from network); 13 Jul 2002 17:59:29 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Jul 2002 17:59:29 -0000 Received: (qmail 28132 invoked by uid 97); 13 Jul 2002 17:59:45 -0000 Delivered-To: qmlist-jakarta-archive-alexandria-dev@jakarta.apache.org Received: (qmail 27992 invoked by uid 97); 13 Jul 2002 17:59:43 -0000 Mailing-List: contact alexandria-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Alexandria Developers List" Reply-To: "Alexandria Developers List" Delivered-To: mailing list alexandria-dev@jakarta.apache.org Received: (qmail 27965 invoked by uid 98); 13 Jul 2002 17:59:42 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D306A15.80204@apache.org> Date: Sat, 13 Jul 2002 13:57:41 -0400 From: Sam Ruby User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: James Strachan CC: turbine-maven-dev@jakarta.apache.org, alexandria-dev@jakarta.apache.org Subject: [Fwd: Re: [GUMP] Build failure - Jaxen] X-Enigmail-Version: 0.62.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ping? I have re-extracted revision 1.38 of build.xml, and found that it still worked. Is there any way that either this version could be restored or that maven itself could be enhanced to produce the necessary functionallity? Note: I did have to make a code change in order to get a successful compile. I've included the patch below. - Sam Ruby Index: src/java/main/org/jaxen/XPathFunctionContext.java =================================================================== RCS file: /cvsroot/jaxen/jaxen/src/java/main/org/jaxen/XPathFunctionContext.java,v retrieving revision 1.16 diff -u -r1.16 XPathFunctionContext.java --- src/java/main/org/jaxen/XPathFunctionContext.java 3 Jun 2002 15:11:51 -0000 1.16 +++ src/java/main/org/jaxen/XPathFunctionContext.java 13 Jul 2002 17:55:31 -0000 @@ -63,7 +63,7 @@ package org.jaxen; import org.jaxen.function.*; -import org.jaxen.function.DocumentFunction; +import org.jaxen.function.xslt.DocumentFunction; import org.jaxen.function.ext.*; import org.jaxen.function.xslt.*; -------- Original Message -------- Subject: Re: [GUMP] Build failure - Jaxen Date: Wed, 10 Jul 2002 09:08:48 -0400 From: Sam Ruby To: James Strachan CC: rubys@apache.org References: <20020709122704.82996.qmail@apache.org> <1a5101c22801$fa435430$9865fea9@spiritsoft.com> James Strachan wrote: >The power of blogging ;-). I spotted your note on your weblog and have >auto-generated an Ant build.xml file for Jaxen which should work perfectly >well in vanilla Ant. So from a CVS checkout of Jaxen you should just be able >to run Ant and it should work... > > Unfortunately, we lost something in the process that was important to me. The purpose of Gump is to see if the process can be bootstrapped. I had worked with you previously to make DOM4J an optional dependency as DOM4J depends on JAXEN... It looks like electricXML is now a required dependency too. It still seems to me that when you have a complex set of interdepencies like these projects have, the value of early warnings of breaking changes is extremely valuable. If you agree, help me find a way to bootstrap this process. If you feel this is not important, then I will simply remove JAXEN from the set of projects that Gump builds. Thoughts? - Sam Ruby -- To unsubscribe, e-mail: For additional commands, e-mail: