-
Ariya Hidayat authored
* Remove -Xverify:none since it has no effect anymore with Java >= 13 https://bugs.openjdk.java.net/browse/JDK-8214731 * Send crash reports to stderr so we can see them in CI probably (?) want to remove this before merging * Revert "Send crash reports to stderr so we can see them in CI" This reverts commit 4c15d94a95ac4a75d8c4886e857d59160cd834fc. * Use deftype not defrecord to prevent invalid bytecode The interface org.quart.JobExecutionContext has a put method on it https://www.quartz-scheduler.org/api/2.1.7/org/quartz/JobExecutionContext.html#put(java.lang.Object,%20java.lang.Object) and defrecord emits a put method as well and we end up with invalid bytecode. https://ask.clojure.org/index.php/9943/defrecord-can-emit-invalid-bytecode the above link will most probably result in a jira issue which would be nice to track here but it doesn't exist yet. Co-authored-by:
dan sutton <dan@dpsutton.com>
Ariya Hidayat authored* Remove -Xverify:none since it has no effect anymore with Java >= 13 https://bugs.openjdk.java.net/browse/JDK-8214731 * Send crash reports to stderr so we can see them in CI probably (?) want to remove this before merging * Revert "Send crash reports to stderr so we can see them in CI" This reverts commit 4c15d94a95ac4a75d8c4886e857d59160cd834fc. * Use deftype not defrecord to prevent invalid bytecode The interface org.quart.JobExecutionContext has a put method on it https://www.quartz-scheduler.org/api/2.1.7/org/quartz/JobExecutionContext.html#put(java.lang.Object,%20java.lang.Object) and defrecord emits a put method as well and we end up with invalid bytecode. https://ask.clojure.org/index.php/9943/defrecord-can-emit-invalid-bytecode the above link will most probably result in a jira issue which would be nice to track here but it doesn't exist yet. Co-authored-by:
dan sutton <dan@dpsutton.com>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.