Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(maint) Only load rubocop rake tasks if gem is available #187

Merged
merged 1 commit into from
Feb 28, 2017

Conversation

glennsarti
Copy link
Contributor

Previously in commit 145ecb4 Rakefile was modified to require the Rubocop
gem however, this gem is not available on jruby systems and would throw errors.
This commit modifies the Rakefile to first detect if the Gem is available and
optionally load the rubocop rake tasks.

Previously in commit 145ecb4 Rakefile was modified to require the Rubocop
gem however, this gem is not available on jruby systems and would throw errors.
This commit modifies the Rakefile to first detect if the Gem is available and
optionally load the rubocop rake tasks.
@mckern
Copy link
Contributor

mckern commented Feb 22, 2017

Should we add a corresponding confinement for the Rubocop gem in Gemfile?

@glennsarti
Copy link
Contributor Author

The Gem is already confined to the MRI and Windows x64 platforms which is what caused the Travis failures in the first place (jruby was failing)

@mckern
Copy link
Contributor

mckern commented Feb 23, 2017

works for giant man

@shrug shrug merged commit dbd16eb into puppetlabs:master Feb 28, 2017
@glennsarti glennsarti deleted the fix-rakefile-for-ruby branch March 1, 2017 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants