| Debugging an Ant task with Eclipse 3.4 [message #326317] |
Fri, 14 March 2008 14:58 |
 Laszlo Benedek
Messages: 25
Registered: July 2009 |
Junior Member |
|
|
Hi All,
To debug an Ant task in Eclipse 3.2, I had the following setup:
The plugin.xml defined the Task
<antTask
library="%ANT_LIBRARY"
name="%ANT_TASK_NAME"
uri="%ANT_TASK_NAMESPACE"
class="my.ant.tasks.MyTask">
</antTask>
The plugin.properties file defined the keys. The libary was set to point
to the location of the jar:
ANT_LIBRARY = runtime/myplugin-ant.jar
To debug the application it was sufficient to change the library
location and point to the bin folder:
ANT_LIBRARY = /bin-ant
The location of the /bin-ant folder showed up in classpath if running
the task in the same JRE as the Workspace. Any changes made to the task
were available without restarting the runtime workspace.
In Eclipse 3.4 the above setup doesn't work anymore. Although the
location of the /bin-ant folder still shows up in the classpath, the
task is not found. It works if I create the jar (myplugin-ant.jar).
But this setup is very time consuming. Every time I make a change in the
task I have to close the runtime workspace, delete and recreate the jar
(myplugin-ant.jar) and restart the runtime workspace.
There must be a simpler process of debugging a task.
Anyone knows it ?
|
|
|
Powered by
FUDForum. Page generated in 0.02644 seconds
] 
Search
Help
Register
Login
Home
