Initial update to remove the web integration tests from the core tck

[starksm64]

Fixes #529

[Ladicek]

The cdi.tck-4.0.version property is for Weld, right? At the moment, Weld uses cdi.tck-4-1.version (and I don't see a PR in https://github.com/weld/core to change it), so this change (here and elsewhere) is wrong.

[starksm64]

No, there is a separate weld.version for that. How this cdi.tck-4-0.version property was used was to allow one to select a different version of the TCK when running the sample test runner poms. Really this dates back to when one could do minor releases of the TCK without doing a full release, so I just dropped it as it is confusing as to what the purpose is and it just complicates the build and verifying it.

[manovotn]

I think Ladislav is right here. This command is taken from Weld to execute TCKs against certain TCK version and the property is defined in Weld here as cdi.tck-4-1.version

The reason it's so explicit is that in some point in time Weld had to run against two different TCK majors (around CDI 2/3 IIRC). That being said, I wouldn't mind changing it to cdi.tck.version if that's what you'd prefer.

[starksm64]

Ok, that is confusing. Let me look at exactly Weld uses it and how this fits into how the TCK is released now.

[starksm64]

I can't see why we would want to take the CDI TCK version used by the sample TCK runner from the weld-core-parent pom cdi.tck-4-1.version value. What is missing in the current changes is a default value for the cdi.tck.version and not using filtering on this property when the jboss-runner.pom is copied to the dist weld/jboss-tck-runner/pom.xml file so that one can override the CDI TCK version used. We can talk about it in today's call.

  <properties>
    <!-- This matches the htmlunit version in TCK -->
    <htmlunit.version>2.50.0</htmlunit.version>
    <cdi.tck.version>${project.version}</cdi.tck.version>
  </properties>