Test coverage files are generated in directory from which maven is run

When running maven target (install) from another directory than cdi-tck root, test coverage is generated in directory from which maven was fired.

This caused unexpected FileNotFound when artifacts are to be installed:

[trunk]$ mvn cdi-tck/pom.xml -Dtck-audit=true clean install

[INFO] Installing /home/kpiwko/devel/weld/trunk/cdi-tck/target/coverage-cdi.html to /home/kpiwko/.m2/repository/org/jboss/jsr299/tck/jsr299-tck-impl/1.0.0-SNAPSHOT/jsr299-tck-impl-1.0.0-SNAPSHOT-coverage-cdi.html
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error installing artifact: File /home/kpiwko/devel/weld/trunk/cdi-tck/target/coverage-cdi.html does not exist

Target directory is generated in trunk. This bug causes problems with automatized testing on Hudson.