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

Use direct path to rake file #332

Merged

Conversation

stevenharman
Copy link
Contributor

@stevenharman stevenharman commented Feb 23, 2017

Before this, we were relying on the Gem's lib dir being on the $LOAD_PATH, and thus load would find the tasks/doc.rake file. This can break when a different gem also has a tasks/docs.rake file, and it's further up in the load path. Same goes for a Rails app with a tasks/docs.rake file existing. This ensures we get OUR tasks/docs.rake file.

Before this, we were relying on the Gem's `lib` dir being on the
$LOAD_PATH, and thus `load` would find the `tasks/doc.rake` file. This
can break when a different gem also has a `tasks/docs.rake` file, and
it's further up in the load path. Same goes for a Rails app with a
`tasks/docs.rake` file existing. This ensures we get OUR
`tasks/docs.rake` file.
@stevenharman stevenharman force-pushed the use_correct_path_to_rake_tasks branch from 44ce5ce to d18a203 Compare February 24, 2017 03:41
@oestrich
Copy link
Contributor

Thanks!

@oestrich oestrich merged commit bcc806d into zipmark:master Feb 28, 2017
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.

2 participants