Sync documentation of main branch

Author: actions-user

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

@@ -8955,6 +8955,22 @@ _No Javadoc found_
 
 
 
+a| https://github.com/quarkusio/quarkus/blob/main/extensions/security/spi/src/main/java/io/quarkus/security/spi/SecuredInterfaceAnnotationBuildItem.java[`io.quarkus.security.spi.SecuredInterfaceAnnotationBuildItem`, window="_blank"]
+[.description]
+--
+Security annotations on interfaces are in most cases not inherited by interface implementors. This build item allows to register interfaces whose implementors will inherit security annotations. If this build item is used extensively, it can get very complex, and we would create situations, where users can hardly tell precedence, like what will happen if different repeatable annotation instance (like the `PermissionsAllowed` annotation) is placed on both implemented and interface method. Or does method-level interface annotation take precedence over implementors class-level annotation. Examples could continue, for which reason we aim to support simple cases for now. 
+The all the implementors of interfaces matched by this build item annotation will inherit security annotations from interface methods and the interface class-level security annotations only apply directly on the methods declared on the interface. All scenarios that are supposed to work are tested. Any scenario that is not working is not yet supported.
+-- a|`org.jboss.jandex.DotName annotationName` 
+
+_No Javadoc found_
+
+`io.quarkus.security.spi.SecuredAnnotationTargetKind targetKind` 
+
+_No Javadoc found_
+
+
+
+
 a| https://github.com/quarkusio/quarkus/blob/main/extensions/security/spi/src/main/java/io/quarkus/security/spi/SecurityTransformerBuildItem.java[`io.quarkus.security.spi.SecurityTransformerBuildItem`, window="_blank"]
 [.description]
 --
@@ -8971,6 +8987,14 @@ _No Javadoc found_
 
 _No Javadoc found_
 
+`java.util.function.Predicate<ClassInfo> isInterfaceWithTransformations` 
+
+_No Javadoc found_
+
+`java.util.Set<DotName> securedAnnotations` 
+
+_No Javadoc found_
+
 
 |===
 == Security Jakarta Persistence - Common

_versions/main/guides/aws-lambda.adoc

@@ -293,7 +293,7 @@ dependencies {
     implementation 'io.quarkus:quarkus-resteasy'
     implementation 'io.quarkus:quarkus-amazon-lambda'
 
-    testImplementation 'io.quarkus:quarkus-junit5'
+    testImplementation 'io.quarkus:quarkus-junit'
     testImplementation 'io.rest-assured:rest-assured'
 }
 ----

_versions/main/guides/building-my-first-extension.adoc

@@ -263,7 +263,7 @@ Let's have a look at the deployment's `./greeting-extension/deployment/pom.xml`.
         </dependency>
         <dependency>
           <groupId>io.quarkus</groupId>
-          <artifactId>quarkus-junit5-internal</artifactId>
+          <artifactId>quarkus-junit-internal</artifactId>
           <scope>test</scope>
         </dependency>
     </dependencies>
@@ -460,7 +460,7 @@ dependencies {
 
     implementation platform("io.quarkus:quarkus-bom:${quarkus.version}")
 
-    testImplementation 'io.quarkus:quarkus-junit5-internal'
+    testImplementation 'io.quarkus:quarkus-junit-internal'
 }
 ----
 
@@ -666,7 +666,7 @@ Now, Quarkus will process this new task which will result in the bytecode genera
 When developing a Quarkus extension, you mainly want to test your feature is properly deployed in an application and works as expected.
 That's why the tests will be hosted in the `deployment` module.
 
-Quarkus proposes facilities to test extensions via the `quarkus-junit5-internal` artifact (which should already be in the deployment pom.xml), in particular the `io.quarkus.test.QuarkusUnitTest` runner which starts an application with your extension.
+Quarkus proposes facilities to test extensions via the `quarkus-junit-internal` artifact (which should already be in the deployment pom.xml), in particular the `io.quarkus.test.QuarkusUnitTest` runner which starts an application with your extension.
 
 We will use https://rest-assured.io[RestAssured] (massively used in Quarkus) to test our HTTP endpoint.
 Let's add the `rest-assured` dependency into the  `./greeting-extension/deployment/pom.xml`.

_versions/main/guides/doc-contribute-docs-howto.adoc

@@ -269,7 +269,7 @@ Our builds use https://vale.sh[Vale] to check grammar, style, and word usage in
 
 This approach requires a working container runtime (Docker or xref:podman.adoc[Podman]).
 
-The `docs` module has a JUnit 5 test that will run the Vale linter in a container (using https://www.testcontainers.org/[Testcontainers]).
+The `docs` module has a JUnit test that will run the Vale linter in a container (using https://www.testcontainers.org/[Testcontainers]).
 It verifies both Quarkus document metadata and Vale style rules.
 
 Run the test in one of the following ways:

_versions/main/guides/getting-started-testing.adoc

@@ -57,7 +57,7 @@ In your build file you should see 2 test dependencies:
 ----
 <dependency>
     <groupId>io.quarkus</groupId>
-    <artifactId>quarkus-junit5</artifactId>
+    <artifactId>quarkus-junit</artifactId>
     <scope>test</scope>
 </dependency>
 <dependency>
@@ -73,18 +73,18 @@ In your build file you should see 2 test dependencies:
 [source,groovy,subs=attributes+]
 ----
 dependencies {
-    testImplementation("io.quarkus:quarkus-junit5")
+    testImplementation("io.quarkus:quarkus-junit")
     testImplementation("io.rest-assured:rest-assured")
 }
 ----
 ****
 
-`quarkus-junit5` is required for testing, as it provides the `@QuarkusTest` annotation that controls the testing framework.
+`quarkus-junit` is required for testing, as it provides the `@QuarkusTest` annotation that controls the testing framework.
 `rest-assured` is not required but is a convenient way to test HTTP endpoints, we also provide integration that automatically
 sets the correct URL so no configuration is required.
 
-Because we are using JUnit 5, the version of the https://maven.apache.org/surefire/maven-surefire-plugin/[Surefire Maven Plugin]
-must be set, as the default version does not support Junit 5:
+Because we are using JUnit, the version of the https://maven.apache.org/surefire/maven-surefire-plugin/[Surefire Maven Plugin]
+must be set, as the default version does not support JUnit:
 
 [source,xml,subs=attributes+]
 ----
@@ -470,11 +470,11 @@ a bit slower, as it adds a shutdown/startup cycle to the test time, but gives a
 
 To reduce the amount of times Quarkus needs to restart, `io.quarkus.test.junit.util.QuarkusTestProfileAwareClassOrderer`
 is registered as a global `ClassOrderer` as described in the
-link:https://junit.org/junit5/docs/current/user-guide/#writing-tests-test-execution-order-classes[JUnit 5 User Guide].
+link:https://docs.junit.org/current/user-guide/#writing-tests-test-execution-order-classes[JUnit User Guide].
 The behavior of this `ClassOrderer` is configurable via `application.properties` using the property
 `quarkus.test.class-orderer`. The property accepts the FQCN of the `ClassOrderer` to use. If the class cannot be found,
 it fallbacks to JUnit default behaviour which does not set a `ClassOrderer` at all. It can also be disabled entirely by
-setting another `ClassOrderer` that is provided by JUnit 5 or even your own custom one.
+setting another `ClassOrderer` that is provided by JUnit or even your own custom one.
 
 === Writing a Profile
 
@@ -704,7 +704,7 @@ matches the value of `quarkus.test.profile.tags`.
 
 == Nested Tests
 
-JUnit 5 https://junit.org/junit5/docs/current/user-guide/#writing-tests-nested[@Nested tests] are useful for structuring more complex test scenarios.
+JUnit https://docs.junit.org/current/user-guide/#writing-tests-nested[@Nested tests] are useful for structuring more complex test scenarios.
 However, note that it is not possible to assign different test profiles or resources to nested tests within the same parent class.
 
 == Mock Support
@@ -836,12 +836,12 @@ Building on the features provided by `QuarkusMock`, Quarkus also allows users to
 
 [IMPORTANT]
 ====
-This functionality is available with the `@io.quarkus.test.InjectMock` annotation **only if** the `quarkus-junit5-mockito` dependency is present:
+This functionality is available with the `@io.quarkus.test.InjectMock` annotation **only if** the `quarkus-junit-mockito` dependency is present:
 [source,xml]
 ----
 <dependency>
     <groupId>io.quarkus</groupId>
-    <artifactId>quarkus-junit5-mockito</artifactId>
+    <artifactId>quarkus-junit-mockito</artifactId>
     <scope>test</scope>
 </dependency>
 ----
@@ -958,7 +958,7 @@ This is considered an advanced option and should only be performed if you fully
 ==== Using Spies instead of Mocks with `@InjectSpy`
 
 Building on the features provided by `InjectMock`, Quarkus also allows users to effortlessly take advantage of link:https://site.mockito.org/[Mockito] for spying on the beans supported by `QuarkusMock`.
-This functionality is available via the `@io.quarkus.test.junit.mockito.InjectSpy` annotation which is available in the `quarkus-junit5-mockito` dependency.
+This functionality is available via the `@io.quarkus.test.junit.mockito.InjectSpy` annotation which is available in the `quarkus-junit-mockito` dependency.
 
 Sometimes when testing you only need to verify that a certain logical path was taken, or you only need to stub out a single method's response while still executing the rest of the methods on the Spied clone. Please see link:https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/Mockito.html#13[Mockito documentation - Spying on real objects] for more details on Spy partial mocks.
 In either of those situations a Spy of the object is preferable.
@@ -1484,7 +1484,7 @@ while the latter three can coexist.
 The reason of this restriction is that `@QuarkusTest` starts a Quarkus server for the whole lifetime of the tests execution run,
 thus preventing the other tests to start their own Quarkus server.
 
-To alleviate this restriction, the `@QuarkusTest` annotation defines a JUnit 5 `@Tag`: `io.quarkus.test.junit.QuarkusTest`.
+To alleviate this restriction, the `@QuarkusTest` annotation defines a JUnit `@Tag`: `io.quarkus.test.junit.QuarkusTest`.
 You can use this tag to isolate the `@QuarkusTest` test in a specific execution run, for example with the Maven Surefire Plugin:
 
 [source,xml]
@@ -1699,7 +1699,7 @@ public @interface QuarkusSecurityTest {   <1>
 == Testing Components
 
 Quarkus provides the `QuarkusComponentTestExtension`, a JUnit extension to ease the testing of components and mocking of their dependencies.
-This JUnit extension is available in the `quarkus-junit5-component` dependency.
+This JUnit extension is available in the `quarkus-junit-component` dependency.
 
 Let's have a component `Foo` - a CDI bean with two injection points.
 

_versions/main/guides/getting-started.adoc

@@ -313,7 +313,7 @@ In the generated build file, you can see 2 test dependencies:
 ----
 <dependency>
     <groupId>io.quarkus</groupId>
-    <artifactId>quarkus-junit5</artifactId>
+    <artifactId>quarkus-junit</artifactId>
     <scope>test</scope>
 </dependency>
 <dependency>
@@ -326,13 +326,13 @@ In the generated build file, you can see 2 test dependencies:
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-testImplementation("io.quarkus:quarkus-junit5")
+testImplementation("io.quarkus:quarkus-junit")
 testImplementation("io.rest-assured:rest-assured")
 ----
 
-Quarkus supports https://junit.org/junit5/[JUnit 5] tests.
+Quarkus supports https://docs.junit.org/current/user-guide/[JUnit] tests.
 
-Because of this, in the case of Maven, the version of the https://maven.apache.org/surefire/maven-surefire-plugin/[Surefire Maven Plugin] must be set, as the default version does not support JUnit 5:
+Because of this, in the case of Maven, the version of the https://maven.apache.org/surefire/maven-surefire-plugin/[Surefire Maven Plugin] must be set, as the default version does not support JUnit:
 
 [source,xml,subs=attributes+]
 ----

_versions/main/guides/hibernate-orm-panache.adoc

@@ -1327,14 +1327,14 @@ public class PanacheMockingTest {
 
 === Using the repository pattern
 
-If you are using the repository pattern you can use Mockito directly, using the `quarkus-junit5-mockito` module,
+If you are using the repository pattern you can use Mockito directly, using the `quarkus-junit-mockito` module,
 which makes mocking beans much easier:
 
 [source,xml]
 ----
 <dependency>
     <groupId>io.quarkus</groupId>
-    <artifactId>quarkus-junit5-mockito</artifactId>
+    <artifactId>quarkus-junit-mockito</artifactId>
     <scope>test</scope>
 </dependency>
 ----

_versions/main/guides/hibernate-orm.adoc

@@ -1949,6 +1949,96 @@ Please refer to the corresponding https://hibernate.org/repositories/[Hibernate
 and https://jakarta.ee/specifications/data/1.0/jakarta-data-1.0[Jakarta Data]
 guides to learn what else they have to offer.
 
+==== Secure Jakarta Data repositories
+
+Quarkus Security provides an initial support for securing Jakarta Data Repositories with security annotations.
+
+.Example Jakarta Data repository with method-level security annotation
+[source,java]
+----
+@Repository
+public interface MyRepository extends CrudRepository<MyEntity, Integer> {
+
+    @RolesAllowed("admin")
+    @Delete
+    void delete(String name);
+
+}
+----
+
+.Example Jakarta Data repository with class-level security annotation
+[source,java]
+----
+@Authenticated
+@Repository
+public interface MyRepository extends CrudRepository<MyEntity, Integer> {
+
+    @Delete
+    void delete(String name);
+
+}
+----
+
+[WARNING]
+====
+In the example above, only methods directly declared on the `MyRepository` interface are secured.
+Methods inherited from `CrudRepository`, such as `insert`, are not secured because type-level annotations only affect the type they annotate.
+====
+
+[IMPORTANT]
+====
+Currently, generic interface methods using type variables or wildcards cannot be secured reliably with standard security annotations.
+Therefore, you must not attempt to secure such methods and instead use two alternatives described below.
+
+.Example repository with a generic method using a type variable
+[source,java]
+----
+public interface MyParentRepository<T extends MyEntity> {
+
+    @Find
+    Stream<T> findAll(Order<T> order);
+
+}
+
+@Repository
+public interface MyRepository extends MyParentRepository<MyEntity> {
+}
+----
+
+Alternative 1: Apply a security annotation to the calling method in your REST layer:
+
+[source,java]
+----
+@Path("my-entity")
+public class MyEntityResource {
+
+    @Inject
+    MyRepository myRepository;
+
+    @PermissionsAllowed("find-all")
+    @GET
+    public List<MyEntity> findAll() {
+        return myRepository.findAll(Order.by(Sort.asc(MyEntity_.NAME))).toList();
+    }
+
+}
+----
+
+Alternative 2: Replace the type variable `T` with a concrete type in the repository interface:
+
+[source,java]
+----
+@Repository
+public interface MyRepository {
+
+    @PermissionsAllowed("find-all")
+    @Find
+    Stream<MyEntity> findAll(Order<MyEntity> order);
+
+}
+----
+====
+
 [[configuration-reference]]
 == Configuration Reference for Hibernate ORM
 

_versions/main/guides/hibernate-reactive-panache.adoc

@@ -1060,23 +1060,23 @@ what mock object to pass.
 
 === Using the repository pattern
 
-If you are using the repository pattern you can use Mockito directly, using the `quarkus-junit5-mockito` module,
+If you are using the repository pattern you can use Mockito directly, using the `quarkus-junit-mockito` module,
 which makes mocking beans much easier:
 
 [source,xml,role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
 .pom.xml
 ----
 <dependency>
     <groupId>io.quarkus</groupId>
-    <artifactId>quarkus-junit5-mockito</artifactId>
+    <artifactId>quarkus-junit-mockito</artifactId>
     <scope>test</scope>
 </dependency>
 ----
 
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-testImplementation("io.quarkus:quarkus-junit5-mockito")
+testImplementation("io.quarkus:quarkus-junit-mockito")
 ----
 
 Given this simple entity:

_versions/main/guides/jreleaser.adoc

@@ -668,7 +668,7 @@ As a reference, these are the full contents of the `pom.xml`:
     </dependency>
     <dependency>
       <groupId>io.quarkus</groupId>
-      <artifactId>quarkus-junit5</artifactId>
+      <artifactId>quarkus-junit</artifactId>
       <scope>test</scope>
     </dependency>
   </dependencies>