Running assertj generator on JDK 11

I am trying to build a library with OpenJDK 11 with the maven-assertj-generator plugin enabled. However, the plugin succeeds, but generates non-compiling code.

Has anyone had any succes on running the assertj-generator with OpenJDK 11?

Generated code:

/**
   * Verifies that the actual Melding's referenties contains the given interface Referentie elements.
   * @param referenties the given elements that should be contained in actual Melding's referenties.
   * @return this assertion object.
   * @throws AssertionError if the actual Melding's referenties does not contain all given interface Referentie elements.
   */
  public MeldingAssert hasReferenties(interface Referentie... referenties) {
    // check that actual Melding we want to make assertions on is not null.
    isNotNull();

    // check that given interface Referentie varargs is not null.
    if (referenties == null) failWithMessage("Expecting referenties parameter not to be null.");

    // check with standard error message, to set another message call: info.overridingErrorMessage("my error message");
    Iterables.instance().assertContains(info, actual.getReferenties(), referenties);

    // return the current assertion for method chaining
    return this;
  }

Wrong line:
public MeldingAssert hasReferenties(interface Referentie... referenties) {
Expected line:
public MeldingAssert hasReferenties(Referentie... referenties) {

To solve the issue, I tried building the assertj-assertions-generator on OpenJDK 11, but I also ran into all kinds of trouble.

• Tried to build a latest version of com.google.testing.compile:compile-testing
• Tried to upgrade Guava
• Needed to upgrade to JDK 8 source code
• Ran into troubles running JUnit Theories

Commencez par reproduire l’exécution de maven-assertj-generator sur OpenJDK 11 en utilisant la méthode générée MeldingAssert.hasReferenties comme point d’entrée en échec. Examinez les contraintes de build de generator, compile-testing et Guava mentionnées dans le rapport, puis exécutez les JUnit Theories pertinentes ; c’est terminé lorsque la méthode générée se compile sans le token d’interface invalide.