corda/gradle.properties

kotlin.incremental=true
org.gradle.jvmargs=-Xmx6g -Dfile.encoding=UTF-8'
org.gradle.caching=false
owasp.failOnError=false
owasp.failBuildOnCVSS=11.0
compilation.allWarningsAsErrors=false
test.parallel=false
kotlin_version=1.9.20
commons_lang3_version=3.12.0
json_api_version=1.1.4
cordaProductVersion=4.12
Enable Kotlin incremental compilation in Gradle 2017-01-06 13:36:16 +00:00			`kotlin.incremental=true`
ENT-11065: Remove the need for JVM flags in client code (#7635) 2024-01-03 11:22:03 +00:00			`org.gradle.jvmargs=-Xmx6g -Dfile.encoding=UTF-8'`
BUILD: Resolve warnings with Gradle and system property API usage. (#4904) 2019-03-20 13:39:51 +00:00			`org.gradle.caching=false`
ENT-2684 Fix owasp dependency checker to fail builds based on CVSS level (#4169) OWASP Dependency Checker has been updated so that it can be configured to automatically fail a build when a vulnerable dependency is detected. This option is exposed through gradle settings, so that a build can be configured in TeamCity to pass/fail. This change is backward-compatible - i.e. it does not affect a build by default unless configured to do so. Ability to fail a build is exposed by the new owasp.failBuildOnCVSS gradle property By default this is set to '11.0' which will always pass a build even if a vulnerability is found (so will not affect anything by default) Reduce the CVSS level between 0-10 to indicate what level to fail a build on Example usage to catch Medium severity (and above) issues: Configure gradle with the option -Powasp.failBuildOnCVSS=4 2018-11-07 09:00:19 +00:00			`owasp.failOnError=false`
			`owasp.failBuildOnCVSS=11.0`
BUILD: Resolve warnings with Gradle and system property API usage. (#4904) 2019-03-20 13:39:51 +00:00			`compilation.allWarningsAsErrors=false`
			`test.parallel=false`
ENT-11251: Upgrade to Kotlin language version 1.9 (#7660) 2024-01-25 13:51:19 +00:00			`kotlin_version=1.9.20`
Upgrade to gradle 7.6, kotlin 1.8 and jdk 17 Major changes due to JDK 17: 1. JDK17 JCE Provider now has built-in support for eddsas, corda uses the bouncycastle (i2p) implementation. This PR removes the conflicting algorithms from the built-in JCE provider. 2. JavaScript scripting has been removed from the JDK, the corda log4j config was using scripting to conditionally output additional diagnostic info if the MDC was populated. This PR has removed the scripting. 3. The artifactory plug-ins used are now deprecated, this PR has removed them and uses the same code as Corda 5 for publishing to artifactory. 4. Javadoc generation has been modified to use the latest dokka plug-ins. 5. Gradle 7.6 has implemented an incredibly annoying change where transitive dependencies are not put on the compile classpath, so that they have to be explicitly added as dependencies to projects. 6. Mockito has been updated, which sadly meant that quite a few source files have to changes to use the new (org.mockito.kotlin) package name. This makes this PR appear much larger than it is. 7. A number of tests have been marked as ignored to get a green, broadly they fall into 3 classes. The first is related to crypto keypair tests, it appears some logic in the JDK prefers to use the SunJCE implementation and we prefer to use bouncycastle. I believe this issue can be fixed with better test setup. The second group is related to our use of a method called "uncheckedCast(..)", the purpose of this method was to get rid of the annoying unchecked cast compiler warning that would otherwise exist. It looks like the Kotlin 1.9 compiler type inference differs and at runtime sometimes the type it infers is "Void" which causes an exception at runtime. The simplest solution is to use an explicit cast instead of unchecked cast, Corda 5 have removed unchecked cast from their codebase. The third class are a number of ActiveMQ tests which appear to have a memory leak somewhere. 2023-03-08 12:19:05 +00:00			`commons_lang3_version=3.12.0`
			`json_api_version=1.1.4`
added new api-scanner 2024-06-13 18:44:31 +00:00			`cordaProductVersion=4.12`