Replace only works for the top-level go.mod. From the proposal doc (link <https://go.googlesource.com/proposal/+/master/design/24301-versioned-go.md> ):
> Minimal version selection gives the top-level module in the build > additional control, allowing it to exclude specific module versions or > replace others with different code, but those exclusions and replacements > only apply when found in the top-level module, not when the module is a > dependency in a larger build. A module author is therefore in complete control of that module‘s build > when it is the main program being built, but not in complete control of > other users’ builds that depend on the module. I believe this distinction > will make this proposal scale to much larger, more distributed code bases > than the Bundler/Cargo/Dep approach. And from the GoWiki module page (link <https://github.com/golang/go/wiki/Modules#when-should-i-use-the-replace-directive> ): > replace allows the top-level module control over the exact version used > for a dependency On Friday, February 7, 2020 at 2:01:19 PM UTC-5, kuznets...@gmail.com wrote: > > 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? > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0ede0c67-46c4-45ba-8095-74d7d08d3a16%40googlegroups.com.
