2019-03-07 12:13:18 +00:00
|
|
|
# This file is parsed from Python in the docs/source/conf.py file
|
|
|
|
|
# because some versions here need to be matched by app authors in
|
|
|
|
|
# their own projects. So don't get fancy with syntax!
|
2022-06-22 15:20:03 +00:00
|
|
|
# Fancy syntax - multi pass ${whatever} replacement
|
2019-03-07 12:13:18 +00:00
|
|
|
|
2023-09-14 10:13:15 +00:00
|
|
|
cordaVersion=4.12
|
2019-12-11 17:50:27 +00:00
|
|
|
versionSuffix=SNAPSHOT
|
2024-03-05 19:40:14 +00:00
|
|
|
cordaShellVersion=4.12-SNAPSHOT
|
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
|
|
|
gradlePluginsVersion=5.1.1
|
|
|
|
|
artifactoryContextUrl=https://software.r3.com/artifactory
|
|
|
|
|
internalPublishVersion=1.+
|
2018-10-05 08:28:00 +00:00
|
|
|
# ***************************************************************#
|
|
|
|
|
# When incrementing platformVersion make sure to update #
|
|
|
|
|
# net.corda.core.internal.CordaUtilsKt.PLATFORM_VERSION as well. #
|
|
|
|
|
# ***************************************************************#
|
2024-03-04 12:24:15 +00:00
|
|
|
platformVersion=140
|
2022-12-08 16:54:38 +00:00
|
|
|
openTelemetryVersion=1.20.1
|
|
|
|
|
openTelemetrySemConvVersion=1.20.1-alpha
|
2019-06-20 15:19:16 +00:00
|
|
|
guavaVersion=28.0-jre
|
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
|
|
|
quasarVersion=0.9.0_r3
|
2020-11-20 10:21:53 +00:00
|
|
|
dockerJavaVersion=3.2.5
|
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
|
|
|
proguardVersion=7.3.1
|
ENT-11101: Fix all crypto issues introduced by Java 17 upgrade
The various crypto tests that were previously ignored have been re-enabled.
The abandoned i2p EdDSA library has been replaced with native support that was added in Java 15.
Java 17 (via the `SunEC` provider) does not support the secp256k1 curve (one of the two ECDSA curves supported in Corda). This would not normally have been an issue as secp256k1 is already taken care of by Bouncy Castle. However, this only works if the `Crypto` API is used or if `”BC”` is explicitly specified as the provider (e.g. `Signature.getInstance(“SHA256withECDSA”, “BC”)`). If no provider is specified, which is what is more common, and actually what the Java docs recommend, then this doesn’t work as the `SunEC` provider is selected. To resolve this, a custom provider was created, installed just in front of `SunEC`, which “augments” `SunEC` by delegating to Bouncy Castle if keys or parameters for secp256k1 are encountered.
`X509Utilities.createCertificate` now calls `X509Certificate.verify()` to verify the created certificate, rather than using the Bouncy Castle API. This is more representative of how certificates will be verified (e.g. during SSL handshake) and weeds out other issues (such as unsupported curve error for secp256k1).
`BCCryptoService` has been renamed to `DefaultCryptoService` as it no longer explicitly uses Bouncy Castle but rather uses the installed security providers. This was done to fix a failing test. Further, `BCCryptoService` was already relying on the installed providers in some places.
The hack to get Corda `SecureRandom` working was also resolved. Also, as an added bonus, tests which ignored `SPHINCS256_SHA256` have been reinstated.
Note, there is a slightly inconsistency between how EdDSA and ECDSA keys are handled (and also RSA). For the later, Bouncy Castle is preferred, and methods such as `toSupportedKey*` will convert any JDK class to Bouncy Castle. For EdDSA the preference is the JDK (`SunEC`). However, this is simply a continuation of the previous preference of the i2p library over Bouncy Castle.
2024-02-29 14:46:27 +00:00
|
|
|
# Bouncy Castle version must not be changed on a patch release. Needs a full release test cycle to flush out any issues.
|
2023-07-31 09:42:28 +00:00
|
|
|
bouncycastleVersion=1.75
|
2021-11-23 09:43:41 +00:00
|
|
|
classgraphVersion=4.8.135
|
2018-10-02 09:33:17 +00:00
|
|
|
disruptorVersion=3.4.2
|
2019-06-20 15:19:16 +00:00
|
|
|
typesafeConfigVersion=1.3.4
|
2017-11-23 22:27:24 +00:00
|
|
|
jsr305Version=3.0.2
|
2020-07-15 09:46:29 +00:00
|
|
|
artifactoryPluginVersion=4.16.1
|
2023-04-06 18:14:30 +00:00
|
|
|
snakeYamlVersion=1.33
|
2022-05-16 17:16:54 +00:00
|
|
|
caffeineVersion=2.9.3
|
2019-06-20 15:19:16 +00:00
|
|
|
metricsVersion=4.1.0
|
2018-08-09 17:17:20 +00:00
|
|
|
metricsNewRelicVersion=1.1.1
|
2019-11-14 10:40:12 +00:00
|
|
|
openSourceBranch=https://github.com/corda/corda/blob/release/os/4.4
|
2019-08-07 13:23:33 +00:00
|
|
|
openSourceSamplesBranch=https://github.com/corda/samples/blob/release-V4
|
2019-10-14 09:08:01 +00:00
|
|
|
jolokiaAgentVersion=1.6.1
|
2020-02-14 17:31:02 +00:00
|
|
|
detektVersion=1.0.1
|
2022-02-16 18:10:05 +00:00
|
|
|
tcnativeVersion=2.0.48.Final
|
2022-08-01 12:00:57 +00:00
|
|
|
commonsConfiguration2Version=2.8.0
|
2022-10-17 16:44:32 +00:00
|
|
|
commonsTextVersion=1.10.0
|
2022-02-22 18:09:30 +00:00
|
|
|
|
|
|
|
|
# ENT-6607 all third party version in here now
|
|
|
|
|
|
|
|
|
|
# gradle-capsule-plugin:1.0.2 contains capsule:1.0.1 by default.
|
|
|
|
|
# We must configure it manually to use the latest capsule version.
|
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
|
|
|
capsuleVersion=1.0.4_r3
|
|
|
|
|
asmVersion=9.5
|
|
|
|
|
artemisVersion=2.29.0
|
2022-02-22 18:09:30 +00:00
|
|
|
# TODO Upgrade Jackson only when corda is using kotlin 1.3.10
|
2023-04-27 16:00:08 +00:00
|
|
|
jacksonVersion=2.13.5
|
2022-04-01 15:58:08 +00:00
|
|
|
jacksonKotlinVersion=2.9.7
|
2023-11-10 15:59:16 +00:00
|
|
|
jettyVersion=9.4.53.v20231009
|
2022-02-22 18:09:30 +00:00
|
|
|
jerseyVersion=2.25
|
|
|
|
|
servletVersion=4.0.1
|
|
|
|
|
assertjVersion=3.12.2
|
|
|
|
|
slf4JVersion=1.7.30
|
2024-03-01 13:53:32 +00:00
|
|
|
log4JVersion=2.23.0
|
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
|
|
|
okhttpVersion=4.11.0
|
2022-10-06 11:33:36 +00:00
|
|
|
nettyVersion=4.1.77.Final
|
2022-02-22 18:09:30 +00:00
|
|
|
fileuploadVersion=1.4
|
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
|
|
|
kryoVersion=5.5.0
|
2022-02-22 18:09:30 +00:00
|
|
|
kryoSerializerVersion=0.43
|
|
|
|
|
# Legacy JUnit 4 version
|
|
|
|
|
junitVersion=4.12
|
|
|
|
|
# Need this version to access classpath scanning error handling fix -
|
|
|
|
|
# see https://github.com/junit-team/junit5/commit/389de48c2a18c5a93a7203ef424aa47a8a835a74
|
|
|
|
|
# Upgrade to 5.5.x when GA release is available.
|
|
|
|
|
junitVintageVersion=5.5.0-RC1
|
|
|
|
|
junitJupiterVersion=5.5.0-RC1
|
|
|
|
|
junitPlatformVersion=1.5.0-RC1
|
2023-12-07 10:46:56 +00:00
|
|
|
mockitoVersion=5.5.0
|
2024-01-03 18:28:16 +00:00
|
|
|
mockitoKotlinVersion=5.2.1
|
2022-02-22 18:09:30 +00:00
|
|
|
hamkrestVersion=1.7.0.0
|
|
|
|
|
joptSimpleVersion=5.0.2
|
|
|
|
|
jansiVersion=1.18
|
2023-07-07 12:29:35 +00:00
|
|
|
hibernateVersion=5.6.14.Final
|
2022-02-22 18:09:30 +00:00
|
|
|
# h2Version - Update docs if renamed or removed.
|
2023-11-03 13:44:49 +00:00
|
|
|
h2Version=2.2.224
|
2022-02-22 18:09:30 +00:00
|
|
|
rxjavaVersion=1.3.8
|
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
|
|
|
dokkaVersion=1.8.20
|
2022-02-22 18:09:30 +00:00
|
|
|
dependencyCheckerVersion=5.2.0
|
|
|
|
|
commonsCollectionsVersion=4.3
|
|
|
|
|
beanutilsVersion=1.9.4
|
2022-10-17 16:44:32 +00:00
|
|
|
shiroVersion=1.10.0
|
2022-02-22 18:09:30 +00:00
|
|
|
hikariVersion=3.3.1
|
2023-07-07 12:29:35 +00:00
|
|
|
liquibaseVersion=4.20.0
|
2022-02-22 18:09:30 +00:00
|
|
|
dockerComposeRuleVersion=1.5.0
|
|
|
|
|
seleniumVersion=3.141.59
|
|
|
|
|
ghostdriverVersion=2.1.0
|
|
|
|
|
jschVersion=0.1.55
|
|
|
|
|
# Override Artemis version
|
|
|
|
|
protonjVersion=0.33.0
|
|
|
|
|
snappyVersion=0.4
|
|
|
|
|
jcabiManifestsVersion=1.1
|
|
|
|
|
picocliVersion=3.9.6
|
|
|
|
|
commonsIoVersion=2.6
|
|
|
|
|
controlsfxVersion=8.40.15
|
|
|
|
|
fontawesomefxCommonsVersion=11.0
|
|
|
|
|
fontawesomefxFontawesomeVersion=4.7.0-11
|
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
|
|
|
javaassistVersion=3.29.2-GA
|
2024-01-02 17:02:20 +00:00
|
|
|
joorVersion=0.9.15
|
