digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-10 10:46:11 +03:00
Code Issues Projects Releases Wiki Activity
6943165c84
daml/release/artifacts.yaml

152 lines
4.8 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
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: 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
- 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
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
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
- 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
type: jar
- 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
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
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
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
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
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
- 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
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
- 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
Reference in New Issue Copy Permalink