riak_pb_messages.beam does not get built with a current rebar version [JIRA: RIAK-1555]

[hanikesn]

Try cloning the riak_pb repo two times. The first time build it with the included rebar binary, the second time build it with the rebar executable from https://raw.github.com/wiki/rebar/rebar/rebar.

The second time riak_pb_messages.beam does not get build, because the riak_pb_msgcodegen plugin is not used correctly.

This could also be an issue with rebar itself.

[binarytemple]

I'm also having problems building a test application getting a warning message:
WARN: Missing plugins: [riak_pb_msgcodegen]

In rebar.config, I even explicitly specified the riak_pb dependency. The original is there as well, I know that because I got a version mismatch (which I corrected)

%%-*- mode: erlang -*-

{erl_opts, [
            {src_dirs, ["./src"]},
            {parse_transform, lager_transform}
           ]}.

{deps, [
        {lager,  "2.0.*", {git, "git://github.com/basho/lager.git", "master"}},
        {riakc, ".*", {git, "git://github.com/basho/riak-erlang-client", "master" }},
        {riak_pb, ".*", {git, "git://github.com/basho/riak_pb", {tag,"2.0.0.16"}  }}
]}.
{plugins, [riak_pb_msgcodegen]}.
{require_otp_vsn, "R1[456]"}.

[HashNuke]

This issue needs some love.

riak_pb comes with an old pre-release version of rebar. Something must have changed about the way rebar handles plugins (the API for which is undocumented and is still in flux according to this issue https://github.com/rebar/rebar/issues/104).

[HashNuke]

@hanikesn @binarytemple @kellymclaughlin

I fixed this in a pull request #101.

• Build is green - https://travis-ci.org/HashNuke/riak_pb/builds/34477607
• Patch is in this branch, if anyone wants to use it - https://github.com/hashnuke/riak_pb/tree/plugin-fix-for-rebar-2.5.1

[DeadZen]

+1 get this thing merged in before it bit rots any further...

[Basho-JIRA]

[~seancribbs] please review and assign according to what you find out.

_[posted via JIRA by Derek Somogyi]_

[DeadZen]

w00t

[cmeiklejohn]

I've merged these changes into #110 to have a resolved build. I suggest we merge #110 and close this PR.

[seancribbs]

This was resolved by #110.