On Thu, 2 Oct 2025 18:31:00 GMT, Kevin Rushforth <[email protected]> wrote:
>> JUnit 6.0.0 and 6.1.0 and 6.1.3 is out and we can consider updating to it. >> >> Release Notes: >> https://docs.junit.org/current/release-notes/index.html#release-notes-6.0.0 >> >> Notes: >> - Java 17 is the baseline (so not a problem for us, since we have a higher >> baseline) >> - Deprecation were removed (not a problem, as we don't rely on any) >> - JUnit Vintage Engine is deprecated (not a problem, as we dropped support >> for it a year ago -> JUnit 4) >> >> JUnit 6 now uses a single version number for all dependencies, that is >> platform, jupiter and vintage (which we do not use anymore). That makes >> updating it easier. >> >> Junit 6.1 adds 2 more exciting features we can use: >> - `@DefaultLocale` >> - `@DefaultTimeZone` >> >> Both for changing the specific functionality just for the tests and change >> back to the previous value after. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > I also don't see the hurry. Absent a compelling reason to update, we can wait > for a while. > This change will need to get backported to all the releases we currently > support @kevinrushforth , otherwise it's a paint to go back and forth. I don't think this is required. (But might help if we use some of the new features.) > Please add .classpath changes. @hjohn or @nlisker please take a look since > you guys use eclipse. Isn't there any way that Eclipse can derive the configuration from Gradle, like IntelliJ does? I'm always confused by all the files that Eclipse generates and are checked into the VCS. So, is there a better way to do that? For reference, in the JDK source code, there seem to be no Eclipse files at all. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1925#issuecomment-5704782423
