metasploit-framework/Rakefile

#!/usr/bin/env rake
require File.expand_path('../config/application', __FILE__)
require 'metasploit/framework/require'

# @note must be before `Metasploit::Framework::Application.load_tasks`
#
# define db rake tasks from activerecord if activerecord is in the bundle.  activerecord could be not in the bundle if
# the user installs with `bundle install --without db`
Metasploit::Framework::Require.optionally_active_record_railtie

Metasploit::Framework::Application.load_tasks
Various merge resolutions from master <- staging * --ask option ported to new location * --version option now works * MSF version updated * All specs passing 2014-08-15 16:33:31 +00:00			`#!/usr/bin/env rake`
			`require File.expand_path('../config/application', __FILE__)`
			`require 'metasploit/framework/require'`
Specs for activerecord patch [#46141013] Spec the desired behavior for ConnectionPool prior to removing the patch to sync with upstream 3.2.12. 2013-03-18 16:01:45 +00:00
Various merge resolutions from master <- staging * --ask option ported to new location * --version option now works * MSF version updated * All specs passing 2014-08-15 16:33:31 +00:00			# @note must be before `Metasploit::Framework::Application.load_tasks`
Allow use of rake db tasks [#46224565] The following rake tasks are added and work similar to how they work in rails apps: * db:create * db:drop * db:migrate * db:migrate:status * db:rollback * db:schema:dump * db:schema:load * db:seed (but no db seeds defined at this time) * db:setup * db:version The hidden task db:test:prepare is also available, which means `rake spec` can depend on it so that the test database is dropped and recreated from the development database when running specs (Although there are yet to be database tests, this branch is in preparation for that work that will be split between multiple developers.) 2013-03-14 20:46:18 +00:00			`#`
Various merge resolutions from master <- staging * --ask option ported to new location * --version option now works * MSF version updated * All specs passing 2014-08-15 16:33:31 +00:00			`# define db rake tasks from activerecord if activerecord is in the bundle. activerecord could be not in the bundle if`
			# the user installs with `bundle install --without db`
			`Metasploit::Framework::Require.optionally_active_record_railtie`
Update Gemfile to metasploit_data_models 0.6.1 [#45771305] MetasploitDataModels 0.6.1 adds a re-usable yard.rake so that all Metasploit project don't have to define their own. It also adds guards so that the YARD tasks aren't defined (and don't cause errors) if YARD is not available. This also adds support for making the Rakefile work with `bundle install --without development test` so it still functions in the bundle building environment for Pro. 2013-03-07 20:22:35 +00:00
Various merge resolutions from master <- staging * --ask option ported to new location * --version option now works * MSF version updated * All specs passing 2014-08-15 16:33:31 +00:00			`Metasploit::Framework::Application.load_tasks`