[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940601#comment-16940601
]
Roddie Kieley commented on PROTON-2105:
---------------------------------------
[~lulf] Took a look. Imported your branch via
{noformat}
module modProject0
require github.com/lulf/qpid-proton PROTON-2105
go 1.13
{noformat}
which go changed to
{noformat}
module modProject0
require github.com/lulf/qpid-proton v0.0.0-20190921201711-83131bc3495d //
indirect
go 1.13
{noformat}
No problem's for 'go get' to get it however atm there's a 'next step' that's
not in place:
{noformat}
i7mbp:modProject0 rkieley$ go mod why
go: finding qpid.apache.org latest
modProject0/pkg imports
qpid.apache.org/amqp: module qpid.apache.org@latest
(v0.0.0-20190926195055-822413ea1ac9) found, but does not contain package
qpid.apache.org/amqp
modProject0/pkg imports
qpid.apache.org/electron: module qpid.apache.org@latest
(v0.0.0-20190926195055-822413ea1ac9) found, but does not contain package
qpid.apache.org/electron
i7mbp:modProject0 rkieley$ go mod graph
modProject0 github.com/lulf/qpid-proton@v0.0.0-20190921201711-83131bc3495d
i7mbp:modProject0 rkieley$
{noformat}
> 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
