Roland Weisleder

It looks like it wasn't a good idea to use `baseProducer` here... How should we handle this?

Okay, I updated the tests with the newly generated data. The build is now green.

FYI, I created a small proof of concept: [rweisleder/jfairy-junit-extension](https://github.com/rweisleder/jfairy-junit-extension)

The issue https://github.com/diffplug/spotless/issues/540 is fixed with Spotless 6.2.1. So this issue should be fixed by merging #782. (or a follow-up PR if dependabot is faster)

A short and unsorted collection of my thoughts… The example ```java noClasses() .that(not(name(Bar1.class.getName())) .and(not(name(Bar2.class.getName())))) ``` gives me a headache because of the double negation. Maybe we should introduce a `onlyClasses()`...

> For me it is always difficult to find the static methods which I have to import. For example, what I like about jOOQ is that there is a single...

Sealed classes will be part of Java 17, see [JEP 409](https://openjdk.java.net/jeps/409).

The essence of this issue is that in the test code the following construct is used: ```java ProcessScenario scenario = mock(ProcessScenario.class); ProcessScenario subScenario = mock(ProcessScenario.class); when(scenario.runsCallActivity("CallWork")).thenReturn(Scenario.use(subScenario)); ``` This means that...

[Related thread on Stack Overflow](https://stackoverflow.com/q/76384057) with a possible answer

This looks like a bug in `JavaPackage.getClasses()`, because the method returns the type and the corresponding array type. ```java class GH1233 { @Test void test() { JavaClass javaClass = new...