For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 2 replies, 3 voices, and was last updated 14 years, 8 months ago by
.
-
Posts
-
Hi there,
I’ve just started evaluating MyEclipse Blue 6.5, and have got our existing project code out from CVS into MyEclipse no problem.
The project has an ant build.xml file which calls multiple other build.xml files, and was designed with the Rational RAD 6 tool in mind. In moving across to MyEclipse I am finding that the ant tasks eclipse.refreshLocal (to keep Eclipse in sync with stuff the build is doing) and projectBuild (to build) aren’t supported and I get:
BUILD FAILED
C:\Temp\myEclipse\Import\middleware\common\MiddlewareCommon\build.xml:45: The following error occurred while executing this line:
C:\Temp\myEclipse\Import\middleware\common\MiddlewareBuild\build.BuildCommon.xml:122: Problem: failed to create task or type eclipse.refreshLocal
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.I am wondering if these tasks are specific to the IBM RAD tool and not generic to ant as shipped with Eclipse, have never used Eclipse before, so am finding things out as I go. As an experiment I tried adding a task for projectBuild to ant in MyEclipse but gave up as I was having to add more and more jar files from the RAD version of Eclipse to make it work, so figured I either need to not use these tasks in the build.xml files and do it some other way, or find out if I have just missed how to do this in MyEclipse somewhere.
Have searched Google and the forums here to no avail.
Simon.
Simon,
I’m not familiar enough with the Ant extensions out there to know if those are specific to RAD or not, but I do know if you go to Window > Prefs > General > Workspace, and check the “Refresh automatically” checkbox, you don’t need any such tasks in the Ant script. That will implicitly refresh and fire build/validation cycles on any newly discovered files… so I think you can nix both those tasks.
