When the deprecation toolkit get installed, it ends up in
somewhere in the GEM_PATH.
If you have a project that doesn't use bundler (like minitest itself),
then all minitest plugins found in the GEM_PATH will get loaded.
This is problematic because we don't want to run the deprecation_toolkit
on projects that didn't specify it.
This problem only happens on project not using bundler, because
otherwise, gems not part of the snapshots don't end up in the
load_path and thus the minitest plugin don't kick in.
Fix Minitest plugin kicking in when it shouldn't:
When the deprecation toolkit get installed, it ends up in somewhere in the GEM_PATH.
If you have a project that doesn't use bundler (like minitest itself), then all minitest plugins found in the
GEM_PATHwill get loaded. This is problematic because we don't want to run the deprecation_toolkit on projects that didn't specify it.This problem only happens on project not using bundler, because otherwise, gems not part of the snapshots don't end up in the load_path and thus the minitest plugin don't kick in.