Closed deepankar-j closed 2 years ago
Not sure what tooling you use here (only normal Mix? Which version?) but I don't think Meck is involved in putting any files anywhere (that's the department of Rebar and Mix).
It looks like an interaction between Mix and its building of Rebar-based software. Perhaps check with the Elixir community? I would imaging any Rebar-based dependency to have this problem in your setup. Meck is not special in this way.
Okay, thanks @eproxus. Yes, I'm using normal mix (v1.12.2). I'll check elsewhere.
@deepankar-j Let me know if you need any further assistance.
When using meck as a dependency and running compilation on our application, we've noticed that meck compilation results in files under deps/meck being updated, along with files under _build//lib/meck. This causes an issue for caching prebuilt dependencies (especially in Docker) because it's not obvious that artifacts need to be preserved from under
deps/meck
. Once I noticed this issue, I worked around it by caching thedeps/meck
folder. However, I'm sure others will be tripped up by this problem as well.Reproduction Steps
mix deps.compile
deps/meck/*
files.Expected behavior
All generated files should be under
_build/<env>/lib/meck
.Observed behavior
The following files/folders are modified/created within
deps/meck
.Versions
Mac OS X 11.6