This page describes the reasons you can get a successful build result in Rational Team Concert when the corresponding Rational Application Developer build failed, or why a workspace that builds correctly in Rational Application Developer might fail using Ant builds run by the Jazz Build Engine.
[javac] C:\Program Files (x86)\IBM\TeamConcert\buildsystem\buildengine\eclipse\fetched\ClassName.java:xx: cannot find symbol [javac] symbol : method required() [javac] location: @interface javax.xml.bind.annotation.XmlElementRef [javac] @XmlElementRef(name = "name", type = JAXBElement.class, required= false)
<javac>or the following task (from Rational Application Developer)?
<workspaceBuild>
If you are having errors because classes, types, symbols cannot be resolved, it is likely an issue with the classpath you need to supply to
<javac>Such issues can be avoided altogether by using the Rational Application Developer specific task:
<workspaceBuild>This task does not require any classpath setup (because it reads that information from the project metadata).
If you are using the Rational Application Developer tasks for building in a command line Rational Team Concert build definition, any errors reported inside the script are not automatically propagated to the Rational Team Concert build results. Logic inside your script will need to perform such error propagation. You will need to use Jazz build Ant tasks to communicate to the Rational Team Concert build results specific error messages generated by Rational Application Developer Ant tasks. This requires that you execute the build inside a shell-sharing installation of Rational Application Developer and the Rational Team Concert Client for Eclipse (Extension install).
The following two technotes show (with an example) how to solve both types of problems:
Status icon key: