Remove hoe from development #396
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
@zzak I switched bundler's task from hoe on rake repository. see ruby/rake#122 |
zzak
pushed a commit
to rails/sdoc
that referenced
this pull request
Jul 14, 2016
Since ruby/rdoc#396 is merged, this is much easier and we can remove the rdoc-install scripts from this gem. /cc #80
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to remove hoe to make it easier for testing plugins and third-party extensions against master.
Removing hoe will simplify the Rakefile and reduced the number of dependencies we have to maintain.
This also allows testing extensions and plugins easier, but also contributors will have a much more familiar workflow to contribute; which IMO is the biggest benefit and worth the complexity of moving parser generation onto our Rakefile.