You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a single repository with hierarchical modules, e.g.:
main
|-- module_1
| |-- go.mod <- it contains deps of module_1 only
| |-- "go files of module_1"
|-- module_2
| |-- go.mod <- it contains deps of module_2 only
| |-- "go files of module_2"
|-- go.mod <- it contains deps of module main only
|-- "go files of main"
If I execute "vgo build" in each folder separately everything works as expected. However, if I execute "vgo build ./..." or "vgo test ./..." in the main folder then the go.mod file of main is automatically modified to include all the dependencies of the internal modules (in this case, module_1 and module_2)
What did you expect to see?
I expected that executing "vgo build ./..." (or "vgo test ./...") each modules was built (or tested) independently and the go.mod file of each module was not impacted by the one of the others.
What did you see instead?
The go.mod file of the parent at the end of the build contains all the dependencies of the inner modules.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?go version go1.10.2 linux/amd64
go version go1.10.2 linux/amd64 vgo:2018-02-20.1
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?What did you do?
I have a single repository with hierarchical modules, e.g.:
If I execute "vgo build" in each folder separately everything works as expected. However, if I execute "vgo build ./..." or "vgo test ./..." in the main folder then the go.mod file of main is automatically modified to include all the dependencies of the internal modules (in this case, module_1 and module_2)
What did you expect to see?
I expected that executing "vgo build ./..." (or "vgo test ./...") each modules was built (or tested) independently and the go.mod file of each module was not impacted by the one of the others.
What did you see instead?
The go.mod file of the parent at the end of the build contains all the dependencies of the inner modules.
The text was updated successfully, but these errors were encountered: