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
For simplicity, the first version of Go will rely on users using Go tooling to make sure that go.mod and go.sum are up-to-date. We will remove the go-resolve goal and also not hook up to generate-lockfiles.
Users are expected to run go mod tidy to make sure that their go.mod and go.sum are good. That is, Pants knows how to read those files, but not yet write them. This is similar to Python pre-#12314.
This is somewhat more acceptable because, for now, you must have Go installed already on your system to use it with Pants.
We'll document this and try to make our error messages helpful.
`go-build` will soon be replaced by a `check` implementation.
`go-resolve` should not exist because we decided in #13050 that third-party dependency management should be done independently of Pants for the first version of Go support.
[ci skip-rust]
[ci skip-build-wheels]
Eric-Arellano
changed the title
Go: design and implement third-party dependency management
Go: document plan for third-party dependency management
Oct 11, 2021
Right now, we have the custom
go-resolve
goal. Should that hook up to./pants generate-lockfiles
?The text was updated successfully, but these errors were encountered: