The fact that a module-mode build ignores dependencies vendored into *other* modules is intentional. #27227 may change several details of vendoring in module mode, but this is not one of them.
If module B vendors its dependencies but does not specify their versions in a go.mod file, then you should specify the versions of those dependencies that you want in *your* module's go.mod file. (You can set them to something consistent using go get -m.) On Sunday, February 10, 2019 at 12:26:10 PM UTC-5, Ian Davis wrote: > > > On Sun, 10 Feb 2019, at 12:03 AM, se...@pion.ly <javascript:> wrote: > > * I have a project 'A' that is importing 'B' > * 'B' uses a vendor folder, if you delete the vendor folder the project > does not compile. > * With `GO111MODULE=on` I am unable to project 'A'. It tries to pull the > latest of 'B', and everything 'B' depends on (instead of using 'B's vendor > folder) > > Does anyone have suggestions on what I should do here? I don't control > project 'B' only 'A' > > > > This sounds like issue https://github.com/golang/go/issues/27227 which is > still under discussion > > Ian > > -- 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. For more options, visit https://groups.google.com/d/optout.
