Rakefile in merb-admin-0.5.5 vs Rakefile in merb-admin-0.5.6

- old
+ new

@@ -7,28 +7,27 @@ GEM_NAME = "merb-admin" AUTHOR = "Erik Michaels-Ober" EMAIL = "sferik@gmail.com" HOMEPAGE = "http://github.com/sferik/merb-admin" SUMMARY = "MerbAdmin is a Merb plugin that provides an easy-to-use interface for managing your data." -GEM_VERSION = "0.5.5" +GEM_VERSION = "0.5.6" spec = Gem::Specification.new do |s| s.rubyforge_project = "merb" s.name = GEM_NAME s.version = GEM_VERSION s.platform = Gem::Platform::RUBY s.has_rdoc = false - s.extra_rdoc_files = ["README.markdown", "LICENSE"] + s.extra_rdoc_files = ["README.rdoc", "LICENSE"] s.summary = SUMMARY s.description = s.summary s.author = AUTHOR s.email = EMAIL s.homepage = HOMEPAGE s.add_dependency("merb-slices", ">= 1.0.12") s.add_dependency("builder", ">= 2.1.2") - s.add_dependency("mlb", ">= 0.0.3") s.require_path = "lib" - s.files = %w(LICENSE README.markdown Rakefile) + Dir.glob("{app,lib,public,schema,spec,stubs}/**/*") + s.files = %w(LICENSE README.rdoc Rakefile) + Dir.glob("{app,lib,public,schema,spec,stubs}/**/*") s.post_install_message = <<-POST_INSTALL_MESSAGE #{"*" * 80} WARNING: MerbAdmin does not implement any authorization scheme. Make sure to apply authorization logic before deploying to production!