Home  >  Article  >  Backend Development  >  How to import workspace as dependency into another go repository?

How to import workspace as dependency into another go repository?

王林
王林forward
2024-02-09 08:33:20625browse

如何将工作区作为依赖项导入到另一个 go 存储库中?

php Xiaobian Yuzai is here to share with you a question about the Go language: "How to import the workspace as a dependency into another Go repository?" In the Go language In development, dependency management is a common problem. Sometimes, we may need to import a workspace as a dependency into another repository for use in a project. In this article, I will give you a detailed introduction to how to achieve this goal to help you better manage the dependencies of your Go language project.

Question content

I have a multi-workspace project whose structure is:

apps/go.mod
go.work

The project contains a submodule apps and its go.work file has:

go 1.180
use (
./apps
)

I have another go project (separate repository) that I want to import this app submodule as a library, here is go.mod:

module xxxx

go 1.18

require (
    github.com/zhaoyi0113/test-go-module v0.0.3 // indirect
)

Then I have the following code:

package main

import (
    "github.com/zhaoyi0113/test-go-module/apps/logger"
)

func main() {
    logger.test()
}

Compilation failed with the following error:

main.go:7:2: no required module provides package github.com/zhaoyi0113/test-go-module/apps/logger; to add it:
        go get github.com/zhaoyi0113/test-go-module/apps/logger

How to import submodules from a multi-workspace project?

Workaround

You cannot import the workspace.

The current situation is as follows:

github.com/zhaoyi0113/test-go-module/apps There is a module declares its module path as github.com/zhaoyi0113/test-go-module . The module is not available because the module's actual path does not match the declared path (note that /apps is missing from one of the paths).

xxxx module requires github.com/zhaoyi0113/test-go-module, but the module is not found in this path. It is located in the apps subdirectory as described in the previous paragraph.

There are two possible fixes depending on where you want to place the module.

If you want to keep the imported go.mod in the current directory then update the module path to include apps:

Import module’s go.mod:

module github.com/zhaoyi0113/test-go-module/apps
go 1.19

go.mod for importing modules:

module xxxx
go 1.18
require (
    github.com/zhaoyi0113/test-go-module/apps v0.0.3 // indirect
)

The second is also a regular option Just put go.mod in the root directory of the project and put the go.work file outside the project. To implement this functionality, move go.mod to the root of the project (as it was in the original commit) and move go.work elsewhere. No changes are required to the imported modules.

The above is the detailed content of How to import workspace as dependency into another go repository?. For more information, please follow other related articles on the PHP Chinese website!

Statement:
This article is reproduced at:stackoverflow.com. If there is any infringement, please contact admin@php.cn delete