0 Nick Edgar (6.5k●7●11) | answered Jan 05 '11, 9:58 a.m. JAZZ DEVELOPER Hi Baris, This looks OK to me. It should work. The workItemPublisher task does accept an inputFileType attribute, and the "WORKITEM" value is valid. Not sure why it's saying otherwise. Could you try running Ant using the JDK included with the RTC eclipse client? This can be set in the 'Java home' field in the Ant page of the build definition. Alternatively (and assuming you're using JBE), run JBE using that JDK. JBE's invocation of Ant uses the same JDK by default. See https://jazz.net/wiki/bin/view/Main/BuildFAQ#WhichJDK

 0 Nick Edgar (6.5k●7●11) | answered Jan 05 '11, 9:59 a.m. JAZZ DEVELOPER You could also try adding verbose="true", to see if it gives more details (e.g. a stack trace) in the build log.

 0 Baris Erdemir (181●28●19) | answered Jan 05 '11, 10:58 a.m. Hi Nick, thanks for the answer, I do not have ant page in my build definition. I am triggering a command line build. then i am calling a bat file which is invoking maven goals, inside maven goals, I am calling ant task. Why do you think linkPublisher and workItemPublisher will differ in terms of the JDK they are using? linkPublisher, artifactlinkpublisher and buildresultpublisher are runing successfully at the same environment. Could you try running Ant using the JDK included with the RTC eclipse client? This can be set in the 'Java home' field in the Ant page of the build definition.

 0 Nick Edgar (6.5k●7●11) | answered Jan 05 '11, 11:22 a.m. JAZZ DEVELOPER > Why do you think linkPublisher and workItemPublisher will differ in terms of the JDK they are using? It's a long shot, but we've seen various phantom bugs occur when using older JDKs, e.g. due to JIT bugs, leaks in the IO libraries, etc. So running with the JDK we ship with is usually my first recommendation, to reduce the variables involved. Note that we also have a Maven build definition, which might simplify the setup (but wouldn't help with the problem at hand).