NWO: Go chaincode packager needs a new implementation #378
Labels
enhancement
New feature or request
NWO
All about our testing infrastructure
testing
All related to testing
The current NWO chaincode packager currently packages the whole of fabric-smart-client and then relies on fabric to reference the chaincode stored inside the source code tree.
This isn't really optimal and also means that some hardcoded checks are made against the path to address being able to locate the code.
A new implementation should be provided at first to exist along side the current implementation (to allow for easy transition for fabric-token-sdk) that only packages the chaincode itself and is flexible enough to not require hardcoded paths, GOPATH to be set or even a path declared as a module name. It should be either an absolute path that the caller can compute (not hardcoded) to ensure maximum flexibility for fabric-smart-client, fabric-token-sdk and also allow consumers of these toolkits to be able to utilise NWO themselves
The text was updated successfully, but these errors were encountered: