Using the IBM defined any tasks keeps giving an error with the Build no matter what I have tried
In my any script, I have added the line:
<import file="C:\IBM\TeamConcert603\jazz\buildsystem\buildtoolkit\BuildToolkitTaskDefs.xml" />
When I run the build definition, the build keeps failing with the error:
C:\IBM\TeamConcert603\jazz\buildsystem\buildtoolkit\BuildToolkitTaskDefs.xml:24 : taskdef A class needed by class com.ibm.team.build.ant.task.ActivityFilePublisherTask cannot be found: org/eclipse/core/runtime/IProgressMonitor using the classloader AntClassLoader[] ...
It continues with a big stack trace.
I have tried using a newer version of Ant, pointing to the lib items manually, deleting all other tasks I dont need in that file (after I copied it) and running that, and it still would run into the same issue. I am at a loss of what is causing the issue.
We do not use the default Eclipse from IBM, we use Eclipse 2018-12 with the IBM plugin.
|
One answer
Ralph Schoon (63.7k●3●36●48)
| answered Aug 01 '19, 2:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Aug 01 '19, 2:20 a.m. From https://jazz.net/help-dev/clm/topic/com.ibm.team.build.doc/topics/r_ant-tasks.html
I always shamelessly steal from the JKE Banking example and there the taskdefs are copied into the ant script (at the end).
I always use brute force search (also local) and found this in a build script:
<import file="${toolKitPath}\\BuildToolkitTaskDefs.xml"> </import>
Note the double backslash (I had to fake this in the post here using 4 backslash). No idea what OS you are using.
The Eclipse client you use is irrelevant, the build runs on a build system in an build engine and not in the client.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I forgot to mention we are using RTC 6.0.3
I believe that we are using that. All I know is we have RTC version 603 and I was given the files for the build system which I put on the machine where we run our builds.
I talked to our CLM Team we have, and they confirmed we are using the Build Engine version 603.