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
Java chaincode has been failing to build (maven issues probably), also the dependencies specified in gradle are different between the 2 java chaincodes. I am not a fan of Java chaincode for fabric for a variety of reasons. Caliper-benchmarks has 2 java chaincodes
fixed-asset
fabcar
I propose we delete the fabcar java chaincode and tests. We already have go and node and just leave fixed-asset to show performance comparisons of java chaincode vs other chaincode (it performs poorly). But we need to fix the gradle info
Java chaincode has been failing to build (maven issues probably), also the dependencies specified in gradle are different between the 2 java chaincodes. I am not a fan of Java chaincode for fabric for a variety of reasons. Caliper-benchmarks has 2 java chaincodes
I propose we delete the fabcar java chaincode and tests. We already have go and node and just leave fixed-asset to show performance comparisons of java chaincode vs other chaincode (it performs poorly). But we need to fix the gradle info
I think should suffice
Then we can consider re-enabling builds for java
The text was updated successfully, but these errors were encountered: