Re: [go-nuts] Re: Dependency hierarchy in go

On Monday, February 10, 2020 at 1:42:34 PM UTC+3, rog wrote: > > On Fri, 7 Feb 2020 at 19:47, > wrote: > >> >> >> On Friday, February 7, 2020 at 10:35:37 PM UTC+3, Jason Phillips wrote: >>> >>> Replace only works for the top-level go.mod. From the proposal doc (link >>>

Re: [go-nuts] Re: Dependency hierarchy in go

On Fri, 7 Feb 2020 at 19:47, wrote: > > > On Friday, February 7, 2020 at 10:35:37 PM UTC+3, Jason Phillips wrote: >> >> Replace only works for the top-level go.mod. From the proposal doc (link >> >> ): >> >>> Minimal ver

[go-nuts] Re: Dependency hierarchy in go

On Friday, February 7, 2020 at 10:35:37 PM UTC+3, Jason Phillips wrote: > > Replace only works for the top-level go.mod. From the proposal doc (link > > ): > >> Minimal version selection gives the top-level module in th

[go-nuts] Re: Dependency hierarchy in go

Replace only works for the top-level go.mod. From the proposal doc (link ): > Minimal version selection gives the top-level module in the build > additional control, allowing it to exclude specific module versions or >

[go-nuts] Re: Dependency hierarchy in go

I'm I bad at explaining? Simple form: A (go.mod = require B) -> B (go.mod = require C; replace C=>C1) -> C1 'A' failed to compile because it does not see C=>C1 replace in child project. Does GO require to copy all replace commands from all child projects in main go.mod manually or is it a bug?