aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler/cli/exec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Warn if executable in bundle exec is emptybronzdoc2016-10-301-0/+6
|
* Add a setting for disable_exec_loadSamuel Giddins2016-08-161-1/+3
|
* [Exec] Only set process title on Ruby 2.1+Samuel Giddins2016-08-101-7/+3
| | | | The Process method is not available before then
* Manually set a process title when using loadJames Healy2016-08-091-0/+9
| | | | | | | | | | | | | | | | | | | | With bundler 1.11.2, the process name for rake tasks looked like this: $ bundle exec rake foo:bar $ ps ux | grep rake user 1758 62.2 2.4 385816 202032 pts/3 Sl+ 16:16 0:04 ruby /usr/bin/rake foo:bar On bundler 1.12.0, the process name changed: $ bundle exec rake foo:bar $ ps ux | grep rake user 1758 62.2 2.4 385816 202032 pts/3 Sl+ 16:16 0:04 /usr/bin/rake The change in behaviour is caused by bundler 1.12 using `load` (instead of `exec`) where possible, and manually using `$0=` to set the command name. Unfortunately, that also alters the process title visible with ps, and using Process.setproctitle can help reverse that
* JRuby in 1.8 mode doesn't support Array as first argument for Kernel.execojab2016-07-161-1/+5
| | | | Fixes #4586
* Add JRuby shebang to ruby_shebang? checkojab2016-07-161-0/+1
| | | | It allows commands to be executed via `.kernel_load` on JRuby
* Fixing the reserved signals and hash valueAsutosh Palai2016-06-271-1/+4
|
* Wiping all possible signalsAsutosh Palai2016-06-271-1/+1
|
* Fixes #4568Asutosh Palai2016-06-271-0/+1
|
* [Exec] Allow executables to exit non-zero via at_exitSamuel Giddins2016-04-141-2/+1
|
* Add test for checking langauge of sentences used in source codeAditya Prakash2016-03-091-1/+1
|
* [RubygemsIntegration] Add support for new activate_bin_path binstubsSamuel Giddins2016-03-051-1/+2
|
* [Exec] Fix loading on 1.8.7Samuel Giddins2016-02-231-1/+1
|
* [Exec] Improve performance when checking for a ruby shebangSamuel Giddins2016-02-221-2/+6
|
* [Exec] Filter bundler code from backtrace when load failsSamuel Giddins2016-02-221-1/+2
|
* [Exec] Set $0 when loadingSamuel Giddins2016-02-221-0/+1
|
* [Exec] Ensure failure loading is printed to STDERRSamuel Giddins2016-02-221-2/+1
|
* [Exec] Load instead of exec-ingSamuel Giddins2016-02-221-11/+42
|
* [Exec] Avoid loading the definition before exec-ingSamuel Giddins2016-02-011-9/+3
|
* Compatibility with frozen string literalsSamuel Giddins2016-01-311-0/+1
|
* [Exec] Fix exec-ing with 0 args in a directory with spacesSamuel Giddins2016-01-251-1/+1
|
* Deal with ENOEXECFelipe Tanus2015-11-301-1/+1
|
* Remove parenthesisJustin Lambert2015-08-051-1/+1
|
* Fix for warning on jruby 9kJustin Lambert2015-08-051-1/+1
| | | | | | | Jruby 9k is ruby 2.2.2, but doesn't support processes. So running `bundle exec` leads to a warning `warning: unsupported exec option: close_others`. This should fix that warning.
* Fix Style/SingleSpaceBeforeFirstArgErick Sasse2015-07-191-1/+1
|
* [RuboCop] Enable Style/StringLiteralsSamuel E. Giddins2015-07-151-1/+1
|
* [RuboCop] Enable Style/EmptyLinesSamuel E. Giddins2015-07-151-1/+0
|
* Removes a warning in jrubyDavid Rodríguez2015-07-111-1/+3
| | | | | | | | | | | | | It seems that jruby's exec does not understand that option: ``` uri:classloader:/jruby/kernel/kernel.rb:28: warning: unsupported exec option: close_others ``` The warning was skipped for rubies under 2.0 (like latest released jruby) but the new jruby 9.0.0.0 is 2.0 compatible by default so the check needs to be refined.
* Unset UI when yielding to other programsSamuel E. Giddins2015-06-021-0/+6
|
* share bundle env setup between exec and RuntimeAndre Arko2015-01-191-52/+17
| | | | | this means we only have to maintain setting up Bundler environment variables in one place
* force TTY only in tests instead of all execAndre Arko2015-01-191-2/+1
|
* Optimized bundle-execKir Shatrov2015-01-191-12/+55
| | | | | (from https://trello.com/c/bf90QcsN/66-exec-as-soon-as-possible) Right now the exec command loads the entire Gemfile, the entire lockfile, resolves the gemfile against the lockfile, and then execs. Instead, let's check $PATH for the exec command and exec instantly if it's there.
* whitespace styleAndre Arko2014-01-261-0/+1
|
* Refactored open and fixed few failing specsSmit Shah2014-01-081-1/+1
|
* Use *args instead of argsSmit Shah2014-01-081-1/+1
|
* Refactored exec method in cliSmit Shah2014-01-081-0/+36