Use activesupport gem rather than active_support #3
Conversation
This file contains 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
|
No, that's not intentional. You used to be able to refer to activesupport either way, until an actual active_support gem was published, apparently. Merging. |
tobias
added a commit
that referenced
this pull request
Dec 13, 2011
…active_support Use activesupport gem rather than active_support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey
Not sure if it is intentional or not but the Gemspec includes a dependency for the active_support gem. As far as I am aware, all this does is set a hard dependency on activesupport 3.0.0 which is the gem that has all the code.
So as it stands you cannot use the gem with rails 3.1