edit comments to remove tech versions from sig files

install/concurrency/bin/sig-test.map

@@ -29,9 +29,9 @@
 #
 # The resultant signature file name has a name that complies
 # with the following format:
-# <package>.sig_<technology_version>
+# <package>.sig
 # Given this format, the following example breaks down as follows:
-#    jakarta.enterprise.concurrent.sig_1.0:
+#    jakarta.enterprise.concurrent.sig:
 #      <package> = jakarta.enterprise.concurrent
 #      <technology_version> = 1.0  (for CONCURRENCY)
 #

install/jakartaee/bin/sig-test.map

@@ -26,7 +26,7 @@
 #
 # The resultant signature file name has a name that complies
 # with the following format:
-# <package>.sig_<technology_version>
+# <package>.sig
 # Given this format, the following example breaks down as follows:
 #    jakarta.servlet=4.0
 #      <package> = jakarta.servlet

install/jaxws/bin/sig-test.map

@@ -16,19 +16,17 @@
 
 ###############################################################
 #
-# IMPORTANT:  this sig-test.map file for use with JDK 8 only!
-#             Using this file with a non JDK 8 will yield errors.
 #
-# The signature test mapping file for the JAX-WS 2.2 TCK.  This file
+# The signature test mapping file for the JAX-WS TCK.  This file
 # should be formatted as a standard java properties file.  The
 # name is the package name and the value is the version of the
 # package that should be tested by the signature tests.
 #
 # The resultant signature file name has a name that complies
 # with the following format:
-# <package>.sig_<technology_version>
+# <package>.sig
 # Given this format, the following example breaks down as follows:
-#    jakarta.xml.jaxws.sig_2.2:
+#    jakarta.xml.jaxws.sig:
 #      <package> = jakarta.xml.ws
 #      <technology_version> = 2.2  (for JAX-WS) 
 #

install/jms/bin/sig-test.map

@@ -29,9 +29,9 @@
 #
 # The resultant signature file name has a name that complies
 # with the following format:
-# <package>.sig_<technology_version>
+# <package>.sig
 # Given this format, the following example breaks down as follows:
-#    jakarta.jms.sig_2.0:
+#    jakarta.jms.sig:
 #      <package> = jakarta.jms
 #      <technology_version> = 2.0  (for JMS) 
 ###############################################################

install/jsonb/bin/sig-test.map

@@ -30,9 +30,9 @@
 #
 # The resultant signature file name has a name that complies
 # with the following format:
-# <package>.sig_<technology_version>
+# <package>.sig
 # Given this format, the following example breaks down as follows:
-#    jakarta.json.bind.sig_1.0:
+#    jakarta.json.bind.sig:
 #      <package> = jakarta.json.bind
 #      <technology_version> = 1.1  (for JSON-B) 
 #

install/jsonp/bin/sig-test.map

@@ -14,25 +14,19 @@
 # SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
 #
 
-#
-# $Id$
-#
-
 ###############################################################
 #
-# IMPORTANT:  this sig-test.map file for use with JDK 8 only!
-#             Using this file with other version of JDK will yield errors.
 #
-# The signature test mapping file for the JSON-P 2.0.0 TCK.  This file
+# The signature test mapping file for the JSON-P TCK.  This file
 # should be formatted as a standard java properties file.  The
 # name is the package name and the value is the version of the
 # package that should be tested by the signature tests.
 #
 # The resultant signature file name has a name that complies
 # with the following format:
-# <package>.sig_<technology_version>
+# <package>.sig
 # Given this format, the following example breaks down as follows:
-#    jakarta.json.sig_2.0.0_se11:
+#    jakarta.json.sig:
 #      <package> = jakarta.json
 #      <technology_version> = 2.0.0  (for JSON-P) 
 #

install/jstl/bin/sig-test.map

@@ -20,8 +20,6 @@
 # name is the package name and the value is the version of the
 # package that should be tested by the signature tests.
 #
-#	$Id$
-#
 ###############################################################
 
 # JSTL packages

src/com/sun/ts/tests/signaturetest/README

@@ -1,6 +1,6 @@
-The latest signature files (specific for Java SE 8 & Java SE 11)  were updated in
+The latest signature files  were updated in
 the jakartaee-tck repoitory (src/com/sun/ts/tests/signaturetests/signature-repository) 
-for JakartaEE 9 release. The wikipage to generate the signature files is updated in the 
+for JakartaEE 10 release. The wikipage to generate the signature files is updated in the 
 wiki link :
 https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Signature-Tests-in-JakartaEE-TCK
 
@@ -66,9 +66,9 @@ signature tests.  All signatures files live in the following directory:
 $TS_HOME/src/com/sun/ts/tests/signaturetest/signature-repository/
 Users should see if their signatures already exist in this directory.
 Note, every property in the sig-test.map file maps to a signature
-file.  For example the property "jakarta.ejb=4.0_se11" maps to the signature
+file.  For example the property "jakarta.ejb=4.0" maps to the signature
 file:
- $TS_HOME/src/com/sun/ts/tests/signaturetest/signature-repository/jakarta.ejb.sig_4.0_se11
+ $TS_HOME/src/com/sun/ts/tests/signaturetest/signature-repository/jakarta.ejb.sig
 
 If the signature file already exist, the user should checkout the signature
 file (using git clone) then record the new signatures and do an "git diff"