Re: Compile scope dependency, used as runtime scope transitively

Declaring "upstream-library" with scope "runtime" in the dependencyManagement section of "my-project" should do it. However, I don't see the real benefit of going through this hassle. /Anders On Wed, Dec 27, 2017 at 11:30 AM, Nick Stolwijk wrote: > But I think that he

Re: Compile scope dependency, used as runtime scope transitively

But I think that he wants it transitive, but only at runtime scope instead of compile time. I also wondered a while ago if this was possible. It would be nice to keep clean projects clean. (As in, declared all compile time dependencies instead of relying on transitive compile time dependencies.)

Re: Compile scope dependency, used as runtime scope transitively

So you could have scope=compile=true (which means the dep is non-transitive) On Wed 27 Dec 2017 at 00:26, Andy Feldman wrote: > On Dec 26, 2017 11:34, "Stephen Connolly" > > wrote: > > On Sun 24 Dec 2017 at 18:01, Andy Feldman

Re: Compile scope dependency, used as runtime scope transitively

On Dec 26, 2017 11:34, "Stephen Connolly" wrote: On Sun 24 Dec 2017 at 18:01, Andy Feldman wrote: > Assuming I have a dependency relationship of "my-project -> my-library -> > upstream-library", with each dependency in compile scope, I

Re: Compile scope dependency, used as runtime scope transitively

On Sun 24 Dec 2017 at 18:01, Andy Feldman wrote: > Assuming I have a dependency relationship of "my-project -> my-library -> > upstream-library", with each dependency in compile scope, I know that > my-project transitively picks up a compile scope dependency on >

Compile scope dependency, used as runtime scope transitively

Assuming I have a dependency relationship of "my-project -> my-library -> upstream-library", with each dependency in compile scope, I know that my-project transitively picks up a compile scope dependency on upstream-library. Reading the documentation at