rebar3.git - Clone of https://github.com/erlang/rebar3

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix rebar3 dialyzer warnings	Fred Hebert	2016-11-19	1	-1/+1
\| \| \| \|	Some tricky changes in there but should be okay
*	Add support for behaviors, and not just behaviours	Brujo Benavides	2016-09-28	1	-1/+2
\|
*	Add support for xref_ignores	Louis-Philippe Gauthier	2016-02-12	1	-10/+12
\|
*	fix dialyzer warnings, except 'no local return' warnings	Tristan Sloughter	2015-08-08	1	-1/+1
\|
*	fix bareness issues	Fred Hebert	2015-05-31	1	-1/+1
\| \| \| \| \| \|	- Crashes in providers lib when no providers in a namespace are bare - Making sure bareness matches semantics; i.e. a bare provider is visible, a non-bare provider is hidden.
*	remove uses of 'case catch'	Tristan Sloughter	2015-05-10	1	-5/+5
\|
*	real bootstrapping	Tristan Sloughter	2015-04-22	1	-1/+1
\|
*	track and cleanup code paths for different contexts	Tristan Sloughter	2015-04-21	1	-17/+5
\|
*	Fixes #306: help text consistency	Fred Hebert	2015-04-02	1	-1/+1
\|
*	Fix dialyzer warnings	James Fish	2015-03-18	1	-1/+1
\|
*	use PRV_ERROR for formattable errors	Fred Hebert	2015-03-16	1	-1/+2
\| \| \| \|	Also expose it in rebar_api
*	copy project apps to deps output dir for compilation	Tristan Sloughter	2015-02-28	1	-1/+0
\|
*	Add xref support for multi-app projects	Kelly McLaughlin	2015-02-05	1	-1/+2
\| \| \| \| \| \| \|	Add xref support for multi-app projects. Instead of only adding the top-level ebin directory to the xref server use rebar_state:project_apps/1 to enumerate the applications for the project and add the ebin directory for each one.
*	Add xref provider for cross reference analysis	Kelly McLaughlin	2015-02-05	1	-0/+296
	* Add a provider for the xref tool for running cross reference analysis on a project. Most of the code has been ported directly from the rebar2 rebar_xref module with some modification and cleanup to support testing. * Port over the eunit test suite from rebar2, but convert it to common_test. The testing is the same, but now the erlang term output is examined to determine if the test run is successful instead of scanning the console output for the expected strings.