Splitting the uses of a/b into their own modules/repo won't work if you ultimately import them into a single module. It would be the same problem, just further down the dependency tree.
On Monday, March 7, 2022 at 7:14:17 PM UTC ian.zh...@gmail.com wrote: > > Thanks for your reply. > > It's sad that *a* and *b* are imported but not developed by my team.... I > guess I will have to split my *demo* to smaller modules to make sure *a* > and *b* are in a different module. > > I tried to have something like this, > > demo/ > pkg/ > onlya/ > a.go > go.mod > go.sum > onlyb/ > b.go > go.mod > go.sum > main.go > go.mod > go.sum > > however, in this way the top-level *go.mod* would still resolve and > contain *a* and *b*... I guess I will have to put *a* or *b* to its own > repo. > > On Monday, March 7, 2022 at 12:25:16 PM UTC-5 seank...@gmail.com wrote: > >> As a v0.x.y module, it's explicitly signaling that it may introduce >> incompatible changes between minor versions, as has happened here. >> unfortunately for you, a module can only exist at a single version within a >> build, so you'll have to modify your dependencies. >> Some time ago, OpenTelemetry graduated their tracing APIs to stable (v1), >> committing to maintaining backwards compatibility, so you may want to look >> at upgrading both your dependencies to target the new, stable version of >> OpenTelemetry >> >> On Monday, March 7, 2022 at 5:02:06 PM UTC Tamás Gulácsi wrote: >> >>> Sorry to say, but *go.opentelemetry.io/otel >>> <http://go.opentelemetry.io/otel>* is a dumpster fire of API breakage >>> and flux. >>> I don't know other solution than modify a or b to use the same version >>> of otel. >>> >>> ian.zh...@gmail.com a következőt írta (2022. március 7., hétfő, >>> 17:49:17 UTC+1): >>> >>>> Hi team, >>>> >>>> I'm working on a new package, *demo*, which has a dependency on *a* >>>> and *b*. >>>> >>>> Both *a* and *b* are pointing to `go.opentelemetry.io/otel` >>>> <http://go.opentelemetry.io/otel> >>>> >>>> *a* points to *go.opentelemetry.io/otel >>>> <http://go.opentelemetry.io/otel>* v0.20.0 >>>> *b* points to *go.opentelemetry.io/otel >>>> <http://go.opentelemetry.io/otel>* v0.25.0 >>>> >>>> However, the *go.opentelemetry.io/otel >>>> <http://go.opentelemetry.io/otel>* introduced break changes between >>>> these 2 versions. >>>> At *v0.25.0*, it dropped some functions that exist in *v0.20.0* and >>>> *v0.25.0* has some new functions. >>>> >>>> In my *demo*, the *go mod tidy* would point to v0.20.0, in this way, >>>> it breaks the dependency of *b.* >>>> >>>> I tried to modify the *go.mod *of *demo* in order to find a common >>>> version between *a* and *b*, but I can't >>>> find such. >>>> >>>> I wonder if there's a way to let *go mod* to allow specific module >>>> versions for *a* and *b. *If not, what's other >>>> possible ways to solve this issue? >>>> >>>> >>>> Looking forward to your reply. >>>> Ian >>>> >>> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/40825a3c-aae3-4873-8bdb-10465627bb2an%40googlegroups.com.
