Daniel Kraus

Here's an example for GitHub's native generator, which I set up for the [gluonfx-maven-plugin](https://github.com/gluonhq/gluonfx-maven-plugin): * Configuration: https://github.com/gluonhq/gluonfx-maven-plugin/blob/master/.github/release.yml * Generated changelog: https://github.com/gluonhq/gluonfx-maven-plugin/releases/tag/1.0.13

I did use ["Keep a Changelog"](https://keepachangelog.com/de/1.0.0/) in some other projects and we (me and my teammates) often forgot to update the `CHANGELOG.md`. It also caused merge conflicts sometimes. I _believe_...

@nipafx I don't think I will find time soon. I will remove it from the milestone, so it doesn't block our progress towards 2.0.

Hmmm, I thought we want to avoid this (https://github.com/junit-pioneer/junit-pioneer/issues/623#issuecomment-1098911367): >If at all possible, I'd like to avoid an option because it makes the user choose. And have settled on (https://github.com/junit-pioneer/junit-pioneer/issues/623#issuecomment-1099404175):...

>I don't think it makes the user choose? By default it's always test-scoped with an optional configuration option to make it class scoped. "configuration option", read it again, slowly. 😬...

There is now an IntelliJ IDEA plugin to run Spotless: * https://github.com/diffplug/spotless/issues/200#issuecomment-1003646129 * https://github.com/ragurney/spotless-intellij-gradle

Just thinking out loud: another approach could be inspired by dynamic tests. Consider the example from the [JUnit 5 user guide](https://junit.org/junit5/docs/current/user-guide/#writing-tests-dynamic-tests): ```java @TestFactory Collection dynamicTestsFromCollection() { return Arrays.asList( dynamicTest("1st dynamic...

Had a closer look and I believe it's not a good idea to reuse dynamic tests, because, for instance, "[l]ifecycle callbacks and extensions are not applied around the invocation of...

@filiphr hmmm, not sure about that: * [Adoptium](https://dash.adoptium.net/): Java 11 6,570,025 vs. Java 17 4,742,938 (GitHub) Downloads. * [InfoWorld](https://infoworld.com/article/3652408/java-8-still-dominates-but-java-17-wave-is-coming-survey.html): "[…] 37% of respondents in the Perforce-sponsored survey answered Java 8....

> I don't see the use-case for this. You should always control your input to your tests which means no randomizing. Actually, random testing is quite a big thing. Be...