This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a commit to branch jakartaee9-tck
in repository https://gitbox.apache.org/repos/asf/tomee-tck.git
The following commit(s) were added to refs/heads/jakartaee9-tck by this push:
new c73b5b3 Updates README.md to point to David's git approach to restore
a fresh TCK installation
c73b5b3 is described below
commit c73b5b36c44bfec28925f40622e0a4581a2beb5f
Author: Richard Zowalla <[email protected]>
AuthorDate: Tue Apr 26 11:39:56 2022 +0200
Updates README.md to point to David's git approach to restore a fresh TCK
installation
---
README.adoc | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/README.adoc b/README.adoc
index 06d61a1..b25a445 100644
--- a/README.adoc
+++ b/README.adoc
@@ -30,6 +30,22 @@ Ensure, that you have a `profile` in your maven settings.xml
like
You can copy & paste from `settings.xml.template`. Ensure, that the
directories exist. Then just run `./setup-tck91.sh`.
It will conduct the initial TCK setup.
+==== Getting a fresh TCK install after modifications
+
+A critical thing to be aware of is that
+
+- 1.) Running the TCK will in fact modify your install in a handful of ways
+- 2.) Some of these processes happen exactly once and will not repeat unless
you unpack a completely fresh TCK install.
+
+Just go to the location of the unzipped TCK and run
+
+ git init
+ git add *
+ git commit -m "initial"
+
+With that you can do a `git clean -fd` / `git reset --hard HEAD` at any time
to restore the TCK install to a fresh state.
+You can also do a `git status` and `git diff` to see exactly what has been
modified.
+
=== Semi Automated Way of Building the TCK from Source
This is interesting, if you need to modify TCK source. To build from source,
following these steps:
