Conversation

stevenharman

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.
@stevenharmanstevenharman force-pushed the use_correct_path_to_rake_tasks branch from 44ce5ce to d18a203 Compare February 24, 2017 03:41
@oestrich

Thanks!

@oestrichoestrich merged commit bcc806d into zipmark:master Feb 28, 2017
Sign up for free to join this conversation on . Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.