[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710278#comment-16710278 ]
Rick Hillegas commented on DERBY-7011: -------------------------------------- I ran both modulepath test targets on a Windows 10 laptop using Java 11. The test-derbyall-with-modulepath target ran successfully. I saw 6 errors when running the test-junit-all-with-modulepath target: * The 2 expected ssl handshake errors which occur on Java 11 (see https://bugs.openjdk.java.net/browse/JDK-8211426 and https://issues.apache.org/jira/browse/DERBY-6998). * 2 unexpected errors in SystemPrivilegesPermissionTest. I will investigate. * 2 unexpected errors in the upgrade suite when upgrading from 10.14.2.0 to 10.15. I will investigate. > Set up a new Jenkins job to run the JUnit tests with a module path > ------------------------------------------------------------------ > > Key: DERBY-7011 > URL: https://issues.apache.org/jira/browse/DERBY-7011 > Project: Derby > Issue Type: Task > Components: Build tools > Affects Versions: 10.15.0.0 > Reporter: Rick Hillegas > Priority: Major > Attachments: derby-7011-01-aa-shortCircuitAfterDerbyNetSuite.diff, > derby-7011-02-aa-shortCircuitAfterLangSuite.diff > > > I have set up a new Jenkins job (Derby-trunk-test-junit-all-with-modulepath) > to run the JUnit tests with a module path. This issue is a place to collect > feedback on how to finish setting up this job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)