2012-11-08 14:51:18 -05:00
version = File . read ( File . expand_path ( '../RAILS_VERSION' , __FILE__ ) ) . strip
2010-03-01 23:36:54 -05:00
2009-08-31 20:20:44 -04:00
Gem :: Specification . new do | s |
2010-02-03 20:59:39 -05:00
s . platform = Gem :: Platform :: RUBY
s . name = 'rails'
2010-03-04 22:41:39 -05:00
s . version = version
2010-03-02 13:32:09 -05:00
s . summary = 'Full-stack web application framework.'
s . description = 'Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.'
2010-04-01 16:46:04 -04:00
2015-03-09 04:55:11 -04:00
s . required_ruby_version = '>= 2.2.1'
2012-11-08 14:51:18 -05:00
s . required_rubygems_version = '>= 1.8.11'
s . license = 'MIT'
2010-02-03 20:59:39 -05:00
2012-03-17 11:32:49 -04:00
s . author = 'David Heinemeier Hansson'
s . email = 'david@loudthinking.com'
s . homepage = 'http://www.rubyonrails.org'
2010-04-12 18:09:40 -04:00
Remove documentation tasks
This patch removes the tasks doc:app, doc:rails, and doc:guides.
In our experience applications do not generate APIs using doc:app.
Methods may be certainly documented for maintainers, annotated
with YARD tags, etc. but that is intended to be read with the
source code, not in a separate website. Then, teams also have
typically selected topics written down in Markdown files, or in
a GitHub wiki... that kind of thing.
If a team absolutely needs to generate application documentation
for internal purposes, they can still easily write their own task.
Regarding doc:rails and doc:guides, we live in 2015. We are used
to go to online docs all the time. If you really want access to the
API offline RubyGems generates it for every Rails component unless
you tell it not to, and you can checkout the Rails source code to
read the guides as Markdown, or download them for a Kindle reader.
All in all, maintaining this code does not seem to be worthwhile
anymore.
As a consequence of this, guides (+3 MB uncompressed) won't be
distributed with the rails gem anymore. Of course, guides and API
are going to be still part of releases, since documentation is
maintained alongside code and tests.
Also, time permitting, this will allow us to experiment with novel
ways to generate documentation in the Rails docs server, since
right now we were constrained by being able to generate them in
the user's environment.
2015-02-06 14:06:29 -05:00
s . files = [ 'README.md' ]
2009-08-31 20:20:44 -04:00
2012-11-08 14:51:18 -05:00
s . add_dependency 'activesupport' , version
s . add_dependency 'actionpack' , version
2012-05-31 12:21:56 -04:00
s . add_dependency 'actionview' , version
2013-10-02 10:40:17 -04:00
s . add_dependency 'activemodel' , version
2012-11-08 14:51:18 -05:00
s . add_dependency 'activerecord' , version
s . add_dependency 'actionmailer' , version
2014-08-12 05:29:21 -04:00
s . add_dependency 'activejob' , version
2012-11-08 14:51:18 -05:00
s . add_dependency 'railties' , version
2013-02-25 18:05:20 -05:00
s . add_dependency 'bundler' , '>= 1.3.0' , '< 2.0'
2014-11-24 16:32:49 -05:00
s . add_dependency 'sprockets-rails'
2009-08-31 20:20:44 -04:00
end