-
-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1 import not working, getting routed to v2 #2111
Comments
Goa v1 can be installed with go get -u -v github.com/goadesign/goa/... Note that the |
In my case, it is trying to fetch v3. This has essentially stopped out builds in CI. Let me know how to resolve this -
|
This is because v3 is the default branch. So essentially there is no way to use GOPATH mode and keep using v1. I had to move to module mode to keep using v1. In future, I would request to proceed with caution to avoid breaking your users' codebase. |
Yeah it's not great, on the other hand keeping the default on GitHub to the old master is also pretty bad as newcomers would be misled. I don't really see a good way out, do you? Obviously it's possible to use git to clone the repo and checkout the v1 branch - that makes it possible to use v1 without Go modules but is an extra unexpected step. I'll add these instructions to the v1 README. |
setup:
go version go1.11.10 linux/amd64
Instructions to install the goa toolchain are not working as expected.
Attempting to install v1 goagen via:
go get -u goa.design/v1/goa
does not hit the v1gopkg
, but rather v2.Not sure how to remedy this, any docs/work arounds available?
The text was updated successfully, but these errors were encountered: