nrknithin opened a new pull request, #7087:
URL: https://github.com/apache/incubator-kie/pull/7087

   Renames every Quarkus JUnit test-support dependency to the coordinates 
introduced in Quarkus 3.31.0:
   
   | Old artifactId | New artifactId | Occurrences |
   |---|---|---|
   | `quarkus-junit5` | `quarkus-junit` | 120 |
   | `quarkus-junit5-internal` | `quarkus-junit-internal` | 27 |
   | `quarkus-junit5-mockito` | `quarkus-junit-mockito` | 20 |
   
   167 replacements across 142 `pom.xml` files. All are `groupId: io.quarkus`.
   
   ## Why
   
   Quarkus renamed these artifacts in **3.31.0** — the `5` was dropped from the 
names because they are no
   longer tied to a single JUnit major version. This repository builds against 
**Quarkus 3.33.3.2**
   (`version.io.quarkus` in `kie-quarkus-build-parent` and 
`optaplanner-build-parent`), so it is past that
   rename and is currently resolving the old coordinates through relocation 
stubs.
   
   The old coordinates still publish, but only as relocation POMs:
   
   ```xml
   <!-- io/quarkus/quarkus-junit5/3.33.3/quarkus-junit5-3.33.3.pom -->
   <name>Quarkus - Relocations - quarkus-junit5</name>
   <distributionManagement>
     <relocation>
       <artifactId>quarkus-junit</artifactId>
       <message>Update the artifactId in your project build file. Refer to
                https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.31 
for more information.</message>
     </relocation>
   </distributionManagement>
   ```
   
   Depending on relocations means every module logs a relocation warning during 
resolution, and the build
   stays exposed to the stubs being dropped in a future Quarkus release. This 
change moves to the real
   coordinates as the migration guide instructs.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to