Rake 12.0.0 causes Flay 2.8.1 to fail; failure does not occur with Rake 11.3.0

Open jdickey opened this issue 8 years ago • 4 comments

See this comment on seattlerb/flay#69.

Using any configuration of Flay when running multiple Rake tasks (e.g., as by default) causes any non-default dirs option value to be ignored. This does not happen when the same Makefile and source files are run against rake 11.3.0. Running bin/rake flay by itself does not have that problem when running rake 12.0.0.

Feb 18 '17 17:02 jdickey

I think it might be rake not clearing ARGV anymore, facing some similar problems

Aug 18 '17 21:08 Fire-Dragon-DoL

@Fire-Dragon-DoL That's not even documented anywhere as a gotcha, is it, let alone a workaround? Closest I saw was #11, and that's ancient.

Looks like we'll be on 11.3.0 for some time to come.

Aug 20 '17 05:08 jdickey

Well, as a workaround I do ARGV.pop at top of my rakefile

Aug 20 '17 07:08 Fire-Dragon-DoL

Thanks; I'll give that a try.

Aug 20 '17 13:08 jdickey