Eclipse update site doesn't build correctly from a top-level build

When building the Eclipse update site as part of a top-level build, a number of files in the update site are incorrect because resource filtering isn't applied correctly. This causes the substitution variable ${tuscany.eclipse.version} to appear as a literal string in various xml files, manifest files and jar names instead of being replaced by a correct value such as 1.6.2.v20110405-1631.

If the Eclipse update site is built from the tools/eclipse directory, everything works correctly.