1

I started out by trying to run ant on a java program in a RH terminal.

BUILD FAILED
/home/phuong3/soar/soarRepos2/soar/tools/trunk/build.xml:187: Compiler Adapter 'javac1.6' can't be found.

Total time: 0 seconds

I was told that this problem would be fixed if I updated ant from 1.6.5 to 1.7.1. 1.7.1 already exists on the system at /opt/apache-ant-1.7.1/bin. So I changed ANT_HOME to this directory, and appended it to PATH. Now the state is:

[**** trunk]$ echo $ANT_HOME
/opt/apache-ant-1.7.1/bin
[**** trunk]$ ant -version
Apache Ant version 1.6.5 compiled on August 30 2006

So I'm presumably missing a very fundamental step. Can you tell me what it is?

EDIT: Bump. I really could use a hint on this. Is there more information I can provide? Basically what I need to know is, once I already have the Ant 1.7.1 binaries in the system, and ANT_HOME set to this directory, what else do I have to do to make 1.7.1 be the version that's used?

fixer1234
  • 28,064
Frank Harris
  • 55

2 Answers2

1

Solved it myself. Explanation to the best of my ability: Since when I typed in ant, the OS iterated through PATH until it found a directory which contained an executable called ant, the first one it found was going to be the right one. The one I wanted it to execute was LAST in the path. So in bash_profile, instead of export PATH=$PATH:/opt/apache-ant-1.7.1/bin, I did export PATH=/opt/apache-ant-1.7.1/bin:$PATH. Now, the desired version of ant shows up first and is the one executed.

Frank Harris
  • 55
0

I've just encountered the same symptoms, but with a different cause.

At some point in the past I must have placed a copy of ant-1.6.5.jar in ~/.ant/lib. This means ant always tried to use that jar. Solution was to remove the jar from ~/.ant/lib.

Steve Bosman
  • 142