Serge Aleynikov

I put together [this example](https://github.com/saleyn/rebar-test) to illustrate the issue. There are two branches there `working` and `not-working`. ```bash $ tree ├── one │   ├── rebar.config │   └── src │   ├──...

@tsloughter, possibly you are right, the issue is with my use of `$REBAR_BUILD_DIR` as the target location of the Elixir's beam files. If that's the case, how would you suggest...

Somewhat unrelated, but is there an option in rebar to specify that a dependency is compile-only? E.g. if project `one` in this case is dependent on `parse_trans`, which is only...

Indeed, the current approach doesn't seem to be portable, as the project shouldn't care about the method a dependency is defined (i.e. _checkouts, path, git, etc). Sounds like an oversight.

I have one more test case in question that doesn't involve `_checkouts`, where there is an Elixir project [three](https://github.com/saleyn/rebar-test/tree/three/three) referencing an Erlang project [one](https://github.com/saleyn/rebar-test/tree/three/one) which has a rebar clause to...

Is there a workaround for the test case above that I can use with the current version of the `rebar3` to be able to compile a mixed Erlang/Elixir project by...

Thanks @ferd. Maybe it would be better for rebar to set `REBAR_BARE_COMPILER_OUTPUT_DIR` env to `$REBAR_BUILD_DIR/lib/one/ebin`, if not already set? This way the projects would not have to deal with this...

I guess the alternative is to introduce another variable (e.g. "REBAR_PROJECT_OUTPUT_DIR"?) that would be set to the target location of the current project's output directory. It would check for the...

My objective is to be able to bundle a mix of Erlang/Elixir modules in one app, and make sure that if used as a dependency the app can be properly...

That does work, though I would assume that the intention of the REBAR_COLOR was to remove all color escaping chars including bold, no? Do you know if there is a...