[GEODE-5859] Java11 testing fails due to String 'code' compiled in test VM

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: tests
• Assignee: Unassigned
• Reporter: Patrick Rhomberg
• Created: 12/Oct/18 16:34
• Updated: 19/Oct/18 20:07
• Resolved: 19/Oct/18 20:07

Description

In several Acceptance and DUnit tests, in particular in tests dealing with deploy jar, we commonly have code blocks like the following:

  private File createJar() throws IOException {
    File jarToDeploy = new File(gfsh.getTemporaryFolder().getRoot(), "ourJar.jar");

    String classContents =
        "import org.apache.geode.cache.util.ObjectSizer; import org.apache.geode.cache.Declarable;public class MySizer implements ObjectSizer, Declarable { public int sizeof(Object o) { return 10; } }";

    JarBuilder jarBuilder = new JarBuilder();
    jarBuilder.buildJar(jarToDeploy, classContents);

    return jarToDeploy;
  }

This causes tests to fail when run in Java11, as code compiled in the Java11 test VM cannot execute on the Java8-compiled server VMs.

Issue Links

• relates to: GEODE-5850 Java11 testing in PutCommandWithJsonTest fails due to String declaration of classes.
• relates to: GEODE-3 Support JDK 9 on Geode

Sub-Tasks

• Extract String code from ConfigureEvictionThroughGfsh: Resolved