As Jacques mentioned, your guess is right. Eclipse insists on using its
own copy of Ant - even when you try to change the preferences. I tried
creating my own project-specific Builder, but that didn't work either.
I tried, but I couldn't get it to work. Can I have a cookie anyway?
-Adrian
Adam Heath wrote:
Adrian Crum wrote:
Your commit doesn't fix the Eclipse issue. I have a fresh checkout and
I'm willing to help solve the problem.
Here are the ant jars listed in the classpath file, let me know what
order they should be in:
<classpathentry kind="lib"
path="framework/base/lib/ant/ant-nodeps-1.7.0.jar"/>
<classpathentry kind="lib"
path="framework/base/lib/ant/ant-apache-bsf-1.7.0.jar"/>
<classpathentry kind="lib"
path="framework/base/lib/ant-launcher-1.7.0.jar"/>
<classpathentry kind="lib" path="framework/base/lib/ant-1.7.0.jar"/>
My guess is that any ant jar in .classpath is not used at all; eclipse
itself has it's one ant jars that is uses to start the build process.
As a test, remove those 4 entries, and try a build. If it starts ant,
and fails in the exact same way, then it shows that it's not using our
own ant jars, but something else. It also means something else inside
eclipse needs to be fixed to make this work.
Backing out my change from a few days ago is not the right thing to do
here; this probably would eventually come up at some point, so we might
as well go about seeing what needs to be done to fix it.
