ant port Was: /usr/local/bin/javavmwrapper and "classpath"

Jan Grant Jan.Grant at bristol.ac.uk
Tue Aug 24 07:41:04 PDT 2004


On Tue, 24 Aug 2004, Jan Grant wrote:

> Agh! Why (oh why oh why) does "classpath" put "." at the start of its 
> output? Apart from the obvious, that is (so that the shell script is 
> simpler to produce).

Following up from my previous email (which came across as more grumpy 
than I intended, apologies), can I ask: is anyone using the apache-ant 
port in anger?

I've had extreme difficulties with it thus far. In particular, the 
script seems to rely on the existence of a CLASSPATH variable it never 
sets. Additionally, it doesn't select any of the *.jar files in 
/usr/local/ant/lib by default, which has the effect of turning off any 
of the optional ant tasks.

Am I doing something wrong? I've wound up including the following in my 
~/.antrc as a workaround:

[[
JAVA_HOME=/usr/local/jdk1.4.2 export JAVA_HOME

lcp=$(  \
        find -s /usr/local/ant/lib -name '*.jar' | while read jar ; do
                echo -n ":${jar}"
        done | sed -e 's/://' )

LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$lcp
]]

Which means if bsf.jar and js.jar are available in the usual place 
(/usr/local/share/java/whatever...) then the script tasks etc are again 
available... but I'd expect /usr/local/bin/ant to do this kind of thing 
on my behalf.

Yours in confusion,
jan

-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/
Just because I have nothing to hide doesn't mean I have nothing to fear.


More information about the freebsd-java mailing list