`rebar3 path' provider

[talentdeficit]

prints requested paths to stdout based on current profile

usage:

$ echo `rebar3 path`
/Users/talentdeficit/dev/erlang/rebar/_build/default/lib/ssl_verify_hostname/ebin /Users/talentdeficit/dev/erlang/rebar/_build/default/lib/relx/ebin /Users/talentdeficit/dev/erlang/rebar/_build/default/lib/providers/ebin /Users/talentdeficit/dev/erlang/rebar/_build/default/lib/getopt/ebin /Users/talentdeficit/dev/erlang/rebar/_build/default/lib/erlware_commons/ebin /Users/talentdeficit/dev/erlang/rebar/_build/default/lib/bbmustache/ebin /Users/talentdeficit/dev/erlang/rebar/_build/default/lib/rebar/ebin
$ echo `rebar3 path --base`
/Users/talentdeficit/dev/erlang/rebar3/_build/default
$ echo `rebar3 path --app=rebar,providers --ebin --seperator=","`
/Users/talentdeficit/dev/erlang/rebar3/_build/default/lib/rebar/ebin,/Users/talentdeficit/dev/erlang/rebar3/_build/default/lib/providers/ebin

[tsloughter]

@ferd any thoughts on this?

@talentdeficit you'll need to add path to the README and shell completions.

[ferd]

I'm wondering what's the intended use case for this? I'm fine adding it in depending on the rationale and the low chance of breakage, but I just need to understand what this is needed for?

[talentdeficit]

mostly so you can do:

erl -pa `rebar3 path`