summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Update bootstrap script // fix windows issuesFred Hebert2017-12-081-28/+265
| | | | | | | | | | | | | | | | | | | | | | | | The bootstrap script has been mostly unchanged for a long period of time, and has not benefited from all the changes and improvements that rebar3 itself had, including (but not limited to) path escaping, handling of directories on windows, and edge case management when it comes to file and symlink handling. This patch brings the updates seen in rebar_string_utils, rebar_utils, and rebar_dir into the bootstrap script so that fewer people have build issues when starting from source, from scratch.
* | Merge pull request #1688 from ferd/update-manpagesFred Hebert2017-12-081-3/+13
|\ \ | |/ |/| Update manpages
| * Update manpagesFred Hebert2017-12-061-3/+13
|/ | | | New switches for cover, adding the alias provider, etc.
* Merge pull request #1686 from ferd/global-plugin-path-fixFred Hebert2017-12-067-2/+94
|\ | | | | Prevent plugin unloading from killing currently running command (soft-purge in-compile)
| * Safer purge switchFred Hebert2017-12-063-6/+9
| | | | | | | | | | | | | | | | | | Rather than the caller having to think of what to purge or not, use erlang:check_process_code/2 to detect if the caller (rebar3) may die because of the operation. If so, do a soft purge with a conditional delete instead of a hard purge with a mandatory delete.
| * Run a soft purge while within the compiler stepFred Hebert2017-12-058-3/+92
|/ | | | Prevents the killing of a plugin with itself
* Merge pull request #1685 from ferd/promote-aliasFred Hebert2017-12-058-5/+271
|\ | | | | Alias plugin promoted to built-in command
| * Alias plugin promoted to built-in commandFred Hebert2017-12-058-5/+271
|/ | | | | | | | | | - Uses the code at https://github.com/tsloughter/rebar_alias and brings it within rebar3 - adds safety checks to prevent redefining built-in commands or obvious circular dependencies between commands (indirect circular deps are still possible) - adds tests - adds a systest to ensure no clash with the existing plugin
* Merge pull request #1682 from ferd/win7-file-supportFred Hebert2017-12-041-2/+2
|\ | | | | Fix file handling on Windows 7
| * Drop the /is switch to robocopy for win7Fred Hebert2017-12-041-2/+2
| | | | | | | | Has no ill effect as tested on Win10
* | Merge pull request #1681 from ferd/fix-plugin-paths-againFred Hebert2017-12-044-3/+107
|\ \ | | | | | | Fix Plugin path handling (again!)
| * | Fix Plugin path handling (again!)Fred Hebert2017-12-044-3/+107
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The path reloading of plugins had been fixed properly, but the problem is that the paths it was using to re-load only considered the current compile step, rather than the overall state of plugins. As such, the reloaded paths after plugin compilation only reloaded the *latest* plugin and not the other ones. This fix forces the addition of all built plugin paths to the code paths after a plugin compile job is run. This ensures that the path is clean for initial plugin deps (only add those that are required), and is re-made total after the fact (add all the plugins possible). This commit also includes a system tests suite that can be run optionally; the problem with this plugin mechanism was impossible to find through mocked dependencies, and a working counterexample was provided to us. The systest suite can be run against real projects without conflict to make sure no regressions are hit.
* | Merge pull request #1679 from ferd/min-coverageFred Hebert2017-12-042-15/+92
|\ \ | | | | | | Support minimal coverage validation in tests
| * | Support minimal coverage validation in testsFred Hebert2017-12-022-15/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds an option (-m, --min_coverage, or {cover_opts, {min_coverage,X}}) to the 'cover' command, where the value is an integer between 0 and 100. If the total coverage during the analysis is below the value received, the command will fail with output like: ===> Requiring 64% coverage to pass. Only 62% obtained If the rate is correct, the command silently passes as it currently does. This feature allows to enforce code coverage standards in a project if desired.
* | | Merge pull request #1684 from tsloughter/cover-exportFred Hebert2017-12-045-7/+59
|\ \ \ | |_|/ |/| | add eunit and ct option to set coverdata file name
| * | add eunit and ct option to set coverdata file nameTristan Sloughter2017-12-045-7/+59
|/ /
* | Merge pull request #1678 from tsloughter/fix-plugin-pathFred Hebert2017-12-033-7/+32
|\ \ | | | | | | fix code path when validating plugins
| * | fix code path when validating pluginsTristan Sloughter2017-12-033-7/+32
|/ /
* | Merge pull request #1676 from jfacorro/1675.disable.color.git.logFred Hebert2017-11-291-1/+1
|\ \ | |/ |/| [Closes #1675] Disable color in git log command
| * [#1675] Disable color in git log commandJuan Facorro2017-11-291-1/+1
|/
* Merge pull request #1672 from ferd/ct-retry-reduxFred Hebert2017-11-242-4/+178
|\ | | | | Add experimental support for ct --retry option
| * Add experimental support for ct --retry optionFred Hebert2017-11-242-4/+178
|/ | | | | | | | | | | | | | | | | This commit adds a common test hook along with the cth_readable stuff whose role is to track failing test cases, and create a test specification out of them. The test specification is dumped on disk at _build/<profile>/logs/retry.spec and can be accessed by calling 'rebar3 ct --retry'. This will auto-load the spec file if it can be found and re-run the failing cases. If any other argument is found on the list specifying tests, the '--retry' argument is ignored. All code for this is marked as experimental in case we end up (keeping and then) dropping the feature.
* Merge pull request #1671 from erlang/revert-1670-ct-retryFred Hebert2017-11-242-184/+5
|\ | | | | Revert "Add experimental support for ct --retry option"
| * Revert "Add experimental support for ct --retry option"Fred Hebert2017-11-242-184/+5
|/
* Merge pull request #1670 from ferd/ct-retryFred Hebert2017-11-232-5/+184
|\ | | | | Add experimental support for ct --retry option
| * Add experimental support for ct --retry optionFred Hebert2017-11-232-5/+184
|/ | | | | | | | | | | | | | | | | This commit adds a common test hook along with the cth_readable stuff whose role is to track failing test cases, and create a test specification out of them. The test specification is dumped on disk at _build/<profile>/logs/retry.spec and can be accessed by calling 'rebar3 ct --retry'. This will auto-load the spec file if it can be found and re-run the failing cases. If any other argument is found on the list specifying tests, the '--retry' argument is ignored. All code for this is marked as experimental in case we end up (keeping and then) dropping the feature.
* Back to git-based versioningFred Hebert2017-11-221-1/+1
|
* Bump to 3.4.7Fred Hebert2017-11-223-3/+3
|
* Merge pull request #1665 from ferd/bump-cth_readable-1.3.2Fred Hebert2017-11-222-3/+3
|\ | | | | Bump cth_readable to 1.3.2
| * Bump cth_readable to 1.3.2Fred Hebert2017-11-202-3/+3
| | | | | | | | Eliminates a lager warning due to config format deprecation
* | Merge pull request #1668 from ferd/fix-make_vsn-custom-resourcesFred Hebert2017-11-221-1/+12
|\ \ | | | | | | Fix compilation for custom resources dynamic vsn
| * | Fix compilation for custom resources dynamic vsnFred Hebert2017-11-221-1/+12
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Erlang compiler runs based on a global state built from currently loaded libraries and the configured code path that is available. For this reason, the rebar3 compiler job unloads all plugin paths before calling the Erlang compiler. However, this causes a problem when an application uses a custom resource handler with a dynamic version in their .app.src file since the plugin that can be used to find the version has been unloaded. Fortunately, the compile phase that runs the version handling is distinct from the phase that uses the Erlang compiler. This patch fixes the problem by re-loading the plugins' paths in memory before generating the .app file, and before unloading them afterwards. It appears that unloading them is unnecessary because the hooks after that will re-load them, but it is likely better to play it safe with that global state and clean up after ourselves. It offers better protection for future changes. Fixes #1657
* | Merge pull request #1667 from ferd/lrascao-profile_dep_countertestFred Hebert2017-11-211-1/+18
|\ \ | | | | | | Fix broken tests
| * | Fix test mocking for profile overridesFred Hebert2017-11-211-2/+4
| | |
| * | Merge branch 'profile_dep_countertest' of https://github.com/lrascao/rebar3 ↵Fred Hebert2017-11-211-0/+15
| |\ \ |/ / / | | | | | | into lrascao-profile_dep_countertest
| * | Profile deps counter testLuis Rascao2017-10-161-0/+15
| | |
* | | Merge pull request #1666 from tsloughter/relx-3.24.3Fred Hebert2017-11-212-3/+3
|\ \ \ | | | | | | | | upgrade relx to 3.24.3
| * | | upgrade relx to 3.24.3Tristan Sloughter2017-11-212-3/+3
|/ / /
* | | Merge pull request #1656 from ferd/unconfuse-debug_infoFred Hebert2017-11-212-6/+60
|\ \ \ | | | | | | | | Make debug_info rules clear
| * | | Make debug_info rules clearFred Hebert2017-11-202-6/+60
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current rebar3 uses debug_info rules where debug_info is added by default, and no_debug_info prevents the default from being added, and removes any explicit debug_info, if any. The problem is that if 'no_debug_info' is anywhere in the config for a run, it cannot be removed even with other profiles. additionally, no_debug_info ignores special tuples like {debug_info, {Mod, Data}} and {debug_info_key, Key}, which can be used to add debug info and encrypt it (in lieu of plain debug_info) respectively. This patch makes it so that the following rules are in place: - the last option seen takes priority, allowing profile overrides by the ordering rules the compiler expects - the overriden options shall be explicitly deleted to avoid confusing the compiler - any option related to debug info seen last cancels any no_debug_info that preceded it - any no_debug_info option seen last cancels all of the other debug_info options - if debug_info is seen last, it cancels out {debug_info_key, Key} - if {debug_info_key, Key} is seen last, it cancels out debug_info - All other options are left untouched in that context (defines can still be expanded and so on) This should allow proper profile rules to be followed. Note that erl_opt profile merging puts precedence on the *last* element of a list, to match the compiler.
* | | Merge pull request #1664 from liamjjmcnamara/quiet_dep_skippingFred Hebert2017-11-201-2/+7
|\ \ \ | |_|/ |/| | Allow silencing skip warnings when fetching deps
| * | Allow silencing skip warnings when fetching depsLiam McNamara2017-11-201-2/+7
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When fetching deps, if this is a clean repo there will be extensive messages warning that dependencies which have already been fetched are being skipped. For large projects being built and tested in a clean environment this significantly increases the noise level of the build. This modification adds an additional rebar option (deps_warning_on_conflict) that will allow disabling these warning messages. If deps_error_on_conflict is set, an error will still be thrown. This will not change default behaviour of rebar. There is a similar outstanding issue: https://github.com/erlang/rebar3/issues/1105 However this seems to be a push for not outputting warnings when the dep version is the same, rather than disabling warnings altogether.
* | Back to git-based versioningFred Hebert2017-11-171-1/+1
| |
* | Bump to 3.4.6Fred Hebert2017-11-172-2/+2
| | | | | | | | Updates relx (windows fixes) and erlware commons (strings)
* | Merge pull request #1662 from tsloughter/up-ec-1.0.4Fred Hebert2017-11-172-6/+6
|\ \ | | | | | | upgrade relx and erlware commons
| * | upgrade relx and erlware commonsTristan Sloughter2017-11-172-6/+6
|/ /
* | Return to git-based versioningFred Hebert2017-11-171-1/+1
| |
* | Bump to 3.4.5Fred Hebert2017-11-172-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - OTP-21 readiness, Full Unicode support, massive dep upgrade - fixed handling of proxy username and password when fetching registry - git versions from tag made consistent and all strip 'v' prefix - Prevent hard crash on duplicate plugin paths - Fix include paths in profile multiapp edge case - Fix unlock state carry, which broke do sequences with unlock in them. - Avoid guessing on utf8 decoding of app files - Various fixes related to .app files - Warn user when an unsupported local git or hg resource is used - Corrects a fix to src_dir values - Update eunit_formatters to latest version - Changes in wording of warnings for more accuracy
* | Merge pull request #1660 from ferd/otp-21-preparednessFred Hebert2017-11-1629-86/+143
|\ \ | | | | | | OTP-21 readiness, Full Unicode support
| * | OTP-21 readiness, Full Unicode supportFred Hebert2017-11-1629-86/+143
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This replaces all deprecated function usage by alternative ones based on a version switch enacted at compile time, preventing all warnings. This will likely introduce some possible runtime errors in using a Rebar3 compiled on OTP-20 or OTP-21 back in versions 19 and earlier, but we can't really work around that. A bunch of dependencies have been updated to support OTP-21 without warnings as well.
generated by cgit v1.1 at 2024-12-29 19:24:30 +0000