BVTCK-208 Remove all mentions of JSR 380

README.md

@@ -1,7 +1,7 @@
 # Jakarta Bean Validation TCK
 *Version: 2.0.4.Final - 10-08-2018*
 
-This repository contains the Jakarta Bean Validation 2.0 ([JSR 380](http://www.jcp.org/en/jsr/detail?id=380))
+This repository contains the Jakarta Bean Validation 2.0
 [TCK](http://en.wikipedia.org/wiki/Technology_Compatibility_Kit).
 
 ## Build from Source

distribution/pom.xml

@@ -19,8 +19,8 @@
 
     <artifactId>beanvalidation-tck-distribution</artifactId>
 
-    <name>JSR-380 TCK Distribution</name>
-    <description>JSR-380 TCK Distribution</description>
+    <name>Jakarta Bean Validation TCK Distribution</name>
+    <description>Jakarta Bean Validation TCK Distribution</description>
 
     <properties>
         <beanvalidation-tck-parent.basedir>${project.parent.basedir}</beanvalidation-tck-parent.basedir>

documentation/pom.xml

@@ -19,8 +19,8 @@
     <artifactId>beanvalidation-tck-documentation</artifactId>
     <packaging>jar</packaging>
 
-    <name>JSR-380 TCK Documentation</name>
-    <description>&gt;Jakarta Bean Validation TCK Documentation</description>
+    <name>Jakarta Bean Validation TCK Documentation</name>
+    <description>Jakarta Bean Validation TCK Documentation</description>
 
     <properties>
         <beanvalidation-tck-parent.basedir>${project.parent.basedir}</beanvalidation-tck-parent.basedir>
@@ -174,7 +174,6 @@
                         <tabsize>4</tabsize>
 
                         <copyrightYear>2009 - ${current-year}</copyrightYear>
-                        <jsrVersion>JSR 380</jsrVersion>
                         <tckVersion>${project.version}</tckVersion>
                         <validationApiVersion>${validation.api.version}</validationApiVersion>
                         <hibernateValidatorVersion>${hibernate.validator.version}</hibernateValidatorVersion>

documentation/src/main/asciidoc/appeals-process.asciidoc

@@ -2,11 +2,11 @@
 == Appeals Process
 
 While the Jakarta Bean Validation TCK is rigorous about enforcing an
-implementation's conformance to the {jsrVersion} specification, it's
+implementation's conformance to the Jakarta Bean Validation specification, it's
 reasonable to assume that an implementor may discover new and/or better ways
 to validate the assertions. This chapter covers the appeals process, defined
 by the Specification Lead, Red Hat, Inc., which allows implementors of the
-{jsrVersion} specification to challenge one or more tests defined by the
+Jakarta Bean Validation specification to challenge one or more tests defined by the
 Jakarta Bean Validation TCK.
 
 The appeals process identifies who can make challenges to the TCK,
@@ -25,8 +25,8 @@ make a private appeal are therefore provided.
 === Who can make challenges to the TCK?
 
 Any implementor may submit an appeal to challenge one or more tests
-in the Jakarta Bean Validation TCK. In fact, members of the {jsrVersion} Expert
-Group (EG) encourage this level of participation.
+in the Jakarta Bean Validation TCK. In fact, members of the Jakarta Bean Validation
+Expert Group (EG) encourage this level of participation.
 
 === What challenges to the TCK may be submitted?
 
@@ -37,7 +37,7 @@ appeal.
 
 What is generally not challengeable are the assertions made by the
 specification. The specification document is controlled by a separate
-process and challenges to it should be handled through the {jsrVersion} EG
+process and challenges to it should be handled through the Jakarta Bean Validation EG
 by sending an e-mail to mailto:beanvalidation-tck@redhat.com[beanvalidation-tck@redhat.com].
 
 === How these challenges are submitted?
@@ -81,5 +81,5 @@ issue to be resolved.
 
 Resolved issue not addressed for 30 days will be closed by the TCK
 Project Lead. If the TCK Project Lead and appellant are unable to agree on
-the issue resolution, it will be referred to the {jsrVersion}
+the issue resolution, it will be referred to the Jakarta Bean Validation
 specification lead or his/her designate.

documentation/src/main/asciidoc/configuration.asciidoc

@@ -13,7 +13,7 @@ sections.
 The TCK distribution comes with a directory
 `setup-examples` which contains two example projects
 for running the TCK. If you followed the instructions in <<installation>> you find the directory under
-`jsr380/tck/setup-examples`. Both setups are using
+`jakarta-bean-validation/tck/setup-examples`. Both setups are using
 Hibernate Validator as Jakarta Bean Validation Provider and Glassfish 5 as EE
 constainer. However, one is using http://maven.apache.org/[Maven] as build tool to run the TCK,
 the other http://ant.apache.org/[Ant]. Depending which
@@ -46,8 +46,8 @@ modify the file (see also the TestNG http://testng.org/doc/documentation-main.ht
 
 [source,xml]
 ----
-<suite name="JSR-380-TCK" verbose="1">
-    <test name="JSR-380-TCK">
+<suite name="Jakarta-Bean-Validation-TCK" verbose="1">
+    <test name="Jakarta-Bean-Validation-TCK">
 
         <method-selectors>
             <method-selector>
@@ -114,7 +114,7 @@ The adapter is also available as Maven artifact under the GAV
 `org.hibernate.beanvalidation.tck:beanvalidation-standalone-container-adapter:{tckVersion}.`
 You can refer to `pom.xml` in the tck-runner module
 of Hibernate Validator (in the directory
-`jsr380/ri/tck-runner`, if you followed the
+`jakarta-bean-validation/ri/tck-runner`, if you followed the
 instruction in <<installation>>) to see how it is
 used.
 

documentation/src/main/asciidoc/index.asciidoc

@@ -1,4 +1,4 @@
-= TCK Reference Guide for {jsrVersion} - Jakarta Bean Validation
+= TCK Reference Guide for Jakarta Bean Validation
 Emmanuel Bernard - Red Hat, Inc.; Hardy Ferentschik - Red Hat, Inc.; Gunnar Morling - Red Hat, Inc.
 :doctype: book
 :revdate: {docdate}

documentation/src/main/asciidoc/installation.asciidoc

@@ -29,7 +29,7 @@ readme.md
 
 You can also download the source code from GitHub - https://github.com/beanvalidation/beanvalidation-tck[https://github.com/beanvalidation/beanvalidation-tck].
 
-The {jsrVersion} reference implementation (RI) project is named
+The Jakarta Bean Validation reference implementation (RI) project is named
 Hibernate Validator. You can obtain the Hibernate Validator release used
 as reference implementation from the Hibernate Validator http://www.hibernate.org/subprojects/validator/download[download
 page].
@@ -55,8 +55,8 @@ runtime.
 
 The rest of the TCK software can simply be extracted. It's
 recommended that you create a dedicated folder to hold all of the
-JSR 380-related artifacts. This guide assumes the folder is called
-`jsr380`. Extract the `src` folder
+Jakarta Bean Validation-related artifacts. This guide assumes the folder is called
+`jakarta-bean-validation`. Extract the `src` folder
 of the TCK distribution into a sub-folder named `tck`
 or use the following git commands:
 
@@ -80,7 +80,7 @@ The resulting folder structure is shown here:
 
 [source]
 ----
-jsr380/
+jakarta-bean-validation/
    ri/
    tck/
 ----

documentation/src/main/asciidoc/introduction.asciidoc

@@ -76,7 +76,7 @@ about enforcing the rules the specification lays down.
 
 The Jakarta Bean Validation TCK is designed as a portable, configurable and
 automated test suite for verifying the compatibility of an implementation
-of {jsrVersion}. The test suite is built atop TestNG and provides a series
+of Jakarta Bean Validation. The test suite is built atop TestNG and provides a series
 of extensions that allow runtime packaging and deployment of JEE artifacts
 for in-container testing (Arquillian).
 

documentation/src/main/asciidoc/preface.asciidoc

@@ -3,7 +3,7 @@
 
 This guide describes how to download, install, configure, and run the
 Technology Compatibility Kit (TCK) used to verify the compatibility of an
-implementation of {jsrVersion}: Jakarta Bean Validation 2.0.
+implementation of Jakarta Bean Validation 2.0.
 
 The Jakarta Bean Validation TCK is built atop http://www.jboss.org/arquillian.html[Arquillian], a portable
 and configurable automated test suite for authoring unit and integration
@@ -23,9 +23,8 @@ their implementation.
 === Before You Read This Guide
 
 The Jakarta Bean Validation TCK is based on the Jakarta Bean Validation
-specification 2.0 ({jsrVersion}). Information about the specification can
-be found on the http://jcp.org/en/jsr/detail?id=380[JSR-380
-JCP page].
+specification 2.0. Information about the specification can
+be found on the https://projects.eclipse.org/projects/ee4j.bean-validation[Jakarta Bean Validation page].
 
 [[book-organization]]
 === How This Guide Is Organized
@@ -51,7 +50,7 @@ it.
 * <<reporting>> explains the test reports that are
 generated by the TCK test suite and introduces the TCK audit report as
 a tool for measuring the completeness of the TCK in testing the
-{jsrVersion} specification and in understanding how test cases relate
+Jakarta Bean Validation specification and in understanding how test cases relate
 to the specification.
 
 * <<configuration>> details the configuration of the

documentation/src/main/asciidoc/reporting.asciidoc

@@ -10,15 +10,15 @@ results.
 A specification can be distilled into a collection of assertions
 that define the behavior of the software. This section introduces the Bean
 Validation TCK coverage report, which documents the relationship between
-the assertions that have been identified in the {jsrVersion} specification
+the assertions that have been identified in the Jakarta Bean Validation specification
 document and the tests in the TCK test suite.
 
 The structure of this report is controlled by the assertion
 document, so we'll start there.
 
 ==== Jakarta Bean Validation TCK Assertions
 
-The Jakarta Bean Validation TCK developers have analyzed the {jsrVersion}
+The Jakarta Bean Validation TCK developers have analyzed the Jakarta Bean Validation
 specification document and identified the assertions that are present in
 each chapter. Here's an example of one such assertion found in section
 2.1: "Every constraint annotation must define a message element of

pom.xml

@@ -13,10 +13,10 @@
     <artifactId>beanvalidation-tck-parent</artifactId>
     <packaging>pom</packaging>
     <version>2.0.5-SNAPSHOT</version>
-    <name>JSR-380 TCK Aggregator</name>
+    <name>Jakarta Bean Validation TCK Aggregator</name>
     <url>http://beanvalidation.org/</url>
 
-    <description>JSR-380 TCK</description>
+    <description>Jakarta Bean Validation TCK</description>
 
     <modules>
         <module>tests</module>

setup-examples/ant/build.xml

@@ -7,7 +7,7 @@
     See the license.txt file in the root directory or <http://www.apache.org/licenses/LICENSE-2.0>.
 
 -->
-<project name="JSR-380 TCK" default="test" basedir="." xmlns:ivy="antlib:org.apache.ivy.ant">
+<project name="Jakarta Bean Validation TCK" default="test" basedir="." xmlns:ivy="antlib:org.apache.ivy.ant">
 
     <!-- ====================================================================== -->
     <!-- Build environment properties                                           -->

setup-examples/ant/readme.md

@@ -1,4 +1,4 @@
-# Ant + Ivy setup example to run the JSR-380 TCK
+# Ant + Ivy setup example to run the Jakarta Bean Validation TCK
 
 This is an example setup to run the Jakarta Bean Validation TCK 2.0 against Glassfish 5 (the Java EE 8 reference implementation)
 using [Ant](https://ant.apache.org) + [Ivy](http://ant.apache.org/ivy/) as build environment.

setup-examples/maven/pom.xml

@@ -17,7 +17,7 @@
     <version>2.0-SNAPSHOT</version>
 
     <name>Example Jakarta Bean Validation TCK Runner</name>
-    <description>Aggregates dependencies and runs the JSR-380 TCK</description>
+    <description>Aggregates dependencies and runs the Jakarta Bean Validation TCK</description>
 
     <properties>
         <tck.version>2.0.0-SNAPSHOT</tck.version>

setup-examples/maven/readme.md

@@ -1,4 +1,4 @@
-# Maven setup example to run the JSR-380 TCK
+# Maven setup example to run the Jakarta Bean Validation TCK
 
 This is an example setup to run the Jakarta Bean Validation TCK 2.0 against Glassfish 5 using [Maven](https://maven.apache.org).
 

setup-examples/readme.md

@@ -1,4 +1,4 @@
-# JSR-380 TCK setup examples
+# Jakarta Bean Validation TCK setup examples
 
 This directory contains [Ant](https://ant.apache.org) and [Maven](https://maven.apache.org/) setup examples for
 running the [Jakarta Bean Validation](http://beanvalidation.org/) TCK against [Glassfish 5](https://javaee.github.io/glassfish/),

standalone-container-adapter/pom.xml

@@ -20,8 +20,8 @@
     <artifactId>beanvalidation-standalone-container-adapter</artifactId>
     <packaging>jar</packaging>
 
-    <name>JSR-380 TCK Container Adapter</name>
-    <description>JSR-380 TCK Arquillian Standalone Container Adapter</description>
+    <name>Jakarta Bean Validation TCK Container Adapter</name>
+    <description>Jakarta Bean Validation TCK Arquillian Standalone Container Adapter</description>
 
     <properties>
         <beanvalidation-tck-parent.basedir>${project.parent.basedir}</beanvalidation-tck-parent.basedir>

tests/pom.xml

@@ -20,8 +20,8 @@
     <artifactId>beanvalidation-tck-tests</artifactId>
     <packaging>jar</packaging>
 
-    <name>JSR-380 TCK Test Suite</name>
-    <description>JSR-380 TCK test suite</description>
+    <name>Jakarta Bean Validation TCK Test Suite</name>
+    <description>Jakarta Bean Validation TCK test suite</description>
 
     <properties>
         <beanvalidation-tck-parent.basedir>${project.parent.basedir}</beanvalidation-tck-parent.basedir>

tests/src/main/resources/tck-audit.xml

@@ -8,7 +8,7 @@
 
 -->
 <!-- Generated by tck-audit.xsl at 2017-07-11 15:29 (revision 2.0.0.CR2-7-gf03fb55) -->
-<specification xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xalan="http://xml.apache.org/xslt" xmlns:exslt="http://exslt.org/common" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://jboss.com/products/weld/tck/audit" xsi:schemaLocation="http://jboss.com/products/weld/tck/audit" name="JSR-380: Jakarta Bean Validation 2.0" version="2.0.0" id="beanvalidation" generateSectionIds="true">
+<specification xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xalan="http://xml.apache.org/xslt" xmlns:exslt="http://exslt.org/common" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://jboss.com/products/weld/tck/audit" xsi:schemaLocation="http://jboss.com/products/weld/tck/audit" name="Jakarta Bean Validation 2.0" version="2.0.0" id="beanvalidation" generateSectionIds="true">
     <section id="introduction" title="Introduction" level="1">
         <!-- 1 - INTRODUCTION -->
     </section>

tests/src/main/resources/tck-tests.xml

@@ -8,8 +8,8 @@
 -->
 <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
 
-<suite name="JSR-380-TCK" verbose="1">
-    <test name="JSR-380-TCK">
+<suite name="Jakarta-Bean-Validation-TCK" verbose="1">
+    <test name="Jakarta-Bean-Validation-TCK">
 
         <method-selectors>
             <method-selector>