Sync documentation of main branch

Author: actions-user

_data/versioned/main/index/quarkus.yaml

@@ -63,7 +63,6 @@ types:
     - io.quarkus:quarkus-reactive-db2-client
     - io.quarkus:quarkus-reactive-mssql-client
     - io.quarkus:quarkus-jdbc-db2
-    - io.quarkus:quarkus-jdbc-derby
     - io.quarkus:quarkus-jdbc-h2
     - io.quarkus:quarkus-jdbc-mariadb
     - io.quarkus:quarkus-jdbc-mssql
@@ -1530,7 +1529,6 @@ types:
     - io.quarkus:quarkus-reactive-oracle-client
     - io.quarkus:quarkus-reactive-pg-client
     - io.quarkus:quarkus-jdbc-db2
-    - io.quarkus:quarkus-jdbc-derby
     - io.quarkus:quarkus-jdbc-h2
     - io.quarkus:quarkus-jdbc-mariadb
     - io.quarkus:quarkus-jdbc-mssql

_data/versioned/main/index/relations.yaml

@@ -2967,7 +2967,7 @@
   - title: Configure data sources in Quarkus
     url: /guides/datasource
     type: reference
-    matches: 12
+    matches: 11
   - title: Reactive SQL Clients
     url: /guides/reactive-sql-clients
     type: guide
@@ -3122,7 +3122,7 @@
   - title: Dev Services for Databases
     url: /guides/databases-dev-services
     type: guide
-    matches: 12
+    matches: 11
   - title: Reactive SQL Clients
     url: /guides/reactive-sql-clients
     type: guide

_generated-doc/main/infra/quarkus-all-build-items.adoc

@@ -6961,11 +6961,11 @@ _No Javadoc found_
 
 _No Javadoc found_
 
-`java.util.Map<String,Path> localizedFiles` 
+`java.util.Map<String,List<MessageFile>> localizedFiles` 
 
 _No Javadoc found_
 
-`java.util.Map<String,Path> mergeCandidates` 
+`java.util.Map<String,List<MessageFile>> mergeCandidates` 
 
 _No Javadoc found_
 

_versions/main/guides/cli-tooling.adoc

@@ -461,7 +461,6 @@ JDBC Driver - MariaDB                              quarkus-jdbc-mariadb
 JDBC Driver - Microsoft SQL Server                 quarkus-jdbc-mssql
 JDBC Driver - MySQL                                quarkus-jdbc-mysql
 JDBC Driver - Oracle                               quarkus-jdbc-oracle
-JDBC Driver - Derby                                quarkus-jdbc-derby
 Elytron Security JDBC                              quarkus-elytron-security-jdbc
 Agroal - Database connection pool                  quarkus-agroal
 ----

_versions/main/guides/databases-dev-services.adoc

@@ -7,14 +7,13 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 :categories: data, tooling
 include::_attributes.adoc[]
 :topics: dev-services,data,database,datasource,dev-mode,testing
-:extensions: io.quarkus:quarkus-agroal,io.quarkus:quarkus-reactive-mysql-client,io.quarkus:quarkus-reactive-oracle-client,io.quarkus:quarkus-reactive-pg-client,io.quarkus:quarkus-jdbc-db2,io.quarkus:quarkus-jdbc-derby,io.quarkus:quarkus-jdbc-h2,io.quarkus:quarkus-jdbc-mariadb,io.quarkus:quarkus-jdbc-mssql,io.quarkus:quarkus-jdbc-mysql,io.quarkus:quarkus-jdbc-oracle,io.quarkus:quarkus-jdbc-postgresql
+:extensions: io.quarkus:quarkus-agroal,io.quarkus:quarkus-reactive-mysql-client,io.quarkus:quarkus-reactive-oracle-client,io.quarkus:quarkus-reactive-pg-client,io.quarkus:quarkus-jdbc-db2,io.quarkus:quarkus-jdbc-h2,io.quarkus:quarkus-jdbc-mariadb,io.quarkus:quarkus-jdbc-mssql,io.quarkus:quarkus-jdbc-mysql,io.quarkus:quarkus-jdbc-oracle,io.quarkus:quarkus-jdbc-postgresql
 
 When testing or running in dev mode Quarkus can provide you with a zero-config database out of the box, a feature we refer to as Dev Services.
 Depending on your database type you may need Docker installed in order to use this feature.
 Dev Services is supported for the following databases:
 
 * DB2 (container) (requires <<#license_acceptance,license acceptance>>)
-* Derby (in-process)
 * H2 (in-process)
 * MariaDB (container)
 * Microsoft SQL Server (container) (requires <<#license_acceptance,license acceptance>>)
@@ -43,7 +42,7 @@ quarkus.devservices.enabled=false
 quarkus.datasource.devservices.enabled=false
 ----
 
-Dev Services for databases relies on Docker to start the server (except for H2 and Derby which are run in process).
+Dev Services for databases relies on Docker to start the server (except for H2 which is run in process).
 If your environment does not support Docker, you will need to start the server manually, or connect to an already running server.
 
 [[license_acceptance]]
@@ -90,7 +89,7 @@ Quarkus will (by default) stop all database Dev Services.
 [[reuse-across-executions]]
 === Reusing Dev Service containers across runs
 
-Assuming you rely on Dev Services based on containers (unlike H2 or Derby),
+Assuming you rely on Dev Services based on containers (unlike H2),
 if you want to keep Dev Service containers running *after a dev mode session or test suite execution*
 to reuse them in the next dev mode session or test suite execution,
 this is possible as well.

_versions/main/guides/datasource.adoc

@@ -9,7 +9,7 @@ include::_attributes.adoc[]
 :diataxis-type: reference
 :categories: data,getting-started,reactive
 :topics: data,database,datasource,sql,jdbc,reactive
-:extensions: io.quarkus:quarkus-agroal,io.quarkus:quarkus-reactive-mysql-client,io.quarkus:quarkus-reactive-oracle-client,io.quarkus:quarkus-reactive-pg-client,io.quarkus:quarkus-reactive-db2-client,io.quarkus:quarkus-reactive-pg-client,io.quarkus:quarkus-reactive-mssql-client,io.quarkus:quarkus-jdbc-db2,io.quarkus:quarkus-jdbc-derby,io.quarkus:quarkus-jdbc-h2,io.quarkus:quarkus-jdbc-mariadb,io.quarkus:quarkus-jdbc-mssql,io.quarkus:quarkus-jdbc-mysql,io.quarkus:quarkus-jdbc-oracle,io.quarkus:quarkus-jdbc-postgresql
+:extensions: io.quarkus:quarkus-agroal,io.quarkus:quarkus-reactive-mysql-client,io.quarkus:quarkus-reactive-oracle-client,io.quarkus:quarkus-reactive-pg-client,io.quarkus:quarkus-reactive-db2-client,io.quarkus:quarkus-reactive-pg-client,io.quarkus:quarkus-reactive-mssql-client,io.quarkus:quarkus-jdbc-db2,io.quarkus:quarkus-jdbc-h2,io.quarkus:quarkus-jdbc-mariadb,io.quarkus:quarkus-jdbc-mssql,io.quarkus:quarkus-jdbc-mysql,io.quarkus:quarkus-jdbc-oracle,io.quarkus:quarkus-jdbc-postgresql
 
 Use a unified configuration model to define data sources for Java Database Connectivity (JDBC) and Reactive drivers.
 
@@ -64,9 +64,6 @@ For more details and optional configurations, see xref:databases-dev-services.ad
 . Add the correct JDBC extension for the database of your choice.
 
 * `quarkus-jdbc-db2`
-* `quarkus-jdbc-derby`
-+
-include::_includes/snip-note-derby.adoc[]
 * `quarkus-jdbc-h2`
 * `quarkus-jdbc-mariadb`
 * `quarkus-jdbc-mssql`
@@ -152,9 +149,6 @@ If the application operates with a single driver, this driver is detected automa
 Quarkus currently includes the following built-in database kinds:
 +
 * DB2: `db2`
-* Derby: `derby`
-+
-include::_includes/snip-note-derby.adoc[]
 * H2: `h2`
 * MariaDB: `mariadb`
 * Microsoft SQL Server: `mssql`
@@ -194,14 +188,11 @@ JDBC is the most common database connection pattern, typically needed when used
 
 .. For use with a built-in JDBC driver, choose and add the Quarkus extension for your relational database driver from the list below:
 +
-* Derby - `quarkus-jdbc-derby`
-+
-include::_includes/snip-note-derby.adoc[]
 * H2 - `quarkus-jdbc-h2`
 +
 [NOTE]
 ====
-You can configure H2 and Derby databases to run in "embedded mode"; however, the Derby extension does not support compiling the embedded database engine into native executables.
+You can configure H2 databases to run in "embedded mode"
 
 For suggestions regarding integration testing, see <<in-memory-databases,Testing with in-memory databases>> .
 ====
@@ -700,20 +691,17 @@ You will usually specify the `db-kind` property or explicitly enable Dev Service
 [[in-memory-databases]]
 === Testing with in-memory databases
 
-Some databases like H2 and Derby are commonly used in the _embedded mode_ as a facility to run integration tests quickly.
+Some databases like H2 are commonly used in the _embedded mode_ as a facility to run integration tests quickly.
 
 The recommended approach is to use the database intended for production to get results as close as possible to a production environment.
 This is made easier by xref:databases-dev-services.adoc[Dev Services] because they require no configuration and start relatively quickly.
 However, it is also possible to use JVM-powered databases for scenarios when the ability to run simple integration tests is required.
 
 ==== Support and limitations
 
-Embedded databases (H2 and Derby) work in JVM mode.
+Embedded databases (H2) work in JVM mode.
 For native mode, the following limitations apply:
 
-* Derby cannot be embedded into the application in native mode.
-However, the Quarkus Derby extension allows native compilation of the Derby JDBC *client*, supporting *remote* connections.
-
 * Embedding H2 within your native image is not recommended.
 Consider using an alternative approach, for example, using a remote connection to a separate database instead.
 
@@ -723,14 +711,12 @@ ifndef::no-deprecated-test-resource[]
 . Add a dependency on the artifacts providing the additional tools that are under the following Maven coordinates:
 +
 * `io.quarkus:quarkus-test-h2` for H2
-* `io.quarkus:quarkus-test-derby` for Derby
 +
 This will allow you to test your application even when it is compiled into a native executable while the database will run as a JVM process.
 
 . Add the following specific annotation on any class in your integration tests for running integration tests in both JVM or native executables:
 +
 * `@QuarkusTestResource(H2DatabaseTestResource.class)`
-* `@QuarkusTestResource(DerbyDatabaseTestResource.class)`
 +
 This ensures that the test suite starts and terminates the managed database in a separate process as required for test execution.
 +
@@ -783,17 +769,6 @@ Example:: `jdbc:db2://localhost:50000/MYDB:user=dbadm;password=dbadm;`
 
 For more information on URL syntax and additional supported options, see the link:https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_r0052342.html[official documentation].
 
-==== Derby
-
-`jdbc:derby:[//serverName[:portNumber]/][memory:]databaseName[;property=value[;property=value]]`
-
-Example:: `jdbc:derby://localhost:1527/myDB`, `jdbc:derby:memory:myDB;create=true`
-
-Derby is an embedded database that can run as a server, based on a file, or can run completely in memory.
-All of these options are available as listed above.
-
-For more information, see the link:https://db.apache.org/derby/docs/10.8/devguide/cdevdvlp17453.html#cdevdvlp17453[official documentation].
-
 ==== H2
 
 `jdbc:h2:{ {.|mem:}[name] | [file:]fileName | {tcp|ssl}:[//]server[:port][,server2[:port]]/name }[;key=value...]`
@@ -882,12 +857,6 @@ a|* JDBC: `com.ibm.db2.jcc.DB2Driver`
 
 * XA: `com.ibm.db2.jcc.DB2XADataSource`
 
-|`derby`
-|`quarkus-jdbc-derby`
-a|* JDBC: `org.apache.derby.jdbc.ClientDriver`
-
-* XA: `org.apache.derby.jdbc.ClientXADataSource`
-
 |`h2`
 |`quarkus-jdbc-h2`
 a|* JDBC: `org.h2.Driver`

_versions/main/guides/dev-services.adoc

@@ -80,7 +80,7 @@ and the database URL has not been configured. More information can be found in t
 xref:databases-dev-services.adoc[Databases Dev Services Guide].
 
 Quarkus provides Dev Services for all databases it supports. Most of these are run in a container, except
-H2 and Derby which are run in-process. Dev Services are supported for both JDBC and reactive drivers.
+H2 which is run in-process. Dev Services are supported for both JDBC and reactive drivers.
 
 Those relational databases that are running in a container are started using Testcontainers and support "reusable instances";
 this implies that if you add the property `testcontainers.reuse.enable=true` in your Testcontainers configuration file,

_versions/main/guides/extension-writing-dev-service.adoc

@@ -48,7 +48,7 @@ Here, the https://hub.docker.com/_/hello-world[`hello-world`] image is used, but
 
 [source,java]
 ----
-@BuildStep(onlyIfNot = IsNormal.class, onlyIf = DevServicesConfig.Enabled.class)
+@BuildSteps(onlyIf = { IsDevServicesSupportedByLaunchMode.class, DevServicesConfig.Enabled.class })
 public DevServicesResultBuildItem createContainer() {
     DockerImageName dockerImageName = DockerImageName.parse("hello-world");
     GenericContainer container = new GenericContainer<>(dockerImageName)
@@ -118,7 +118,7 @@ For example,
 
 [source,java]
 ----
-@BuildStep(onlyIfNot = IsNormal.class, onlyIf = DevServicesConfig.Enabled.class)
+@BuildSteps(onlyIf = { IsDevServicesSupportedByLaunchMode.class, DevServicesConfig.Enabled.class })
 public DevServicesResultBuildItem createContainer(MyConfig config) {}
 ----
 

_versions/main/guides/flyway.adoc

@@ -75,12 +75,6 @@ In your build file, add the following dependencies:
     <artifactId>flyway-database-db2</artifactId>
 </dependency>
 
-<!-- Derby specific dependencies -->
-<dependency>
-    <groupId>org.flywaydb</groupId>
-    <artifactId>flyway-database-derby</artifactId>
-</dependency>
-
 <!-- HSQLDB specific dependencies -->
 <dependency>
     <groupId>org.flywaydb</groupId>
@@ -160,8 +154,6 @@ implementation("org.flywaydb:flyway-database-oracle")
 implementation("org.flywaydb:flyway-database-postgresql")
 // Flyway DB2 specific dependencies
 implementation("org.flywaydb:flyway-database-db2")
-// Flyway Derby specific dependencies
-implementation("org.flywaydb:flyway-database-derby")
 // HSQLDB specific dependencies
 implementation("org.flywaydb:flyway-database-hsqldb")
 // Informix specific dependencies

_versions/main/guides/hibernate-orm.adoc

@@ -42,7 +42,6 @@ Add the following dependencies to your project:
 * the Hibernate ORM extension: `io.quarkus:quarkus-hibernate-orm`
 * your JDBC driver extension; the following options are available:
   - `quarkus-jdbc-db2` for link:https://www.ibm.com/products/db2-database[IBM DB2]
-  - `quarkus-jdbc-derby` for link:https://db.apache.org/derby/[Apache Derby]
   - `quarkus-jdbc-h2` for link:https://www.h2database.com/html/main.html[H2]
   - `quarkus-jdbc-mariadb` for link:https://mariadb.com/[MariaDB]
   - `quarkus-jdbc-mssql` for link:https://www.microsoft.com/en-gb/sql-server/[Microsoft SQL Server]