digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 09:17:43 +03:00
Code Issues Projects Releases Wiki Activity
d951d738ee
daml/release/artifacts.yaml

209 lines
6.3 KiB
YAML
Raw Normal View History

Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/data:data
Release missing sources jars (#2683) * Release missing sources jars * Review feedback by Gerolf
2019-08-29 09:21:57 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
daml-lf: repackage daml-lf archive proto (daml_lf -> daml_lf_dev) (#3169)
2019-10-15 12:36:11 +03:00
- target: //daml-lf/archive:daml_lf_dev_archive_java_proto
daml-lf: clean achive bazel build (#3175) * clean the mess in daml-lf achive bazel build * add release note * Address Moritz's comments * more release notes
2019-10-15 11:36:47 +03:00
type: jar-lib
daml-lf: repackage daml-lf archive proto (daml_lf -> daml_lf_dev) (#3169)
2019-10-15 12:36:11 +03:00
javadoc-jar: daml_lf_dev_archive_java_proto_javadoc.jar
daml-lf: clean achive bazel build (#3175) * clean the mess in daml-lf achive bazel build * add release note * Address Moritz's comments * more release notes
2019-10-15 11:36:47 +03:00
mavenUpload: True
daml-lf: repackage daml-lf archive proto (daml_lf -> daml_lf_dev) (#3169)
2019-10-15 12:36:11 +03:00
- target: //daml-lf/archive:daml_lf_dev_archive_proto_zip
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
type: zip
location:
groupId: com.digitalasset
daml-lf: repackage daml-lf archive proto (daml_lf -> daml_lf_dev) (#3169)
2019-10-15 12:36:11 +03:00
artifactId: daml-lf-dev-archive-proto
- target: //daml-lf/archive:daml_lf_dev_archive_proto_tarball
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
type: targz
location:
groupId: com.digitalasset
daml-lf: repackage daml-lf archive proto (daml_lf -> daml_lf_dev) (#3169)
2019-10-15 12:36:11 +03:00
artifactId: daml-lf-dev-archive-proto
daml-lf proto: archive proto for daml-lf 1.6 (#3142) * daml-lf proto: archive proto for daml-lf 1.6 * try to fix archive ProtoTest for windows * more windows fix for archive ProtoTest
2019-10-15 21:35:20 +03:00
- target: //daml-lf/archive:daml_lf_1.6_archive_java_proto
type: jar-lib
javadoc-jar: daml_lf_1.6_archive_java_proto_javadoc.jar
mavenUpload: True
- target: //daml-lf/archive:daml_lf_1.6_archive_proto_zip
type: zip
location:
groupId: com.digitalasset
artifactId: daml-lf-1.6-archive-proto
- target: //daml-lf/archive:daml_lf_1.6_archive_proto_tarball
type: targz
location:
groupId: com.digitalasset
artifactId: daml-lf-1.6-archive-proto
daml-lf: clone dev protobuf for LF 1.7 (#3371)
2019-11-07 15:32:38 +03:00
- target: //daml-lf/archive:daml_lf_1.7_archive_proto_zip
type: zip
location:
groupId: com.digitalasset
artifactId: daml-lf-1.7-archive-proto
- target: //daml-lf/archive:daml_lf_1.7_archive_proto_tarball
type: targz
location:
groupId: com.digitalasset
artifactId: daml-lf-1.7-archive-proto
daml-lf: clean achive bazel build (#3175) * clean the mess in daml-lf achive bazel build * add release note * Address Moritz's comments * more release notes
2019-10-15 11:36:47 +03:00
- target: //daml-lf/archive:daml_lf_archive_reader
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
daml-lf: clean achive bazel build (#3175) * clean the mess in daml-lf achive bazel build * add release note * Address Moritz's comments * more release notes
2019-10-15 11:36:47 +03:00
- target: //compiler/damlc/jar:damlc_jar
type: jar-deploy
platformDependent: True
Fix the import paths of {value,transaction,blindinginfo}.proto (#3312) * Fix the import paths of {value,transaction,blindinginfo}.proto This cleans the imports in daml_kvutils.proto: -import "daml-lf/transaction/src/main/protobuf/transaction.proto"; +import "com/digitalasset/daml/lf/transaction.proto"; This shouldn't be a breaking change to the outside as the proto files themselves are not published, only the java libraries generated from them. * Update missed deps
2019-11-01 17:54:55 +03:00
- target: //daml-lf/transaction:value_java_proto
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
type: jar-proto
Upload proto and deploy jars to maven (#3507) * Add helper to produce an empty zip files. This is used to generate empty sources and javadoc jars for deploy jars later on. * Create empty auxilliary jars. da_java_binary: - empty javadoc jar - empty sources jar da_java_proto_library: - empty javadoc jar - the sources jar is automatically generated by java_proto_library as a side effect da_scala_binary: - empty javadoc jar - empty sources jar * Support maven upload for jar-deploy and jar-proto For jar-deploy targets we don't check for internal dependencies, because these should already be contained in the (fat-)jar itself. Additionally, the release program now uploads javadocs and sources for jar-proto and jar-deploy as well to comply with maven central. * Upload ledger-api-test-tool and kvutils + dependencies to maven central. This is the diff running the output of the release without and with these changes. A few artifacts now also get their javadoc and sources uploaded (mostly to bintray, but now they are ready for a maven central upload). ledger-api-test-tool has the scala version removed from the artifact as it is a deploy jar and nobody should care which specific scala version is used. Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-javadoc.jar Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-sources.jar Only in release/com/daml/ledger/testtool: ledger-api-test-tool Only in release-before/com/daml/ledger/testtool: ledger-api-test-tool_2.12 Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-javadoc.jar Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-javadoc.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-sources.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-javadoc.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-sources.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-javadoc.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-sources.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-javadoc.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-sources.jar
2019-11-18 16:40:15 +03:00
mavenUpload: true
Fix the import paths of {value,transaction,blindinginfo}.proto (#3312) * Fix the import paths of {value,transaction,blindinginfo}.proto This cleans the imports in daml_kvutils.proto: -import "daml-lf/transaction/src/main/protobuf/transaction.proto"; +import "com/digitalasset/daml/lf/transaction.proto"; This shouldn't be a breaking change to the outside as the proto files themselves are not published, only the java libraries generated from them. * Update missed deps
2019-11-01 17:54:55 +03:00
- target: //daml-lf/transaction:transaction_java_proto
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
type: jar-proto
Upload proto and deploy jars to maven (#3507) * Add helper to produce an empty zip files. This is used to generate empty sources and javadoc jars for deploy jars later on. * Create empty auxilliary jars. da_java_binary: - empty javadoc jar - empty sources jar da_java_proto_library: - empty javadoc jar - the sources jar is automatically generated by java_proto_library as a side effect da_scala_binary: - empty javadoc jar - empty sources jar * Support maven upload for jar-deploy and jar-proto For jar-deploy targets we don't check for internal dependencies, because these should already be contained in the (fat-)jar itself. Additionally, the release program now uploads javadocs and sources for jar-proto and jar-deploy as well to comply with maven central. * Upload ledger-api-test-tool and kvutils + dependencies to maven central. This is the diff running the output of the release without and with these changes. A few artifacts now also get their javadoc and sources uploaded (mostly to bintray, but now they are ready for a maven central upload). ledger-api-test-tool has the scala version removed from the artifact as it is a deploy jar and nobody should care which specific scala version is used. Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-javadoc.jar Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-sources.jar Only in release/com/daml/ledger/testtool: ledger-api-test-tool Only in release-before/com/daml/ledger/testtool: ledger-api-test-tool_2.12 Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-javadoc.jar Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-javadoc.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-sources.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-javadoc.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-sources.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-javadoc.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-sources.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-javadoc.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-sources.jar
2019-11-18 16:40:15 +03:00
mavenUpload: true
Fix the import paths of {value,transaction,blindinginfo}.proto (#3312) * Fix the import paths of {value,transaction,blindinginfo}.proto This cleans the imports in daml_kvutils.proto: -import "daml-lf/transaction/src/main/protobuf/transaction.proto"; +import "com/digitalasset/daml/lf/transaction.proto"; This shouldn't be a breaking change to the outside as the proto files themselves are not published, only the java libraries generated from them. * Update missed deps
2019-11-01 17:54:55 +03:00
- target: //daml-lf/transaction:blindinginfo_java_proto
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
type: jar-proto
Upload proto and deploy jars to maven (#3507) * Add helper to produce an empty zip files. This is used to generate empty sources and javadoc jars for deploy jars later on. * Create empty auxilliary jars. da_java_binary: - empty javadoc jar - empty sources jar da_java_proto_library: - empty javadoc jar - the sources jar is automatically generated by java_proto_library as a side effect da_scala_binary: - empty javadoc jar - empty sources jar * Support maven upload for jar-deploy and jar-proto For jar-deploy targets we don't check for internal dependencies, because these should already be contained in the (fat-)jar itself. Additionally, the release program now uploads javadocs and sources for jar-proto and jar-deploy as well to comply with maven central. * Upload ledger-api-test-tool and kvutils + dependencies to maven central. This is the diff running the output of the release without and with these changes. A few artifacts now also get their javadoc and sources uploaded (mostly to bintray, but now they are ready for a maven central upload). ledger-api-test-tool has the scala version removed from the artifact as it is a deploy jar and nobody should care which specific scala version is used. Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-javadoc.jar Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-sources.jar Only in release/com/daml/ledger/testtool: ledger-api-test-tool Only in release-before/com/daml/ledger/testtool: ledger-api-test-tool_2.12 Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-javadoc.jar Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-javadoc.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-sources.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-javadoc.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-sources.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-javadoc.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-sources.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-javadoc.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-sources.jar
2019-11-18 16:40:15 +03:00
mavenUpload: true
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/transaction:transaction
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
daml-lf: new data-scalacheck library for ImmArray, FrontStack, et al (#2342) * new data-scalacheck library for ImmArray, FrontStack, et al * add checkLaws functions as library to data-scalacheck * make checkLaws more configurable at use points
2019-08-01 18:10:56 +03:00
- target: //daml-lf/data-scalacheck:data-scalacheck
Release missing sources jars (#2683) * Release missing sources jars * Review feedback by Gerolf
2019-08-29 09:21:57 +03:00
type: jar-scala
Release lf scalacheck test jars to maven central (#3519) as they are dependencies used downstream
2019-11-19 15:10:28 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/transaction-scalacheck:transaction-scalacheck
Release missing sources jars (#2683) * Release missing sources jars * Review feedback by Gerolf
2019-08-29 09:21:57 +03:00
type: jar-scala
Release lf scalacheck test jars to maven central (#3519) as they are dependencies used downstream
2019-11-19 15:10:28 +03:00
mavenUpload: True
cleanup daml-lf scala packages (#1581) * cleanup daml-lf scala packages * Address Stephen's Comments * update maven coordinates of language package
2019-06-12 18:55:48 +03:00
- target: //daml-lf/language:language
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/interface:interface
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/validation:validation
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/interpreter:interpreter
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/scenario-interpreter:scenario-interpreter
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/engine:engine
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/repl:repl
type: jar
- target: //ledger-api/grpc-definitions:ledger-api-protos-tarball
type: targz
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
location:
groupId: com.digitalasset
artifactId: ledger-api-protos
- target: //ledger-api/rs-grpc-bridge:rs-grpc-bridge
type: jar-lib
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/java/bindings:bindings-java
type: jar-lib
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/java/bindings-rxjava:bindings-rxjava
type: jar-lib
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/sandbox:sandbox-tarball
type: targz
location:
groupId: com.digitalasset
artifactId: sandbox
- target: //extractor:extractor-binary
type: jar-deploy
- target: //ledger-api/grpc-definitions:ledger-api-scalapb
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger-api/testing-utils:testing-utils
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/scala/bindings:bindings
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger-api/rs-grpc-akka:rs-grpc-akka
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Ledger API: Add healthcheck endpoints. (#3573) * grpc-definitions: Delete health_service.proto We can use the version in io.grpc:grpc-services instead. * ledger: Delete ledger/API.md. * sandbox: Fix warnings in ApiServices flagged by IntelliJ. * sandbox: Implement a dummy grpc.health.v1.Health.Check endpoint. * sandbox: Implement a dummy grpc.health.v1.Health.Watch endpoint. * sandbox: Drop repeated elements from grpc.health.v1.Health.Watch. * sandbox: Wrap the HealthService in basic tests. * sandbox: Stop streaming the server health too. * ledger-api-test-tool: Health check tests. * Add a changelog entry for the health check endpoints. CHANGELOG_BEGIN - [Ledger API] Add healthcheck endpoints, conforming to the `GRPC Health Checking Protocol <https://github.com/grpc/grpc/blob/master/doc/health-checking.md>`_. It is always ``SERVING`` for now. - [DAML Ledger Integration Kit] Add conformance test coverage for the ``grpc.health.v1.Health`` service. CHANGELOG_END * ledger-api-integration-tests: Increment the number of services. * Apply suggestions from code review Co-Authored-By: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * sandbox: Use `AkkaBeforeAndAfterAll` in the HealthServiceSpec. In an attempt to get it working on CI. * sandbox: Change `dropRepeated` to `DropRepeated()`. Keep it in one file. * test-common: Use `Delayed.by` in `TimeBoundObserver`. * test-common: Close the source when `TimeBoundObserver` completes. * ./fmt.sh That'll teach me not to `--no-verify` just because it's a merge commit. * sandbox: Inline `HealthService.suppress`. At some point it was being used twice. * sandbox: Increase the timeout for HealthServiceSpec. * sandbox: Reimplement HealthService using the Scala protobuf types. * sandbox: Generate an Akka-compatible trait for the health service. And refactor a lot of test code to make it easy to test. * ledger-api-common: Move the HealthService here. * rs-grpc-testing-utils: Publish to Maven. * rs-grpc-testing-utils: Add Maven coordinates.
2019-11-22 17:02:05 +03:00
- target: //ledger-api/rs-grpc-testing-utils:rs-grpc-testing-utils
type: jar-scala
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/ledger-api-akka:ledger-api-akka
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //scala-protoc-plugins/scala-logging:scala-logging-lib
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/ledger-api-scala-logging:ledger-api-scala-logging
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/ledger-api-client:ledger-api-client
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: true
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/ledger-api-domain:ledger-api-domain
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/ledger-api-common:ledger-api-common
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Move AuthService (#3272) * Move AuthService and Claims * Move interceptor and authorization wrappers * Add artifact * Address review comments
2019-10-29 18:46:43 +03:00
- target: //ledger/ledger-api-auth:ledger-api-auth
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger/sandbox:sandbox
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Ledger api test tool release (#756) * release: make 'ci/release.sh' runnable for dry runs. release-dry-run.sh is outdated and duplicates logic from ci/release.sh, so it got deleted. * ledger-api-test-tool: release the tool together with the SDK components. * ledger-api-test-tool: update docs to reflect distribution mechanism. * ledger-api-test-tool: further docs refinements. * Add Ledger API Test Tool mention into release notes.
2019-04-29 15:16:19 +03:00
- target: //ledger/ledger-api-test-tool:ledger-api-test-tool
type: jar-deploy
Upload proto and deploy jars to maven (#3507) * Add helper to produce an empty zip files. This is used to generate empty sources and javadoc jars for deploy jars later on. * Create empty auxilliary jars. da_java_binary: - empty javadoc jar - empty sources jar da_java_proto_library: - empty javadoc jar - the sources jar is automatically generated by java_proto_library as a side effect da_scala_binary: - empty javadoc jar - empty sources jar * Support maven upload for jar-deploy and jar-proto For jar-deploy targets we don't check for internal dependencies, because these should already be contained in the (fat-)jar itself. Additionally, the release program now uploads javadocs and sources for jar-proto and jar-deploy as well to comply with maven central. * Upload ledger-api-test-tool and kvutils + dependencies to maven central. This is the diff running the output of the release without and with these changes. A few artifacts now also get their javadoc and sources uploaded (mostly to bintray, but now they are ready for a maven central upload). ledger-api-test-tool has the scala version removed from the artifact as it is a deploy jar and nobody should care which specific scala version is used. Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-javadoc.jar Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-sources.jar Only in release/com/daml/ledger/testtool: ledger-api-test-tool Only in release-before/com/daml/ledger/testtool: ledger-api-test-tool_2.12 Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-javadoc.jar Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-javadoc.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-sources.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-javadoc.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-sources.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-javadoc.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-sources.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-javadoc.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-sources.jar
2019-11-18 16:40:15 +03:00
mavenUpload: true
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/scala/codegen:codegen
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
type: jar-scala
mavenUpload: true
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/scala/codegen:codegen-main
type: jar
- target: //language-support/scala/bindings-akka:bindings-akka
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
mavenUpload: True
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/java/codegen:shaded_binary
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
mavenUpload: true
- target: //language-support/java/codegen:lib
type: jar-scala
mavenUpload: true
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //navigator/backend:navigator-binary
type: jar-deploy
Unify Scala and Java Codegen Inputs (#585) * Extract codegen-common module, #166 * Scala Codegen Main using the same option parser as Java Codegen, #166 There is one important difference, Scala Codegen does not allow mapping dars to different package names, all dars have to be mapped to the same package name. Replace Scala Codegen println's with scala logging, respecting the configured codegen verbosity * Fix bazel formatting * Update the release dry run script * Releasing codegen-common * Improving Scala Codegen error reporting (code review) * Addressing codereview comments * Make it explicit that we skip not supported option
2019-04-18 22:04:57 +03:00
- target: //language-support/codegen-common:codegen-common
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
mavenUpload: true
Release codegen front-end shaded binary, #615 (#617) * Release codegen front-end shaded binary, #615 * Fix bazel formatting
2019-04-19 17:24:57 +03:00
- target: //language-support/codegen-main:shaded_binary
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
mavenUpload: true
Add damlonx artifacts to the release (#627)
2019-04-23 15:00:55 +03:00
- target: //ledger/participant-state:participant-state
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Add damlonx artifacts to the release (#627)
2019-04-23 15:00:55 +03:00
- target: //ledger/participant-state-index:participant-state-index
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
Remove DAML-on-X IndexServer and Reference Server (#3108) It is not needed anymore and can therefore be deleted.
2019-10-08 12:47:21 +03:00
- target: //ledger/sandbox:ledger-api-server
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Remove DAML-on-X IndexServer and Reference Server (#3108) It is not needed anymore and can therefore be deleted.
2019-10-08 12:47:21 +03:00
mavenUpload: True
DamlOnX: release kvutils (#763) * Move package comment to correct place * Update kvutils package documentation * Release participant-state-kvutils
2019-04-29 17:05:22 +03:00
- target: //ledger/participant-state/kvutils:daml_kvutils_java_proto
type: jar-proto
Upload proto and deploy jars to maven (#3507) * Add helper to produce an empty zip files. This is used to generate empty sources and javadoc jars for deploy jars later on. * Create empty auxilliary jars. da_java_binary: - empty javadoc jar - empty sources jar da_java_proto_library: - empty javadoc jar - the sources jar is automatically generated by java_proto_library as a side effect da_scala_binary: - empty javadoc jar - empty sources jar * Support maven upload for jar-deploy and jar-proto For jar-deploy targets we don't check for internal dependencies, because these should already be contained in the (fat-)jar itself. Additionally, the release program now uploads javadocs and sources for jar-proto and jar-deploy as well to comply with maven central. * Upload ledger-api-test-tool and kvutils + dependencies to maven central. This is the diff running the output of the release without and with these changes. A few artifacts now also get their javadoc and sources uploaded (mostly to bintray, but now they are ready for a maven central upload). ledger-api-test-tool has the scala version removed from the artifact as it is a deploy jar and nobody should care which specific scala version is used. Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-javadoc.jar Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-sources.jar Only in release/com/daml/ledger/testtool: ledger-api-test-tool Only in release-before/com/daml/ledger/testtool: ledger-api-test-tool_2.12 Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-javadoc.jar Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-javadoc.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-sources.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-javadoc.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-sources.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-javadoc.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-sources.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-javadoc.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-sources.jar
2019-11-18 16:40:15 +03:00
mavenUpload: true
DamlOnX: release kvutils (#763) * Move package comment to correct place * Update kvutils package documentation * Release participant-state-kvutils
2019-04-29 17:05:22 +03:00
- target: //ledger/participant-state/kvutils:kvutils
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Upload proto and deploy jars to maven (#3507) * Add helper to produce an empty zip files. This is used to generate empty sources and javadoc jars for deploy jars later on. * Create empty auxilliary jars. da_java_binary: - empty javadoc jar - empty sources jar da_java_proto_library: - empty javadoc jar - the sources jar is automatically generated by java_proto_library as a side effect da_scala_binary: - empty javadoc jar - empty sources jar * Support maven upload for jar-deploy and jar-proto For jar-deploy targets we don't check for internal dependencies, because these should already be contained in the (fat-)jar itself. Additionally, the release program now uploads javadocs and sources for jar-proto and jar-deploy as well to comply with maven central. * Upload ledger-api-test-tool and kvutils + dependencies to maven central. This is the diff running the output of the release without and with these changes. A few artifacts now also get their javadoc and sources uploaded (mostly to bintray, but now they are ready for a maven central upload). ledger-api-test-tool has the scala version removed from the artifact as it is a deploy jar and nobody should care which specific scala version is used. Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-javadoc.jar Only in release/com/daml/ledger/participant-state-kvutils-java-proto/100.13.35: participant-state-kvutils-java-proto-100.13.35-sources.jar Only in release/com/daml/ledger/testtool: ledger-api-test-tool Only in release-before/com/daml/ledger/testtool: ledger-api-test-tool_2.12 Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-javadoc.jar Only in release/com/digitalasset/daml/lf/engine/trigger/runner_2.12/100.13.35: runner_2.12-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-blindinginfo-java-proto/100.13.35: daml-lf-blindinginfo-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-transaction-java-proto/100.13.35: daml-lf-transaction-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-javadoc.jar Only in release/com/digitalasset/daml-lf-value-java-proto/100.13.35: daml-lf-value-java-proto-100.13.35-sources.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-javadoc.jar Only in release/com/digitalasset/damlc/100.13.35: damlc-100.13.35-sources.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-javadoc.jar Only in release/com/digitalasset/extractor/100.13.35: extractor-100.13.35-sources.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-javadoc.jar Only in release/com/digitalasset/ledger-service/http-json-deploy/100.13.35: http-json-deploy-100.13.35-sources.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-javadoc.jar Only in release/com/digitalasset/navigator/100.13.35: navigator-100.13.35-sources.jar
2019-11-18 16:40:15 +03:00
mavenUpload: true
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +03:00
- target: //ledger-service/lf-value-json:lf-value-json
type: jar-scala
- target: //ledger-service/utils:utils
type: jar-scala
- target: //ledger-service/jwt:jwt
type: jar-scala
Check internal dependencies of maven artifacts (#3454) * Check internal dependencies of maven artifacts All artifacts that are uploaded to maven need to also have their dependencies uploaded to maven. * inline tuple matching * remove unnecessary parenthesis * mark missing artifacts for maven upload
2019-11-14 16:18:54 +03:00
mavenUpload: True
json-api: store contracts similar to Extractor's single-table (#3192) * new library ledger-service/db-backend * borrow contracts table schema from extractor * borrow contract insertion, removing some data to be unused * match contract schema with insert function * factor insertContract arguments * offset table declarations * CLI argument for query store * surrogate template IDs * compute surrogate template IDs on-the-fly * database init action * incoherent typeclasses, eh * newtype SurrogateTpId * offset fetch/update functions * bad sql * bulk insert contracts, function for selecting contracts * expose contract column name for query's usage * Initializing DB on startup if configured * dropping existing tables as part of initialization * fix some query syntax errors * createSchema flag * function for streaming transactions with jwt party selected * formatting * usage * collect acs contracts and the ledger offset at the end * lastOffset * fixing merge conflicts, updating the way 3rd party deps are specified * Moving ContractDao into http-json module so it can take domain AST as an input * cleanup * injecting new dependencies * split transaction batches into inserts and deletes * generate sql for deleting contracts * `fetch_sources = True` for java_deps * make the delete-constructed fragment more efficient; handle empty list here * pass logHandler for insertContracts * ContractDao returns ConnectionIO, it's up to the caller to wrap query into a transaction * fixing typo * minor cleanup, moving fromLedgerApi factory function into corresponding companion objects * don't need it any more * GetActiveContractsResponse => domain.Contract factory * make concatFragment private * add partition graph; move other contract-fetching experiments to ContractsFetch * experimenting with akka sources * introducing domain.Offset to work around API's empty/null offset cases * minor cleanup * decompose fetchActiveContractsFromOffset * missed via * ACS splitting graph * finish doc for ACS splitting graph * remove unneeded stages * WIP * lazily read a stream of ConnectionIO into a single ConnectionIO * cancel on IO error * figuring out how to put all the pieces together * graph WIP * Removing workflowId from the JSON API * simplify acsAndBoundary; describe other flow pieces * WIP * use Vector in InsertDeleteStep; add variant for ACS (no deletes) * `org.wartremover.warts.NonUnitStatements` enforced in `http-json` module * evaluate InsertDeleteStep to a ConnectionIO * database variant of LfValueCodec, using numbers for numbers * convert input to JSON, combine insert plans, connect rest of contractsToOffsetIo * remove strict contractsToOffset sink * moving dao methods into an object * putting pieces together * contractsFromOffset WIP * should be it * cleanup * cleanup * contractsIo that takes List[domain.TemplateId.RequiredPkg]) * contractsIo that takes List[domain.TemplateId.RequiredPkg]) * cleanup * put all pieces together, testing something does not work yet * diff is not required to return anything that is why Sink.lastOption that gives Option[domain.Offset] * factor out tuple split * use traverse syntax in contractsIo2 * factor explicit flow steps out of graph DSL; remove aggregate * locally model the Absolute/Begin distinction for offset bookmarking in DB * Adding test cases to run HTTP Service with Postgres backend the same set of test cases, run with and without DB backend * make better use of domain.Offset in OffsetBoundary * monomorphize InsertDeleteStep#append * Disabling a test that fails with DB backend * add release note * add release note about workflowId * a test case that checks the number or stored contracts * trying to figure out why Postgres test fails on Windows with NPE
2019-11-06 21:53:16 +03:00
- target: //ledger-service/db-backend:db-backend
type: jar-scala
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +03:00
- target: //ledger-service/http-json:http-json
type: jar-scala
Releasing http-json-binary (#2751) com/digitalasset/ledger-service/http-json-deploy/100.13.21
2019-09-04 22:47:24 +03:00
- target: //ledger-service/http-json:http-json-binary
type: jar-deploy
Release DAML trigger runner to Bintray (#3243) This should make it a bit easier to use in a managed environment and has been requested by some users.
2019-10-22 01:14:46 +03:00
- target: //triggers/runner:trigger-runner
type: jar-deploy
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
- target: //daml-assistant/scala-daml-project-config:scala-daml-project-config
type: jar-scala
mavenUpload: true
Extractor with authentication (#3514) * Make Extractor work against Ledger API servers protected by authentication * Update changelog * Address https://github.com/digital-asset/daml/pull/3514#pullrequestreview-318811500 - https://github.com/digital-asset/daml/pull/3514#discussion_r347753205 - https://github.com/digital-asset/daml/pull/3514#discussion_r347753629 - https://github.com/digital-asset/daml/pull/3514#discussion_r347754462 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347755484 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347752424 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347756328 * Fix docs * Fix artifacts.yaml
2019-11-19 19:12:25 +03:00
- target: //libs-scala/grpc-utils:grpc-utils
type: jar-scala
mavenUpload: True
- target: //libs-scala/timer-utils:timer-utils
type: jar-scala
mavenUpload: true
Reference in New Issue Copy Permalink