JUnit 6 update strategy

Guillaume Smet

unread,

Dec 2, 2025, 7:23:38 AM (2 days ago) Dec 2

to Quarkus Development mailing list

Hi,

It seems we more or less all agree we should proceed with the JUnit 6 update.

I would like to suggest the following strategy:

- Rename all artifacts that are named with junit5 -> junit-jupiter

- Put relocations in place

- Update to JUnit 6

- Fix our tests if needed, there might be some usage of CSV parameterized tests that might need fixing

- Write recipes to update projects to the new artifacts

I think people will be able to use JUnit 5 by overriding the BOM if they actually need to.

There's also the question of when: we won't have a December release, then we will have 3.31 at the end of January, then 3.32 at the end of February with the feature freeze for 3.33 LTS released at the end of March.

So I would say: either we do it now or we wait for after the 3.32 feature freeze.

We probably need a broader discussion with the ecosystem before deciding.

--

Guillaume

Guillaume Smet

unread,

Dec 2, 2025, 7:25:00 AM (2 days ago) Dec 2

to Quarkus Development mailing list

BTW one advantage of doing it now is that the ecosystem will have more time to adjust before we release 3.31 at the end of January.

--

Guillaume

Georgios Andrianakis

unread,

Dec 2, 2025, 7:29:01 AM (2 days ago) Dec 2

to quark...@googlegroups.com

+1

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo-a%2B38GNki0ZYjfPuvyL-55x_Y9de8ifuG3zwR95n_mDA%40mail.gmail.com.