| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Add OTP 19.0 to travis
|
|/ |
|
|\
| |
| | |
Avoid PLT rebuild when files deleted on new dialyzer
|
|/ |
|
|\
| |
| | |
Handle empty PLT or app when using dialyzer
|
| | |
|
|/ |
|
|\
| |
| | |
Escriptize based on configured apps only
|
| |
| |
| |
| | |
Used a nonexisting option instead of a correct one
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this patch, the escriptize command flat out selected all
declared dependencies.
This patch instead looks at the app files and only includes the
dependencies of the top level app and the extra ones, avoiding to
package more apps than required.
This required a version bump on cth_readable as it mistakenly included
'syntax_lib' instead of 'syntax_tools' as a dependency.
|
|\ \
| |/
|/| |
Fixes for windows environment: 1) copy empty directories when cloning…
|
|/
|
|
| |
git occasionally has a refs directory with no files in it - if the directory is not present, then git does not believe it is a git repo) and 2) change order of git rev-parse arguments to match git docs
|
|\
| |
| | |
lock file contains expected hash for pkg dependencies
|
| |
| |
| |
| |
| | |
This uses the env variable as a global store for variables. It's not the
cleanest thing, but it sounded nicer than pdicts.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reworks the version and hash printing in the lockfile to minimize
diff changes:
- the version is on its own line so that the locks are mostly the same
aside from the last line
- the hashes are each printed on one line with the package name for
simpler diffing too.
|
| | |
|
| |
| |
| |
| | |
- also making sure unlocking works fine
|
| |
| |
| |
| |
| | |
Tests have broken as locks were expanded and auto-filled newer versions
of lockfiles. This fixes them back.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- the internal representation for package locks moves from `{Name, {pkg,
PkgName, Vsn}, Lvl}` to `{Name, {pkg, PkgName, Vsn, Hash}, Lvl}`
- the internal representation for packages moves from `{pkg, PkgName,
Vsn}` to `{pkg, PkgName, Vsn, Hash}`
- the hash can be `undefined`, meaning no check will be done
- no checking is done yet.
|
|\ \
| | |
| | | |
Let DEBUG="" and QUIET="" mean disable the option
|
| | |
| | |
| | |
| | |
| | | |
Setting DEBUG/QUIET environment variable to the empty string now acts
the same as unsetting it. Unsetting is not always easy/possible.
|
|\ \ \
| | | |
| | | | |
use logs rather than skimming github pages
|
|/ / / |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Fix unicode rendering of deps tree (issue #1140)
|
|/ / |
|
|\ \
| | |
| | | |
ignore return value of `rebar_utils:reread_config` in shell provider
|
|/ / |
|
|\ \
| | |
| | | |
normalize include dirs to absolute paths during compilation
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
changed include files were not properly picked up by `erlc_compiler`
in cases where they were in directories relative to the application
source and not the current working dir of rebar3
fixes #1199
|
|\ \
| | |
| | | |
REBAR-1184 always recompile if `ERL_COMPILER_OPTIONS` env var is set
|
| | | |
|
| | |
| | |
| | |
| | | |
partially addresses #1184
|
|\ \ \
| | | |
| | | | |
Compiler source paths in output are now relative
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This required moving the reporting functions to rebar_base_compiler but
since this was already done for error_tuple, this seems to make sense.
Paths are also reformatted for warnings in erlc files.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This will allow us to eventually change the default type without it
looking ridiculous.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
By default rebar3 displays compiler sources as absolute paths in their
original location, which is under the build dir.
This change introduces an option 'compiler_source_format' to format
sources in two alternative ways:
relative
absolute
When either 'relative' or 'absolute' are specified, the file is
resolved to its original location when it is a link. When 'relative'
is specified, the path is displayed relative to the current working
directory. When 'absolute' is specified, the path is absolute.
The default value is 'unchaged' which leaves the compiler source
unchanged.
This is arguably too flexible as I suspect most people would opt for
'relative' all the time - it's the most compact representation of the
file and is sufficient to find the source given cwd. The change
however is meant to introduce the change gradually, preserving
existing behavior and giving users a choice for formats.
In time perhaps the default can be changed to 'relative' - but still
allowing users to revert to the other two options ('absolutel' and
'unchanged') as needed.
|
|\ \ \ \
| |_|/ /
|/| | | |
add support for passing a sys_config to common test
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Expand os ENV proxy support to bootstrap script
|
| | | | |
|
|\ \ \ \
| |/ / /
| | | | |
Support ENV config for proxy values
|
|/ / /
| | |
| | |
| | |
| | | |
- The configured stuff in rebar3 takes precedence over the ENV
- The env is then chosen
|