How to Resolve Import Conflicts in Google Go App Engine Projects?

Google Go AppEngine imports and conflicts when serving / testing

Appengine is encountering issues when scanning the application directory for dependencies, leading to conflicts with files imported within the source code.

To resolve this issue, you have two options:

Option 1: Remove the source repository path from sub-folder package imports

• Modify imports to exclude the "source repository" part. For example, instead of "github.com/blah/blah", use "blah/blah".

Option 2: Move sub-folder packages to a separate project

• Move sub-folder dependencies to an independent project without an app.yaml file.
• In the main project, import these dependencies using the full path, e.g., "github.com/MarkHayden/SampleIssueDeps/lib1".

When using option 1, your project becomes specific to Appengine and may require build constraints ( build !appengine) for code that should be excluded when building for other targets.

When using option 2, Appengine will no longer attempt to import dependencies, as they will be pulled in externally.

In summary, for sub-folder packages in Appengine projects, either remove the source repository part from import paths or move the code to separate projects and import them as external dependencies.

The above is the detailed content of How to Resolve Import Conflicts in Google Go App Engine Projects?. For more information, please follow other related articles on the PHP Chinese website!