daml/3rdparty
Neil Mitchell 85c72f87d1 Move to using proto3-wire from upstream (#480)
* Move to using proto3-wire from upstream

* Move to upstream proto3-suite, with some custom patches in my fork

* Delete the BUILD.bazel for hte proto3 stuff, not used and the test was failing

* Delete the old proto3-wire and proto3-suite forks

* Delete proto3-wire

* Prettify BUILD.bazel files, sort the deps

* Remove some special cases from the license checker

* Delete unused Nix files from grpc-haskell

* Switch to upstream proto3-suite

* Make old-time work on Windows

* Formatting

* Patch rules_haskell to use a response file for -optP to avoid overflowing argument size limits on Windows

* Update 3rdparty/haskell/BUILD.old-time

Co-Authored-By: neil-da <35463327+neil-da@users.noreply.github.com>

* Update the comments in old-time

* Use the revised location of proto3-suite
2019-04-24 15:59:08 +00:00
..
c Enforce consistent formatting of BUILD files. (#412) 2019-04-12 13:10:16 +02:00
haskell Move to using proto3-wire from upstream (#480) 2019-04-24 15:59:08 +00:00
jvm adding Metrics around Ledger operations (#646) 2019-04-24 16:51:20 +02:00
BUILD open-sourcing daml 2019-04-04 09:33:38 +01:00
dependencies.digest adding Metrics around Ledger operations (#646) 2019-04-24 16:51:20 +02:00
NO_AUTO_COPYRIGHT open-sourcing daml 2019-04-04 09:33:38 +01:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00
workspace.bzl adding Metrics around Ledger operations (#646) 2019-04-24 16:51:20 +02:00

Third-Party JVM Dependencies

This subtree contains a Bazel workspace file workspace.bzl and BUILD files underneath jvm/ describing external Java and Scala dependencies. These files are automatically generated and should not be modified manually. If you need to add a third party dependency then modify the file dependencies.yaml in the repository root and re-run bazel-deps in order to regenerate these files as described at the top of the file dependencies.yaml.

Third-Party Haskell Dependencies

The haskell/ subtree contains BUILD files defining custom Hazel builds for Cabal packages imported via Hazel's hazel_custom_package_* rules in the WORKSPACE.