Mocking final classes with Java8 when compiling with -parameters flag

I gave the new final class mocking feature a spin by configuring mock-maker-inline in the appropriate place, and by and large it does what it says on the tin: mocking of final classes does work indeed. Awesome!

But I found there’s one unintended side-effect: constructor parameters as retained when compiling with Java 8’s -parameters flag are lost. (We rely on this feature because we use jackson-module-parameter-names.)

The following TestNG test illustrates the issue. Note that test1, test2 and test3 are executed sequentially, in that order. Note also that test1 and test3 are identical. When this class is compiled with -parameters and when mock-maker-inline is enabled, then the first two tests pass (as they should), while the third fails.

import static org.mockito.Mockito.mock;
import static org.testng.Assert.assertEquals;

import org.testng.annotations.Test;

public final class Test {
    static final class Dummy {
        public Dummy(final String dummyArg) {}
    }

    // Passes, because we compile with `-parameters`.
    @Test
    public void test1() throws NoSuchMethodException {
        final String param = Dummy.class.getConstructor(String.class).getParameters()[0].getName();
        assertEquals(param, "dummyArg");
    }

    // Passes, because we have configured `mock-maker-inline`.
    @Test(dependsOnMethods = "test1")
    public void test2() {
        @SuppressWarnings("unused")
        final Dummy d = mock(Dummy.class);
    }

    // Fails, because parameter names got lost.
    @Test(dependsOnMethods = "test2")
    public void test3() throws NoSuchMethodException {
        final String param = Dummy.class.getConstructor(String.class).getParameters()[0].getName();
        assertEquals(param, "dummyArg");
    }
}

[raphw]

PS: You can already use the new version, it is released as 2.2.4.

[raphw]

I reported it but those bugs are only filed when they pass QA. I will add the ticket once I receive a confirmation.