claudio4j commented on issue #4086: URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1459004426
> This one seems to be not straightforward as [moving to v2 in Go is quite complicated](https://go.dev/doc/modules/major-version). We have several modules and we may take the opportunity to move to [Go workpsaces](https://go.dev/doc/tutorial/workspaces). It's my understanding go workspaces may help with the `replaces` directive in `go.mod`, but the major pain is to actually accomodate the `/v2` to upgrade the version, that's a pity. As an example, there is `github.com/google/go-github/v32` which is a lot. I suppose they must have some script to update the version, but that seems not good to force the client users to constantly update the versions in the import section. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
