You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Alessio Gottardo <ta...@yahoo.it.INVALID> on 2017/12/14 16:55:48 UTC
Re: Electron/Amqp MessageAnnotations in Golang
On Thursday, 9 November 2017, 20:17:41 GMT, Alan Conway <ac...@redhat.com> wrote:
> Apologies for the long delay, this is a bug and was reported previously:> https://issues.apache.org/jira/browse/PROTON-1429>> I am fixing it now, watch the JIRA to be notified when it is fixed. You can> get the latest code direct from git, the "go get" repo will be updated with> the next release of proton, which should be fairly soon.
Hi there,
Is there any news on when this fix will be formally released?
Otherwise is there a script to automatically fix the issues regarding the git repository path and $GOPATH?
This approach does not make the `electron` code available to the Go compiler:
```go get qpid.apache.org/electroncd $GOPATH/src/qpid.apache.org/git checkout 4edafb1a473e3a0d9aa3b9498a3f5bba257aba0a```
Having a look here: https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=4edafb1a473e3a0d9aa3b9498a3f5bba257aba0a I can see the path is: `proton-c/bindings/go/src/qpid.apache.org/` and I was wondering if there is a script that automatically put that code in the expected path inside $GOPATH?
Many thanks Alessio
Re: Electron/Amqp MessageAnnotations in Golang
Posted by Alan Conway <ac...@redhat.com>.
The release is scheduled to happen this week. Meantime:
The apache repo has multiple projects in different languages, so the Go
code is not in the root of the repo as go-get expects. Go get pulls the
"go1" branch, which has only the Go code in the root directory - so when we
release we merge the latest code to that branch. You can do that in your
local repo for yourself:
cd $GOPATH/src/qpid.apache.org
git checkout go1
Then follow merge instructions in readme-go-get.md:
git pull
git merge -s recursive -Xsubtree=proton-c/bindings/go/src/
qpid.apache.org master
Alternatively you can set up a GOPATH with multiple entries, one pointing
to the proton-c/bindings/go subdirectory in a complete checkout of the
master branch.
On Thu, Dec 14, 2017 at 11:55 AM, Alessio Gottardo <ta...@yahoo.it>
wrote:
>
>
> On Thursday, 9 November 2017, 20:17:41 GMT, Alan Conway <
> aconway@redhat.com> wrote:
>
>
> > Apologies for the long delay, this is a bug and was reported previously:
> > https://issues.apache.org/jira/browse/PROTON-1429
> >
> > I am fixing it now, watch the JIRA to be notified when it is fixed. You
> can
> > get the latest code direct from git, the "go get" repo will be updated
> with
> > the next release of proton, which should be fairly soon.
>
> Hi there,
>
>
> Is there any news on when this fix will be formally released?
>
>
> Otherwise is there a script to automatically fix the issues regarding the
> git repository path and $GOPATH?
>
> This approach does not make the `electron` code available to the Go
> compiler:
>
>
> ```
> go get qpid.apache.org/electron
> cd $GOPATH/src/qpid.apache.org/
> git checkout 4edafb1a473e3a0d9aa3b9498a3f5bba257aba0a
> ```
>
>
> Having a look here: https://git-wip-us.apache.org/
> repos/asf?p=qpid-proton.git;a=commit;h=4edafb1a473e3a0d9aa3b9498a3f5b
> ba257aba0a
> I can see the path is: `proton-c/bindings/go/src/qpid.apache.org/`
> <http://qpid.apache.org/>
> and I was wondering if there is a script that automatically put that code
> in the expected path inside $GOPATH?
>
>
> Many thanks
> Alessio
>
>
>
>
>