You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
# Changelog
2
+
3
+
Notable changes in each release are documented on the project's [GitHub releases](https://github.com/hyperledger/fabric-chaincode-java/releases) page. Change history from previous releases is retained below.
Copy file name to clipboardExpand all lines: COMPATIBILITY.md
+14-15
Original file line number
Diff line number
Diff line change
@@ -16,54 +16,53 @@ This table shows the summary of the compatibility of the Java libraries, togethe
16
16
17
17
18
18
Testing is performed with
19
-
- Java v8: Openjdk version 1.8.0_222
20
-
- Java v11: Eclipse Temurin 11.0.16.1_1-jdk (this has changed from Openjdk version 11.04_11)
19
+
- Java v8: OpenJDK
20
+
- Java v11: Eclipse Temurin (this has changed from OpenJDK)
21
21
22
22
23
23
By default a Fabric Peer v1.4 will create a Java 8 VM, and a Fabric Peer v2.x will create a Java 11 VM. Whilst is the default, the docker image used to host the chaincode and contracts can be altered. Set the environment variable `CORE_CHAINCODE_JAVA_RUNTIME` on the peer to the name of the docker image. For example `CORE_CHAINCODE_JAVA_RUNTIME=example/customJavaRuntime:latest`
24
24
25
-
The Java Libraries will connect to the peer whilst running; this is referred to as 'Fabric Peer Connectivity' in the table. For example, whilst the Fabric Peer v1.4 will create a Java 8 environment, if a Java 11 environment was configured, the Java Libraries at v2.5.0 still function when connecting to the Fabric Peer v1.4.
25
+
The Java Libraries will connect to the peer whilst running; this is referred to as 'Fabric Peer Connectivity' in the table. For example, whilst the Fabric Peer v1.4 will create a Java 8 environment, if a Java 11 environment was configured, the Java Libraries at v2.5 still function when connecting to the Fabric Peer v1.4.
26
26
27
27
## Compatibility
28
28
29
-
The key elements are :
29
+
The key elements are:
30
30
31
31
- the version of the Fabric Contract Java libraries used
32
32
- the version of the JVM used to run the code
33
33
- When starting a chaincode container to run a Smart Contract the version of the runtime that is used is determined by these factors:
34
34
35
-
Fabric v1.4.2, and Fabric v2.5.0 will, by default, start up docker image to host the chaincode and contracts. The version of the docker image used is defined by the version of Fabric in use.
35
+
Fabric v1.4.2, and Fabric v2.5.x will, by default, start up docker image to host the chaincode and contracts. The version of the docker image used is defined by the version of Fabric in use.
36
36
37
37
With Fabric v2.1.0 and later, the chaincode container can be configured to be started by different chaincode builders, and not the Peer. In this case, the environment used is not in the control of Fabric.
38
38
39
39
The Java libraries are produced are `group: 'org.hyperledger.fabric-chaincode-java', name: 'fabric-chaincode-shim'`
40
40
41
41
### Supported JVMs
42
42
43
-
v1.4.x and v2.5.0 Java Libraries are supported running inJava 11with thex86_64architecture. Later Java 11 versions are supported but are not tested.
43
+
v1.4.x and v2.5.x Java Libraries are supported running inJava 11with thex86_64architecture. Later Java 11 versions are supported but are not tested.
44
44
45
-
v1.4.x Java Libraries are supported running inJava 8with thex86_64architecture.Later Java 8 versions are supported but are not tested.
45
+
v1.4.x Java Libraries are supported running inJava 8with thex86_64architecture.Later Java 8 versions are supported but are not tested.
46
46
47
-
Architecture Support: all docker images, JVMs, tools are tested underx86_64 ONLY
47
+
Architecture Support: all docker images, JVMs, tools are tested underx86_64 ONLY
48
48
49
49
50
+
### Default Peer Runtime selection
50
51
51
-
### Default Peer Runtime selection
52
+
When using Fabric v2.5, the default docker image that is used to run the Java chaincode is *eclipse-temurin:11.0.21_9-jdk*
52
53
53
-
When using Fabric 2.5.0, the default docker image that is used to run the Java chaincode is *eclipse-temurin:11.0.16.1_1-jdk*
54
-
55
-
With the default docker image used by Fabric 2.5.0, if the packaged Java code contains a build script or a wrapper for either Maven or Gradle, it will be built using Gradle 7.0 wrapper , or Maven 3.8.1 wrapper.
54
+
With the default docker image used by Fabric v2.5, if the packaged Java code contains a build script or a wrapper for either Maven or Gradle, it will be built using Gradle 7.0 wrapper, or Maven 3.8.1 wrapper.
56
55
57
56
- If both Gradle and Maven files are present Gradle is used.
58
57
- Gradle build files can be groovy, or kotlin.
59
58
- If the Gradle or Maven wrappers are present, this will used in preference to the installed wrappers.
60
59
61
-
Remeber that when using the wrappers, code will be downloaded from the internet. Keep this in mind for any installation with limited or no internet access.
60
+
Remember that when using the wrappers, code will be downloaded from the internet. Keep this in mind for any installation with limited or no internet access.
62
61
63
62
Alternatively it is recommended to package prebuilt jar files, including the contract and all dependencies, in which case no build or Internet access is required when installing Java chaincode.
64
63
65
64
Please check the [Dockerfile](./fabric-chaincode-docker/Dockerfile) that is used for the environment to see exactly how these versions are installed.
66
65
67
66
### Supported Runtime communication with the Peer
68
-
69
-
Subject to a suitable runtime environment, the 1.4 and 2.5 Java Libraries can used to communicate with Fabric Peers at 2.5 and previous LTS versions. The level of functionality that is implied by the Fabric version in use and channel capabilities.
67
+
68
+
Subject to a suitable runtime environment, the 1.4 and 2.5 Java Libraries can used to communicate with Fabric Peers at 2.5 and previous LTS versions. The level of functionality that is implied by the Fabric version in use and channel capabilities.
Copy file name to clipboardExpand all lines: RELEASING.md
-4
Original file line number
Diff line number
Diff line change
@@ -18,10 +18,6 @@ The following tasks are required before releasing:
18
18
- Update version numbers in `build.gradle` files to the required version
19
19
- Update test, sample, and docs files to match the new version
20
20
- Update the [`COMPATIBILITY.md`](./COMPATIBILITY.md)
21
-
- Create a new release notes file
22
-
- Update the [`CHANGELOG.md`](./CHANGELOG.md) file
23
-
24
-
The `changelog.sh` script in `scripts` will prepopulate the changelog but you must check and edit the file manually afterwards as required
25
21
26
22
See the [[FABCJ-289] release: 2.2.0 LTS](https://github.com/hyperledger/fabric-chaincode-java/pull/124) pull request for an example, although be careful to search for all versions in the codebase as they're easy to miss and things change!
0 commit comments