[jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path

[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704943#comment-16704943 ] Rick Hillegas commented on DERBY-7011: -- The modulepath junit tests are still failing and they

[jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path

[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705078#comment-16705078 ] Rick Hillegas commented on DERBY-7011: -- Attaching

[jira] [Updated] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path

[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-7011: - Attachment: derby-7011-01-aa-shortCircuitAfterDerbyNetSuite.diff > Set up a new Jenkins job to

[jira] [Resolved] (DERBY-6973) Provide SHA-512 checksums on future releases

[ https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-6973. -- Resolution: Fixed Fix Version/s: 10.15.0.0 I am not inclined to touch the maven

[jira] [Closed] (DERBY-6973) Provide SHA-512 checksums on future releases

[ https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas closed DERBY-6973. > Provide SHA-512 checksums on future releases > > >

[jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path

[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705420#comment-16705420 ] ASF subversion and git services commented on DERBY-7011: Commit 1847862 from

Jenkins build is still unstable: Derby-trunk-suites.All #207

See

Jenkins build is back to normal : Derby-trunk-test-junit-all-with-modulepath #9

See

[jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path

[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705611#comment-16705611 ] Bryan Pendleton commented on DERBY-7011: To make sure I understand: these tests appear to run

[jira] [Commented] (DERBY-6973) Provide SHA-512 checksums on future releases

[ https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705613#comment-16705613 ] Bryan Pendleton commented on DERBY-6973: I agree, we shouldn't mess with the Maven checksums. I

Build failed in Jenkins: Derby-trunk-test-junit-all-with-modulepath #8

See Changes: [rhillegas] DERBY-6980: Add module diagrams for the client and runner modules to the public api; commit derby-6980-15-aa-addClientAndRunnerDiagramsToPublicAPI.diff.

Jenkins build is still unstable: Derby-JaCoCo #331

See