HV-1890 Update versions in documentation

documentation/src/main/asciidoc/ch01.asciidoc

@@ -34,8 +34,8 @@ This transitively pulls in the dependency to the Jakarta Bean Validation API
 
 Hibernate Validator requires an implementation of https://projects.eclipse.org/projects/ee4j.el[Jakarta Expression Language]
 for evaluating dynamic expressions in constraint
-violation messages (see <<section-message-interpolation>>). When your application runs in a Java EE
-container such as JBoss AS, an EL implementation is already provided by the container. In a Java SE
+violation messages (see <<section-message-interpolation>>). When your application runs in a Jakarta EE
+container such as WildFly/JBoss EAP, an EL implementation is already provided by the container. In a Java SE
 environment, however, you have to add an implementation as dependency to your POM file. For instance
 you can add the following dependency to use the Jakarta EL https://github.com/eclipse-ee4j/el-ri[reference
 implementation]:
@@ -82,7 +82,7 @@ Validator CDI portable extension by adding the following Maven dependency to you
 ----
 ====
 
-Note that adding this dependency is usually not required for applications running on a Java EE
+Note that adding this dependency is usually not required for applications running on a Jakarta EE
 application server. You can learn more about the integration of Jakarta Bean Validation and CDI in
 <<section-integration-with-cdi>>.
 

documentation/src/main/asciidoc/ch11.asciidoc

@@ -171,7 +171,7 @@ extractors.
 Furthermore, parameter and return value constraints on the methods and constructors of CDI managed
 beans will automatically be validated upon invocation.
 
-When your application runs on a Java EE container, this integration is enabled by default. When
+When your application runs on a Jakarta EE container, this integration is enabled by default. When
 working with CDI in a Servlet container or in a pure Java SE environment, you can use the CDI
 portable extension provided by Hibernate Validator. To do so, add the portable extension to your
 class path as described in <<section-getting-started-cdi>>.
@@ -250,7 +250,7 @@ constructors.
 ====
 The interceptor `org.hibernate.validator.cdi.internal.interceptor.ValidationInterceptor` is
 registered by `org.hibernate.validator.cdi.internal.ValidationExtension`. This happens implicitly
-within a Java EE runtime environment or explicitly by adding the _hibernate-validator-cdi_
+within a Jakarta EE runtime environment or explicitly by adding the _hibernate-validator-cdi_
 artifact - see <<section-getting-started-cdi>>
 ====
 
@@ -353,9 +353,9 @@ include::{sourcedir}/org/hibernate/validator/referenceguide/chapter11/cdi/method
 ====
 
 
-=== Java EE
+=== Jakarta EE
 
-When your application runs on a Java EE application server such as http://wildfly.org/[WildFly],
+When your application runs on a Jakarta EE application server such as http://wildfly.org/[WildFly],
 you also can obtain `Validator` and `ValidatorFactory` instances via `@Resource` injection in
 managed objects such as EJBs etc., as shown in <<example-validator-resource-injection>>.
 

documentation/src/main/asciidoc/ch12.asciidoc

@@ -113,7 +113,7 @@ fail fast mode when bootstrapping a validator.
 The Jakarta Bean Validation specification defines a set of preconditions which apply when defining
 constraints on methods within class hierarchies. These preconditions are defined in
 {bvSpecUrl}#constraintdeclarationvalidationprocess-methodlevelconstraints-inheritance[section 5.6.5]
-of the Jakarta Bean Validation 2.0 specification. See also <<section-method-constraints-inheritance-hierarchies>>
+of the Jakarta Bean Validation specification. See also <<section-method-constraints-inheritance-hierarchies>>
 in this guide.
 
 As per specification, a Jakarta Bean Validation provider is allowed to relax these preconditions.

documentation/src/main/asciidoc/pr01.asciidoc

@@ -11,7 +11,7 @@ code which is really metadata about the class itself.
 
 image::application-layers.png[]
 
-Jakarta Bean Validation 2.0 - defines a metadata model and API for entity and method validation.
+Jakarta Bean Validation 3.0 defines a metadata model and API for entity and method validation.
 The default metadata source are annotations, with the ability to override and extend the meta-data
 through the use of XML. The API is not tied to a specific application tier nor programming model. It
 is specifically not tied to either web or persistence tier, and is available for both server-side
@@ -23,4 +23,4 @@ Hibernate Validator is the reference implementation of Jakarta Bean Validation.
 well as the Jakarta Bean Validation API and TCK are all provided and distributed under the
 http://www.apache.org/licenses/LICENSE-2.0[Apache Software License 2.0].
 
-Hibernate Validator 6 and Jakarta Bean Validation 2.0 require Java 8 or later.
+Hibernate Validator 7 and Jakarta Bean Validation 3.0 require Java 8 or later.

pom.xml

@@ -101,7 +101,7 @@
 
         <!-- URLs used in javadoc and documentation generation -->
 
-        <bv.spec.url>http://beanvalidation.org/2.0/spec/</bv.spec.url>
+        <bv.spec.url>https://jakarta.ee/specifications/bean-validation/3.0/jakarta-bean-validation-spec-3.0.html</bv.spec.url>
         <java.api-docs.base-url>http://docs.oracle.com/javase/8/docs/api</java.api-docs.base-url>
         <java.technotes.base-url>http://docs.oracle.com/javase/8/docs/technotes</java.technotes.base-url>
         <javaee.api-docs.base-url>http://docs.oracle.com/javaee/7/api</javaee.api-docs.base-url>