jakarta-alexandria-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <ru...@apache.org>
Subject [Fwd: Re: [GUMP] Build failure - Jaxen]
Date Sat, 13 Jul 2002 17:57:41 GMT
  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 <rubys@intertwingly.net>
To: James Strachan <james_strachan@yahoo.co.uk>
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:   <mailto:alexandria-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:alexandria-dev-help@jakarta.apache.org>


Mime
View raw message