Updated gemspec to automatically find files using git

Author: peakpg

browsercms.gemspec

@@ -11,35 +11,19 @@ Gem::Specification.new do |s|
  s.summary = %q{BrowserCMS is a a general purpose, open source Web Content Management System (CMS), written using Ruby on Rails.}
  s.description = %q{Web Content Management in Rails.}
  s.email = %q{github@browsermedia.com}
- s.executables = ["browsercms", "bcms", "bcms-upgrade"]
  s.extra_rdoc_files = [
  "LICENSE.txt",
  "README.markdown"
  ]
  s.required_ruby_version = '>= 1.9.2'
 
- s.files = Dir["rails/*.rb"]
- s.files += Dir["browsercms.gemspec"]
- s.files += Dir[".yardopts"]
- s.files += Dir["doc/app/**/*"]
- s.files += Dir["doc/guides/html/**/*"]
- s.files += Dir["app/**/*"]
- s.files += Dir["db/migrate/[0-9]*_*.rb"]
- s.files += Dir["db/demo/**/*"]
- s.files += Dir["db/browsercms.seeds.rb"]
- s.files += Dir["lib/**/*"]
+ s.files = `git ls-files`.split("\n")
+ s.files -= Dir['test/dummy/*']
  s.files -= Dir["lib/tasks/cucumber.rake"]
  s.files -= Dir["lib/tasks/cms.rake"]
- s.files += Dir["public/stylesheets/cms/**/*"]
- s.files += Dir["public/javascripts/jquery*"]
- s.files += Dir["public/javascripts/cms/**/*"]
- s.files += Dir["public/bcms/**/*"]
- s.files += Dir["public/site/**/*"]
- s.files += Dir["public/images/cms/**/*"]
- s.files += Dir["public/themes/**/*"]
- s.files += Dir["public/themes/**/*"]
- s.files += Dir["vendor/assets/**/*"]
- s.files -= Dir['test/dummy/*']
+ s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
+ s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+
 
  s.add_dependency('rails', "~> 3.1")
 

doc/release_notes.txt

@@ -17,6 +17,7 @@ Add the ability to add BrowserCMS to Rails projects.
  end
 * [#3] Asset Pipeline: All bcms assets are now served using the assets pipeline.
 * [#443] Removed two primative javascript and stylesheets in favor of asset pipeline (where needed).
+* [#448] Mountable Engines - BrowserCMS is now a mountable engine, which should make integrating it with other projects easier.
 
 v3.3.0
 ======

lib/tasks/cms.rake

@@ -1,3 +1,4 @@
+# These are tasks for the core browsercms project, and shouldn't be bundled into the distributable gem
 namespace :test do
 
  desc 'Runs all Tests (Test::Unit) and Features (cucumber)'

upgrading_to_3_1.md

@@ -7,34 +7,44 @@ Make migrate generation use 3.1 style
 Needs
 -----
 
-* Design how a portlet can include a single jquery based library by just declaring it in the render.html.erb.
-** eg. auto_discovery_link_tag -> Does not get included in the head
-* Add better messaging for `browsercms demo [NAME]`
-* Remove bespin
-* Run in production mode locally. Try POW to see if that adds subdomains easily.
+* Add ticket for upgrading to Rails 3.1
 * Differ `bundle install` from happening until Gemfile is updated to include bcms
+* Remove bespin
+* Improve Performance - Sitemap and serving pages is particularly slow
+** Use Ancestry gem - It handles automatically turning models into tree via a single column. Would be very very performant in comparison to current behavior.
 
 Wants (Taking advantage of 3.1)
 -----
-* http://freelancing-gods.com/posts/combustion_better_rails_engine_testing
+
+* Improve generators for assets from engines (Review http://bibwild.wordpress.com/2011/09/20/design-for-including-rails-engine-assets-into-pipeline-manifest/)
 * Remove the styled_file_field (no longer maintained)
-* Creating Modules using Mountable apps
-** `rails plugin new [NAME] --mountable` is the command
-* Engines - Rework bcms as a mountable engine, using the dummy app. Dummy apps are designed to be run using rails s, which is perfect.
-** Generators (like model) within an engine will namespace things properly
-** Need to run `rake bcms:install:migrations` to install engine migrations (Handled through install)
-** This will also make bcms includable as part of a Gemfile using git
+* [#416] Make bcms includable as part of a Gemfile using git
 * Migrations have a single 'def change' method now, rather than self.up and self.down
-* Use Ancestry gem - It handles automatically turning models into tree via a single column. Would be very very performant in comparison to current behavior.
 * Themes can be packaged as assets as well (I think?). Rework bluesteel so its part of the asset pipeline.
+* Run in production mode locally (for better error testing). Try POW to see if that adds subdomains easily.
+* Design how a portlet can include a single jquery based library by just declaring it in the render.html.erb.
+** eg. auto_discovery_link_tag -> Does not get included in the head
+* Add better messaging for `browsercms demo [NAME]`
+
 
 Ideas
 -----
 * Allow for multiple view templates for blocks.
 * Look at Papertrail and see how they structure versions. Their API seems every simple for single blocks.
 
-## Modules to be updated:
-* bcms_fckEditor will need to be updated to use the new JS inclusion
+## Modules to be updated (for Engines)
+
+bcms_news (first one)
+bcms_polling
+bcms_event
+bcms_fckeditor (Needs to correctly use new JS inclusion)
+bcms_content_rotator
+bcms_webdav
+bcms_cas
+bcms_google_mini_search
+bcms_page_comments
+
+
 
 ### How to upgrade to a Rails Engine