Ittai Zeidman

We tried using Coursier for our internal version of Bazel-deps and found discrepancies with how it resolves dependencies compared to aether. I'll ask Or to comment in #23 if he...

:) I think the biggest difference between bazel-deps and our tool is that we’re really focused on having many repositories play together and having a managed dependencies place for most...

@johnynek using deps instead of runtime_deps will indeed trigger more compilations if changes of that dependency propagate over the ijar. Other than that it should be the same since: 1....

Carmi by "what they import" you mean what they actually use in their sources as opposed to arbitrary needs of the compiler, right? On Wed, 6 Sep 2017 at 23:42...

Three small points: 1. Will one have conflicts if there is a header which loads scala library and also this happens in a prelude? 2. I think recursive workspaces is...

Just so it's clear- our tool does resolution ahead of time just like bazel-deps. We might change it when/if recursive workspaces arrives since it sounds like it will allow advantages...

You mean build all targets of external dependencies? On Tue, 28 Nov 2017 at 3:39 P. Oscar Boykin wrote: > oscar [15:33] > the reason I did it was simple:...

Oh I see, thanks for the clarification On Tue, 28 Nov 2017 at 7:39 P. Oscar Boykin wrote: > Sorry this was unclear. Why do we make BUILD rules for...

jar is an optional packaging type. For others it's mandatory. There's also classifier and I think something else.

+1 for @noam-almog's request for usage, I was thinking the same thing. WDYT about the following usage? ``` scala "Person Validations" should { "fail a person with an empty first...