Why @Nested classes can't be static?

[vlsi]

I've a case when @ClassRule in a junit4-based test.
Here's the test:

testcontainers-java/modules/localstack/src/test/java/org/testcontainers/containers/localstack/LocalstackContainerTest.java

Line 84 in 63189c8

public static LocalStackContainer localstack = new LocalStackContainer(LocalstackTestImages.LOCALSTACK_IMAGE)

It turns out @Nested must be non-static class, so it forbids usage of static fields, so it effectively forces the users to re-initialized the test containers for every test rather than "once per class".

Note that the container might take long to start, so it would be great to still use @Nested static class.

Am I missing something? Is there a way to restructure the test with JUnit5?

Of course I can move public static LocalStackContainer localstack to a upper level, however:

1. It would look like a global variables and it would be harder to understand which containers are used by which tests
2. The global containers would start for any test, even if a single nested test starts

[vlsi]

The question was for junit community, and I created it in a wrong project by mistake. Moved to junit here: junit-team/junit-framework#4613