In particular, this release solves a bug in umbrella projects / path dependencies. So if your project failed to compile in the previous RC, please give this one a try. Let us know in the comments if you found any bugs or if everything worked out fine.
You can either compile the v1.7 branch from source OR use the precompiled files, as described in our install page.
Note that you will need {:ex_doc, "~> 0.19-rc"} if you want to generate docs using the release candidate.
Whats the guidance on updating libs to use the new @doc metadata tags? When I update a project to 1.7.0-rc.* I get compiler warnings with @since and @deprecated (fine). If however I move to the new @doc since: "new version" I get compiler errors on current and older releases (as expected)
Does this mean I have to use conditional compilation to be backwards compatible without errors and warnings?
Its not hard deprecated - it just emits compiler warnings. Since this is a lib that others use I try hard to remove all warnings since, to a consumer, it looks like an uncaring developer and smelly code. Hence why I’m picky.
I have four applications that work together using path dependencies (not using umbrella). The apps were working okay in 1.6.6, but would not start under the 1.7.0-rc.0 release. They are working again with the 1.7.0-rc.1 release. Thank you!
I’ve been using 1.7 branch as my development environment since before rc.0. So far it’s working great (tested on 3 umbrella projects). The only problem I stumbled into was absinthe failing to compile specs (already fixed btw.)
Thanks everyone for the feedback! We shall release the final version tomorrow, so if you haven’t given it a try yet, don’t forget to do it in the next 24 hours.
