<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="${lib}/${lib.ant-contrib}"/>
</classpath>
</taskdef>

<if> and <var> are not recognized, and taskdef is underlined in red saying "failed to load type"

The problem also occurs for emma, and our custom tasks too.

All of this had been green before the upgrade, and all the location specified above for the pathelement does correctly point to the jar.

1. the taskdef for antcontrib above that references a property file.

2. taskdefs using a classpath ref.

<taskdef
description="Produces a properties file of business errors from an Excel spreadsheet."
name="errorCatalog"
classname="com.aspentech.imos.common.system.load.ErrorCatalog"
classpathref="error-catalog.classpath"/>

(where the path is defined in and imported from our build-classpath.xml like this
<fileset dir="${lib}" id="error-catalog.libs">
<include name="${lib.commons-lang}"/>
<include name="${lib.commons-logging}"/>
<include name="${lib.jtds}"/>
<include name="${lib.log4j}"/>
<include name="${lib.poi}"/>
</fileset>
<path id="error-catalog.classpath">
<fileset refid="error-catalog.libs"/>
<pathelement location="${lib.error-catalog}"/>
</path>

3. (unsuprisingly) the combination of the two also does not work

<!-- this loads <emma> and <emmajava> custom tasks: -->
<taskdef resource="emma_ant.properties" classpathref="emma.classpath"/>

4. included classpath almost works but all the attributes for the taks are red (this was a problem in 5.1 also)

<taskdef name="junit"
classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask">
<classpath id="junit.classpath">
<fileset refid="junit.libs"/>
</classpath>
</taskdef>

So whether it is one bug or several bugs, every aspect of taskdef is broken in at least some way and it is impossible to write any but this absolute simplest build files without a lot of red marks in the gutter, and useless complaints about errors when I checkin any set of files that includes a build file (unless I tell it not to perform code analysis for the effected files).

Given that nothing works a general bug about taskdef seems appropriate. I did not find bugs for the current release that described these cases individually (my search may have been faulty of course). If this should be split into separate bugs or duplicates existing bugs let me know I'll be happy to watch/file those instead. If you've fixed one or all of these cases then thank you!