[go-nuts] Re: Problem with migration to the new "module" technology from "go"

in the case you should provide local path to your module through *module.package replace => local.path *in go.mod it makes some pain and stops independent work with project. To decrease the pain, I made some solution for maven which automatically work with

[go-nuts] Re: Problem with migration to the new "module" technology from "go"

You need to tell go module where to find the library. It defaults to using central repositories (such as github). If you have the library in the local machine, you can add into your go.mod file something like this: ``` replace namespace/to/pkgname => local/path/to/pkgname ``` When you run 'go i