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

Continue with Rails3 and start fixing Remarkable slowly #21

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

jeroenvandijk
Copy link

Hi guys,

I did a big refactoring of the gemspecs and I cleaned up the Rakefiles. I also marked all (52) examples that are failing as pending so people can fix them one by one. You guys might not agree with everything I have changed, but I do think that these commits can bring Remarkabe back to live.

I'll continue with fixing the failings specs. Most of them are due to changes in ActiveRecord.

Please let me know if you have suggestions to improve things.

Jeroen

- Refactored Gemspecs created by Jeweler so it is useable for Bundler
- Renamed remarkable to remarkable_core so we can have a remarkable wrapper gem
- Moved the Rails, Rspec and Remarkable versions to seperate files to make things DRY
- remove all tests that were meant for older Rails version before 2.3
- remove all RAILS_VERSION guards
- add pending block around that were failing due to the lack of guards
When running tests we now rely on Bundler and not some combination of Rubygems and Jeweler

50 remarkable_activerecord specs are now failing due to the upgrade of Rails from 3.0.0.beta3 to 3.0.3
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.

1 participant