mirror of
https://github.com/digital-asset/daml.git
synced 2024-11-10 10:46:11 +03:00
157fab963b
Also move Interface and InterfaceType out of the reader subpackage; they belong with the rest of the data model at the iface root. The specific mechanics of reading a Dar all the way to producing an EnvironmentInterface are left to Scala codegen's Codegen and Java codegen's CodeGenRunner; there's no consensus or great stability on the best way to tie these pieces together, but all the pieces might as well be available in the interface library at least. Inspired by a query on Slack by @leonelag regarding reading the codegen-relevant parts of dalfs and dars; thanks! * daml-lf: move EnvironmentInterface to interface library from Scala codegen * daml-lf: move Interface out of reader subpackage * language-support/java: deal with moving Interface out of reader subpackage * document Interface and EnvironmentInterface * missed copyright header in reader package.scala * extractor: deal with moving Interface out of reader subpackage * navigator: deal with moving Interface out of reader subpackage |
||
---|---|---|
.. | ||
bin | ||
src | ||
.gitignore | ||
BUILD.bazel | ||
README.md | ||
UNRELEASED.md |
Extractor
Build
The code uses SBT as a build system
sbt compile
To run the tests
sbt test
Release
- Create a branch
extractor-release-<major>-<minor>-<point>
for the release. Check the file ledger-tools/extractor/version.sbt. For example, let's say the the current version of the project is0.9.3-SNAPSHOT
. You need to create a branch calledextractor-release-0-9-3
; - Move the ## Unreleased section of ledger-tools/extractor/UNRELEASED.md to the new release version you have created in ledger-tools/extractor/CHANGELOG.md and commit to that branch. The message of the commit is not important as it will be discarded;
- Run
sbt release
. This will ask for the release version and the next version, and will create commit with the release version and next version, and also takes care about tagging; - Push your branch and tag:
git push origin release/extractor/0.9.3 # check the tag that has been created, and push it
git push -u origin extractor-release-0-9-3 # push your branch
- Go to the release Jenkins job Enter the tag you published and run the job.
- Create a Pull Request from your branch, have it reviewed and merged. After it's done, you can delete the branch.