[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942432#comment-16942432
]
Roddie Kieley commented on PROTON-2105:
---------------------------------------
[~lulf] After reading the docs and looking at some examples I'm not sure we'll
be able to avoid something similar to the above. As per [Using Go
Modules|https://blog.golang.org/using-go-modules]:
{quote}
The go.mod file defines the module’s module path, which is also the import path
used for the root directory...
{quote}
So it appears in the qpid-proton go.mod file we'd have something like
{noformat}
module github.com/apache/qpid-proton
{noformat}
and in the import to get from the root to the go source for a package we need
the above + go/src/qpid.apache.org/amqp
{noformat}
import "github.com/apache/qpid-proton/go/src/qpid.apache.org/amqp"
{noformat}
And as well we don't get to require qpid-proton-c from the go side which would
be more accurate given that it depends on the native c libraries produced.
> Support Go modules
> ------------------
>
> Key: PROTON-2105
> URL: https://issues.apache.org/jira/browse/PROTON-2105
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
> Reporter: Ulf Lilleengen
> Assignee: Roddie Kieley
> Priority: Major
>
> As of Go 1.12, go module support is available. In order to manage
> dependencies using go modules, dependencies must also be using go modules.
> Therefore, adding a go.mod file to each module would allow qpid proton go
> bindings to be managed as a go module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
