When following reference documentation in paragraph "Running the TCK against CDI RI and JBoss AS",
there are following incompatibilities which leads to running TCK failure:

1/ TCK cannot be run against JBoss 5.1.x but nighly snapshot of 5.2.x must be used (required Bean Validation support)

2/ It is unclear whether directory should be changed to "weld" directory included within TCK [A] or to "weld" in meaning directory of RI [B]

• [A] if user does so, running "ant update" in jboss-as subdir leads to

[kpiwko@kapy jboss-as]$ ant update
Buildfile: build.xml
[typedef] Could not load definitions from resource org/apache/maven/artifact/ant/antlib.xml. It could not be found.
[echo] /tmp

install-weld.deployer:
[echo] Installing Weld 1.0.0-CR1 to /home/kpiwko/deploy/jboss-5.1.0.GA
[delete] Deleting directory /home/kpiwko/deploy/jboss-5.1.0.GA/server/default/deployers/weld.deployer

BUILD FAILED
/home/kpiwko/devel/weld/jsr299-tck-1.0.0-CR1/weld/jboss-as/build.xml:28: Problem: failed to create task or type urn:maven-artifact-ant:dependencies
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.

Total time: 0 seconds

• [B] if user does so, "ant update" target passes, but there's no "jboss-tck-runner" directory in there

3/ it is stated that user should change "jboss.dir" property in "local.build.properties", but there's only local "build.properties" file