Personally I do not set ANT_HOME at all. I simply make sure the bin directory is in my PATH and all is well.

        Erik


Noel J. Bergman wrote:
Peter,

The ANT developers probably all set ANT_HOME, or have ant installed in
/opt/ant, or some such.

I think that some of the lurkers here work on ANT, but I'll cross-post the
fix to their list.

        --- Noel

-----Original Message-----
From: Peter M. Goldstein [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 26, 2002 18:59
To: 'James Developers List'
Subject: RE: cvs commit: jakarta-james build.sh

Noel,


The ant script is broken with respect to locating ANT_HOME as a
relative entity.  They restore the path AFTER they try to cd with a
relative path, instead of before, so they are in the wrong directory
when they issue the cd.  This is demonstrable with a couple of embedded
echo statements


[clip]

I will update the Ant file.  I checked the CVS repository and the head
version of the file has the same problem.  You might want to notify the
Ant developers.

---------------------------

Index: tools/bin/ant
===================================================================
RCS file: /home/cvspublic/jakarta-james/tools/bin/ant,v
retrieving revision 1.3
diff -u -r1.3 ant
--- tools/bin/ant       26 Sep 2002 22:05:11 -0000      1.3
+++ tools/bin/ant       26 Sep 2002 22:42:18 -0000
@@ -63,10 +63,11 @@

   ANT_HOME=`dirname "$PRG"`/..

+  # need to restore position BEFORE we can cd with a ".."
+  cd $saveddir
+
   # make it fully qualified
   ANT_HOME=`cd "$ANT_HOME" && pwd`
-
-  cd $saveddir
 fi

 # set ANT_LIB location


-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>






-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to