Use ./bin/jruby instead of bin/jruby

mohamedhafez · web-flow · commit 35e5d77bad66 · 2024-12-20T19:25:32.000+01:00
The extra dot removes having PATH set a particular way
diff --git a/BUILDING.md b/BUILDING.md
@@ -117,14 +117,14 @@ For normal day-to-day testing, we recommend running the Ruby specs. We have set
 "fast" grouping that takes only a couple minutes to run:
 
 ```
-bin/jruby -S rake spec:ruby:fast
+./bin/jruby -S rake spec:ruby:fast
 ```
 
 For a more intensive workout, you can also run the Ruby (MRI) tests
 via the following rake command:
 
 ```
-bin/jruby -S rake test:mri
+./bin/jruby -S rake test:mri
 ```
 
 This suite takes a while to complete, so if you want to run an individual file
@@ -135,7 +135,7 @@ from MRI's tests (under test/mri), use one of the following commands:
 The MRI suite (under `test/mri`) has a runner script in `test/mri/runner.rb` that sets up
 an appropriate test environment. Many of the MRI tests will need to be run via this script.
 ```
-bin/jruby test/mri/runner.rb test/mri/<path to test>
+./bin/jruby test/mri/runner.rb test/mri/<path to test>
 ```
 
 You can pass `-v` to the runner for verbose output or `-n test_method_name` to only run a single test method.
@@ -149,7 +149,7 @@ Excludes are in the form of Ruby scripts under `test/mri/exclude`, named based o
 To run a given test with these excludes enabled, you can use the --excludes flag:
 
 ```
-bin/jruby test/mri/runner.rb --excludes=test/mri/excludes <test file>
+./bin/jruby test/mri/runner.rb --excludes=test/mri/excludes <test file>
 ```
 
 #### Run a single spec using RSpec
@@ -161,7 +161,7 @@ The notable exception is the "Ruby specs" under spec/ruby, which are run with ms
 rspec will be installed with `mvn package -Pbootstrap` or you can install it manually.
 
 ```
-bin/jruby -S rspec spec/path/to/spec
+./bin/jruby -S rspec spec/path/to/spec
 ```
 
 #### Run a single "Ruby spec" using mspec
@@ -171,7 +171,7 @@ The specs under spec/ruby are part of the "Ruby spec" suite of tests and use the
 Individual specs can be run with the mspec tool:
 
 ```
-bin/jruby spec/mspec/bin/mspec ci spec/ruby/<path to spec>
+./bin/jruby spec/mspec/bin/mspec ci spec/ruby/<path to spec>
 ```
 
 If `ci` is omitted or replaced with `run` you will see any specs known to fail. The `ci` command
@@ -183,7 +183,7 @@ If you are familiar with Java debuggers, you can attach one to a JRuby process u
 The exact flag may vary with debugger and platform:
 
 ```
-JRUBY_OPTS="-J-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=localhost:5005" bin/jruby <rest of arguments>
+JRUBY_OPTS="-J-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=localhost:5005" ./bin/jruby <rest of arguments>
 ```
 #### JRuby internal unit tests
 
