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
On Sun, 10 Feb 2019, at 12:03 AM, s...@pion.ly 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
* 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)
