Closed jasnow closed 5 years ago
If you could add the follow-up errors, too, it'd help diagnosing.
<details>
is a tag you can use around long listings, if you have many of them and want to keep legibility.
Hope this helps!
The paths seem to have changed:
require 'aruba/spawn_process'
=> require 'aruba/processes/spawn_process'
There is a documentation warning on this line, about usage of this private API:
https://github.com/cucumber/aruba/blob/master/lib/aruba/processes/spawn_process.rb#L15
I took a look at the offending file, and it looks like those lines were added by Aruba's installer. I'll try to verify this later, but I think we should update these files in 0.14.x to emit deprecation messages when they're required.
@mvz - OK
The 0.14.10 release will now warn about requiring these files.
@jasnow: Getting this error for rake on one of my repos after upgrading to alpha.4:
Run fine on current aruba gem release.
@mvz: Hm .. that file is deprecated in the current release. Are you using the InProcess runner or just requiring that file somewhere?
@jasnow: "in_process" still works (no error or message) in gem release 0.14.9.
@mvz: That means you're not actually using the InProcess class defined there. I indeed noticed that requiring that file in 0.14.9 won't print a deprecation message, whereas instantiating Aruba::InProcess will. It probably should complain when required, but for using the alpha.4 release, you can just remove the require.
To help me find out where we need to improve deprecation messaging, do you know why you added a require for this particular file?