| FAQ: Frequently Asked Questions |
|
| |
| 1. What is AntView AntView is an Eclipse plugin
to parse Ant Build files in Eclipse project directories. The plugin will
display Ant targets and allow execution of targets from the view.
|
| 2. What release works with which version of Eclipse AntView 2.x supports Eclipse R2.0
AntView 1.x supports Eclipse R1.0 and WebSphere Application Developer 4.X
(WAD)
|
| 3. I get a 'Classic Compiler' error when running Ant or What/How do I
set the build.compiler The Ant property 'eclipse.running' is set to 'true'
when an Ant target is executed from within Eclipse. Use the following target
in your Ant build file and include it as a dependency.
<target name="properties" if="eclipse.running">
<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/>
</target>
|
| 4. When running a javadoc target I get an execution error
- CreateProcess. This is one issue with javadoc from Eclipse/AntView
and I'm not sure it's the only one. A solution reported to eclipse.org
is to add the directory location of the javadoc executable (e.g. <jdk
dir>/bin) to your PATH environment variable.
|
| 5. How come I get a stack trace when I cancel
an Ant build from the progress dialog. Unfortunately, there is not a
lot I can do about it. There is some debugging code left in an internal
Eclipse Ant Core class that prints the stack trace. It looks like this was
removed in the MAIN branch around July 16, 2002, but this was after the
release date. Also, it looks like the code is back in on R2_0_1 branch.
Sigh.
|