You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a gem that I need to test against completely different sent of dependencies. There no such thing as "default" dependencies.
So, I've generated 4 Gemfiles with appraisal and would like to use one of them as a default, so when I run rake it'll actually lanch something like appraisal:default_gemset test. Actually, even appraisal rake task would be ok for default.
Yeah, I can feel your pain there. I'm working on making Appraisal to be a standalone executable so we can cut out this Rake invocation tree. In the meantime, I'd suggest you to look at our setting in Paperclip which I think might work for you.
I'm going to keep this open until I can fix this behavior. Thanks for reporting in.
I have a gem that I need to test against completely different sent of dependencies. There no such thing as "default" dependencies.
So, I've generated 4 Gemfiles with appraisal and would like to use one of them as a default, so when I run
rake
it'll actually lanch something likeappraisal:default_gemset test
. Actually, evenappraisal
rake task would be ok for default.Unfortunately this doesn't work.
In my Rakefile I have this:
when I run
rake
i see this stacktrace:The text was updated successfully, but these errors were encountered: