Point to docs.hibernate.org instead of docs.jboss.org/hibernate in various docs

Author: marko-bekhta

design/working/6.0-posts.adoc

@@ -2,7 +2,7 @@
 Steve Ebersole
 :awestruct-tags: ["Hibernate ORM"]
 :awestruct-layout: blog-post
-:docs-url: https://docs.jboss.org/hibernate/orm/6.0
+:docs-url: https://docs.hibernate.org/orm/6.0
 :javadocs-url: {docs-url}/javadocs
 :migration-guide-url: {docs-url}/migration-guide/migration-guide.html
 :user-guide-url: {docs-url}/userguide/html_single/Hibernate_User_Guide.html

documentation/src/main/asciidoc/querylanguage/Expressions.adoc

@@ -763,7 +763,7 @@ Recognized Field types are listed below.
 | `offset minute` | `Integer` | 0-59 | Minutes of offset | ✖
 |===
 
-For a full list of field types, see the Javadoc for https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/query/TemporalUnit.html[`TemporalUnit`].
+For a full list of field types, see the Javadoc for https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/query/TemporalUnit.html[`TemporalUnit`].
 
 [source, hql]
 ----
@@ -811,7 +811,7 @@ The pattern must be written in a subset of the pattern language defined by Java'
 select format(local datetime as 'yyyy-MM-dd HH:mm:ss')
 ----
 
-For a full list of `format()` pattern elements, see the Javadoc for https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/dialect/Dialect.html#appendDatetimeFormat[`Dialect.appendDatetimeFormat`].
+For a full list of `format()` pattern elements, see the Javadoc for https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/dialect/Dialect.html#appendDatetimeFormat[`Dialect.appendDatetimeFormat`].
 
 [[function-trunc-datetime]]
 [discrete]

documentation/src/main/asciidoc/shared/url-attributes.adoc

@@ -4,7 +4,7 @@
 
 include::./common-attributes.adoc[]
 
-:doc-base-url: https://docs.jboss.org/hibernate/orm
+:doc-base-url: https://docs.hibernate.org/orm
 :doc-version-base-url: {doc-base-url}/{majorMinorVersion}
 :doc-migration-guide-url: {doc-version-base-url}/migration-guide/migration-guide.html
 :doc-quick-start-url: {doc-version-base-url}/quickstart/html_single/

documentation/src/main/asciidoc/userguide/appendices/LegacyBasicTypeResolution.adoc

@@ -121,7 +121,7 @@ But first, let's explore how implicit resolution works and how applications can
 ====
 A thorough discussion of `BasicTypeRegistry` and all the different ways to contribute types is beyond the scope of this documentation.
 
-Please see the http://docs.jboss.org/hibernate/orm/{majorMinorVersion}/integrationguide/html_single/Hibernate_Integration_Guide.html[Integration Guide] for complete details.
+Please see the http://docs.hibernate.org/orm/{majorMinorVersion}/integrationguide/html_single/[Integration Guide] for complete details.
 ====
 
 As an example, take a String attribute such as we saw before with Product#sku.

documentation/src/main/asciidoc/userguide/chapters/caching/Caching.adoc

@@ -38,7 +38,7 @@ Besides provider specific configuration, there are a number of configurations op
 
 `hibernate.cache.use_second_level_cache`::
 	Enable or disable second level caching overall. By default, if the currently configured
-	https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/cache/spi/RegionFactory.html[`RegionFactory`] is not the `NoCachingRegionFactory`, then the second-level cache is going to be enabled. Otherwise, the second-level cache is disabled.
+	https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/cache/spi/RegionFactory.html[`RegionFactory`] is not the `NoCachingRegionFactory`, then the second-level cache is going to be enabled. Otherwise, the second-level cache is disabled.
 `hibernate.cache.use_query_cache`::
 	Enable or disable second level caching of query results. The default is false.
 `hibernate.cache.query_cache_factory`::
@@ -119,7 +119,7 @@ transactional::
 ====
 Rather than using a global setting, it is recommended to define the cache concurrency strategy on a per entity basis.
 
-Use the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/Cache.html[`@org.hibernate.annotations.Cache`] annotation for this purpose.
+Use the https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/Cache.html[`@org.hibernate.annotations.Cache`] annotation for this purpose.
 ====
 
 The `@Cache` annotation define three attributes:
@@ -376,7 +376,7 @@ include::{example-dir-caching}/SecondLevelCacheTest.java[tags=caching-query-regi
 
 [NOTE]
 ====
-When using {jpaJavadocUrlPrefix}CacheStoreMode.html#REFRESH[`CacheStoreMode.REFRESH`] or https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/CacheMode.html#REFRESH[`CacheMode.REFRESH`] in conjunction with the region you have defined for the given query,
+When using {jpaJavadocUrlPrefix}CacheStoreMode.html#REFRESH[`CacheStoreMode.REFRESH`] or https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/CacheMode.html#REFRESH[`CacheMode.REFRESH`] in conjunction with the region you have defined for the given query,
 Hibernate will selectively force the results cached in that particular region to be refreshed.
 
 This behavior is particularly useful in cases when the underlying data may have been updated via a separate process
@@ -418,7 +418,7 @@ by placing the annotation on the entity class or the persistent collection attri
 [[caching-management]]
 === Managing the cached data
 
-Traditionally, Hibernate defined the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/CacheMode.html[`CacheMode`] enumeration to describe
+Traditionally, Hibernate defined the https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/CacheMode.html[`CacheMode`] enumeration to describe
 the ways of interactions with the cached data.
 Jakarta Persistence split cache modes by storage ({jpaJavadocUrlPrefix}CacheStoreMode.html[`CacheStoreMode`])
 and retrieval ({jpaJavadocUrlPrefix}CacheRetrieveMode.html[`CacheRetrieveMode`]).
@@ -494,7 +494,7 @@ include::{example-dir-caching}/SecondLevelCacheTest.java[tags=caching-management
 ====
 
 Hibernate is much more flexible in this regard as it offers fine-grained control over what needs to be evicted.
-The https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/Cache.html[`org.hibernate.Cache`] interface defines various evicting strategies:
+The https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/Cache.html[`org.hibernate.Cache`] interface defines various evicting strategies:
 
 - entities (by their class or region)
 - entities stored using the natural-id (by their class or region)
@@ -517,7 +517,7 @@ If you enable the `hibernate.generate_statistics` configuration property,
 Hibernate will expose a number of metrics via `SessionFactory.getStatistics()`.
 Hibernate can even be configured to expose these statistics via JMX.
 
-This way, you can get access to the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/stat/Statistics.html[`Statistics`] class which comprises all sort of
+This way, you can get access to the https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/stat/Statistics.html[`Statistics`] class which comprises all sort of
 second-level cache metrics.
 
 [[caching-statistics-example]]

documentation/src/main/asciidoc/userguide/chapters/domain/associations.adoc

@@ -755,7 +755,7 @@ include::{extrasdir}/associations-many-to-any-example.sql[]
 [[associations-JoinFormula]]
 ==== `@JoinFormula` mapping
 
-The https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/JoinFormula.html[`@JoinFormula`] annotation is used to customize the join between a child Foreign Key and a parent row Primary Key.
+The https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/JoinFormula.html[`@JoinFormula`] annotation is used to customize the join between a child Foreign Key and a parent row Primary Key.
 
 [[associations-JoinFormula-example]]
 .`@JoinFormula` mapping usage
@@ -805,7 +805,7 @@ Therefore, the `@JoinFormula` annotation is used to define a custom join associa
 [[associations-JoinColumnOrFormula]]
 ==== `@JoinColumnOrFormula` mapping
 
-The https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/JoinColumnOrFormula.html[`@JoinColumnOrFormula`] annotation is used to customize the join between a child Foreign Key and a parent row Primary Key when we need to take into consideration a column value as well as a `@JoinFormula`.
+The https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/JoinColumnOrFormula.html[`@JoinColumnOrFormula`] annotation is used to customize the join between a child Foreign Key and a parent row Primary Key when we need to take into consideration a column value as well as a `@JoinFormula`.
 
 [[associations-JoinColumnOrFormula-example]]
 .`@JoinColumnOrFormula` mapping usage

documentation/src/main/asciidoc/userguide/chapters/domain/basic_types.adoc

@@ -2022,7 +2022,7 @@ include::{example-dir-resources}/mapping/converter/hbm/MoneyConverterHbmTest.hbm
 A basic type that's converted by a Jakarta Persistence `AttributeConverter` is immutable if the underlying Java type is immutable
 and is mutable if the associated attribute type is mutable as well.
 
-Therefore, mutability is given by the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/type/descriptor/java/JavaType.html#getMutabilityPlan--[`JavaType#getMutabilityPlan`]
+Therefore, mutability is given by the https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/type/descriptor/java/JavaType.html#getMutabilityPlan--[`JavaType#getMutabilityPlan`]
 of the associated entity attribute type.
 
 This can be adjusted by using `@Immutable` or `@Mutability` on any of:
@@ -2601,8 +2601,8 @@ include::{example-dir-generated}/temporals/GeneratedUuidTests.java[tags=mapping-
 ----
 ====
 
-See https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/ValueGenerationType.html[`@ValueGenerationType`]
-and https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/generator/AnnotationValueGeneration.html[`AnnotationBasedGenerator`]
+See https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/ValueGenerationType.html[`@ValueGenerationType`]
+and https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/generator/AnnotationValueGeneration.html[`AnnotationBasedGenerator`]
 for details of each contract
 
 

documentation/src/main/asciidoc/userguide/chapters/domain/collections.adoc

@@ -3,7 +3,7 @@
 :core-project-dir: {root-project-dir}/hibernate-core
 :core-test-base: {core-project-dir}/src/test/java
 :example-dir-collection: {core-test-base}/org/hibernate/orm/test/mapping/collections
-:docs-base: https://docs.jboss.org/hibernate/orm/{majorMinorVersion}
+:docs-base: https://docs.hibernate.org/orm/{majorMinorVersion}
 :javadoc-base: {docs-base}/javadocs
 :java-javadoc-base: https://docs.oracle.com/en/java/javase/11/docs/api/java.base
 :extrasdir: extras/collections
@@ -722,7 +722,7 @@ When fetching the collection, Hibernate will use the fetched ordered columns to
 [[collections-customizing-ordered-list-ordinal]]
 ===== Customizing ordered list ordinal
 
-You can customize the ordinal of the underlying ordered list by using the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/ListIndexBase.html[`@ListIndexBase`] annotation.
+You can customize the ordinal of the underlying ordered list by using the https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/ListIndexBase.html[`@ListIndexBase`] annotation.
 
 [[collections-customizing-ordered-list-ordinal-mapping-example]]
 .`@ListIndexBase` mapping example
@@ -755,7 +755,7 @@ include::{extrasdir}/collections-customizing-ordered-list-ordinal-persist-exampl
 While the Jakarta Persistence
 {jpaJavadocUrlPrefix}OrderBy.html[`@OrderBy`] annotation allows you to specify the entity attributes used for sorting
 when fetching the current annotated collection, the Hibernate specific
-https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/OrderBy.html[`@OrderBy`] annotation is used to specify a *SQL* clause instead.
+https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/OrderBy.html[`@OrderBy`] annotation is used to specify a *SQL* clause instead.
 
 In the following example, the `@OrderBy` annotation uses the `CHAR_LENGTH` SQL function to order the `Article` entities
 by the number of characters of the `name` attribute.
@@ -936,7 +936,7 @@ include::{extrasdir}/collections-map-value-type-entity-key-add-example.sql[]
 ===== Maps with a custom key type
 
 Hibernate defines the
-https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/MapKeyType.html[`@MapKeyType`] annotation
+https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/MapKeyType.html[`@MapKeyType`] annotation
 which you can use to customize the `Map` key type.
 
 Considering you have the following tables in your database:

documentation/src/main/asciidoc/userguide/chapters/domain/embeddables.adoc

@@ -302,7 +302,7 @@ Embeddable types that are used as collection entries, map keys or entity type id
 [[embeddable-Target]]
 ==== `@TargetEmbeddable` mapping
 
-The https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/TargetEmbeddable.html[`@TargetEmbeddable`] annotation is used to specify the implementation class of an embeddable-valued mapping when the declared type is a non-concrete type (interface, etc).
+The https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/TargetEmbeddable.html[`@TargetEmbeddable`] annotation is used to specify the implementation class of an embeddable-valued mapping when the declared type is a non-concrete type (interface, etc).
 
 As an example, consider an `@Embedded` attribute (`City.coordinates`) whose declared type (`Coordinates`) is an interface.  However, Hibernate needs to know about the concrete type to use, which is `GPS` in this case.  The `@TargetEmbeddable` annotation is used to provide this information.
 

documentation/src/main/asciidoc/userguide/chapters/domain/entity.adoc

@@ -404,7 +404,7 @@ For details on mapping the identifier, see the <<chapters/domain/identifiers.ado
 [[entity-sql-query-mapping]]
 ==== Mapping the entity to a SQL query
 
-You can map an entity to a SQL query using the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/Subselect.html[`@Subselect`] annotation.
+You can map an entity to a SQL query using the https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/Subselect.html[`@Subselect`] annotation.
 
 [[mapping-Subselect-example]]
 .`@Subselect` entity mapping
@@ -463,7 +463,7 @@ Hibernate will trigger a Persistence Context flush if there are pending `Account
 
 When working with lazy associations or entity references for types that define and inheritance hierarchy Hibernate often creates proxies starting from the root class, with no information about the actual subtype that's referenced by the lazy instance. This can be a problem when using `instanceof` to check the type of said lazy entity references or when trying to cast to the concrete subtype.
 
-The https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/ConcreteProxy.html[`@ConcreteProxy`] annotation can be used on an entity hierarchy root mapping to specify that Hibernate should always try to resolve the actual subtype corresponding to the proxy instance created. This effectively means that proxies for that entity hierarchy will always be created from the correct subclass, allowing to preserve laziness and enable using type checks and casts.
+The https://docs.hibernate.org/orm/{majorMinorVersion}/javadocs/org/hibernate/annotations/ConcreteProxy.html[`@ConcreteProxy`] annotation can be used on an entity hierarchy root mapping to specify that Hibernate should always try to resolve the actual subtype corresponding to the proxy instance created. This effectively means that proxies for that entity hierarchy will always be created from the correct subclass, allowing to preserve laziness and enable using type checks and casts.
 
 [[entity-concrete-proxy-mapping]]
 .Root entity class annotated with `@ConcreteProxy`