Example tck-dist bundle build

[starksm64]

Here is an example module that can be run after the TCK has been staged to create a dist bundle usable for the EE10 release. I have also added a signature map file and signature-generation profile to create it as I did not see this discussed in the TCK user guide. How to run the signature tests against the OpenLiberty compatible implementation still needs to be added to the CK user guide.

[njr-11]

Does this need the current year, 2022, as well?

[njr-11]

How to run the signature tests against the OpenLiberty compatible implementation still needs to be added to the CK user guide.

The TCK was using a different approach where it runs signature tests as part of all of the other tests, which is how they were running in Open Liberty, and in that case didn't need any additional instructions. I can see in this pull that you're getting us back to a more standard approach to the signature tests which will require adding the instructions as you point out and deleting the duplication, all of which can be a separate pull.

[KyleAure]

I really like the use of the sigtest-maven-plugin for generating the signature file to be used for testing.
But, instead of requiring those who run this TCK to configure this plugin for executing the verification.
I suggest we use the generated signature file and modify the SignatureTest package to use the plugin methods to do the verification on an application deployed to the server. That way the TCK user doesn't need to perform an extra setup just to run the signature tests.

[njr-11]

I really like the use of the sigtest-maven-plugin for generating the signature file to be used for testing.
But, instead of requiring those who run this TCK to configure this plugin for executing the verification.
I suggest we use the generated signature file and modify the SignatureTest package to use the plugin methods to do the verification on an application deployed to the server. That way the TCK user doesn't need to perform an extra setup just to run the signature tests.

I like that approach. I would be in favor of opening a separate issue to get that done for the TCK in this same release and then be able to merge this pull to make other progress.