Chris@909: = EDGE
Chris@909: 
Chris@909: * Samuel Williams (http://www.oriontransfer.co.nz/):
Chris@909: 	Thanks to Tekin for his patches.
Chris@909: 	Updated migrations system to tie in more closely with the current rails mechanism.
Chris@909: 	Rake task for updating database schema info
Chris@909: 		rake db:migrate:upgrade_plugin_migrations
Chris@909: 	Please see http://engines.lighthouseapp.com/projects/10178-engines-plugin/tickets/17 for more information.
Chris@909: 
Chris@909: * Refactored the view loading to work with changes in Edge Rails
Chris@909: 
Chris@909: * Fixed integration of plugin migrations with the new, default timestamped migrations in Edge Rails
Chris@909: 
Chris@909: * Refactored tests into the plugin itself - the plugin can now generate its own test_app harness and run tests within it.
Chris@909: 
Chris@909: 
Chris@909: = 2.0.0 - (ANOTHER) MASSIVE INTERNAL REFACTORING
Chris@909: 
Chris@909: * Engines now conforms to the new plugin loading mechanism, delegating plugin load order and lots of other things to Rails itself.
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.2.2
Chris@909: 
Chris@909: * Added the ability to code mix different types of files, cleaning up the existing code-mixing implementation slightly (Ticket #271)
Chris@909: 
Chris@909: 
Chris@909: = 1.2.1
Chris@909: 
Chris@909: * Added documentation to clarify some of the issues with Rails unloading classes that aren't required using "require_dependency" (Ticket #266)
Chris@909: 
Chris@909: * Fixed a bug where test_help was being loaded when it wasn't needed, and was actually causing problems (Ticket #265)
Chris@909: 
Chris@909: 
Chris@909: = 1.2.0 - MASSIVE INTERNAL REFACTORING
Chris@909: 
Chris@909: * !!!Support for Rails < 1.2 has been dropped!!!; if you are using Rails =< 1.1.6, please use Engines 1.1.6, available from http://svn.rails-engines.org/engines/tags/rel_1.1.6
Chris@909: 
Chris@909: * Engines are dead! Long live plugins! There is now no meaningful notion of an engine - all plugins can take advantage of the more powerful features that the engines plugin provides by including app directories, etc.
Chris@909: 
Chris@909: * Init_engine.rb is no longer used; please use the plugin-standard init.rb instead.
Chris@909: 
Chris@909: * Engines.start is no longer required; please use the config.plugins array provided by Rails instead
Chris@909: 
Chris@909: * To get the most benefit from Engines, set config.plugins to ["engines", "*"] to load the engines plugin first, and then all other plugins in their normal order after.
Chris@909: 
Chris@909: * Access all loaded plugins via the new Rails.plugins array, and by name using Rails.plugins[:plugin_name].
Chris@909: 
Chris@909: * Access plugin metadata loaded automatically from about.yml: Rails.plugins[:name].about. Plugin#version is provided directly, for easy access.
Chris@909: 
Chris@909: * Module.config is has been removed - use mattr_accessor instead, and initialize your default values via the init.rb mechanism.
Chris@909: 
Chris@909: * Public asset helpers have been rewritten; instead of engine_stylesheet, now use stylesheet_link_tag :name, :plugin => "plugin_name"
Chris@909: 
Chris@909: * Plugin migrations have been reworked to integrate into the main migration stream. Please run script/generate plugin_migration to create plugin migrations in your main application.
Chris@909: 
Chris@909: * The fixture method for loading fixtures against any class has been removed; instead, engines will now provide a mechanism for loading fixtures from all plugins, by mirroring fixtures into a common location.
Chris@909: 
Chris@909: * All references to engines have been removed; For example, any rake tasks which applied to engines now apply to all plugins. The default Rails rake tasks for plugins are overridden where necessary.
Chris@909: 
Chris@909: * Layouts can now be shared via plugins - inspiration gratefully taken from PluginAWeek's plugin_routing :)
Chris@909: 
Chris@909: * Actual routing from plugins is now possible, by including routes.rb in your plugin directory and using the from_plugin method in config/routes.rb (Ticket #182)
Chris@909: 
Chris@909: * Controllers are no longer loaded twice if they're not present in the normal app/ directory (Ticket #177)
Chris@909: 
Chris@909: * The preferred location for javascripts/stylesheets/etc is now 'assets' rather than 'public'
Chris@909: 
Chris@909: * Ensure that plugins started before routing have their controllers appropriately added to config.controller_paths (Ticket #258)
Chris@909: 
Chris@909: * Removed Engines.version - it's not longer relevant, now we're loading version information from about.yml files.
Chris@909: 
Chris@909: * Added a huge amount of documentation to all new modules.
Chris@909: 
Chris@909: * Added new warning message if installation of engines 1.2.x is attempted in a Rails 1.1.x application
Chris@909: 
Chris@909: * Added details of the removal of the config method to UPGRADING
Chris@909: 
Chris@909: * Removed the plugins:info rake task in favour of adding information to script/about via the Rails::Info module (Ticket #261)
Chris@909: 
Chris@909: * Improved handling of testing and documentation tasks for plugins
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.1.4
Chris@909: 
Chris@909: * Fixed creation of multipart emails (Ticket #190)
Chris@909: 
Chris@909: * Added a temporary fix to the code-mixing issue. In your engine's test/test_helper.rb, please add the following lines:
Chris@909: 
Chris@909:    # Ensure that the code mixing and view loading from the application is disabled
Chris@909:    Engines.disable_app_views_loading = true
Chris@909:    Engines.disable_app_code_mixing = true
Chris@909: 
Chris@909:   which will prevent code mixing for controllers and helpers, and loading views from the application. One thing to remember is to load any controllers/helpers using 'require_or_load' in your tests, to ensure that the engine behaviour is respected (Ticket #135)
Chris@909: 
Chris@909: * Added tasks to easily test engines individually (Ticket #120)
Chris@909: 
Chris@909: * Fixture extensions will now fail with an exception if the corresponding class cannot be loaded (Ticket #138)
Chris@909: 
Chris@909: * Patch for new routing/controller loading in Rails 1.1.6. The routing code is now replaced with the contents of config.controller_paths, along with controller paths from any started engines (Ticket #196)
Chris@909: 
Chris@909: * Rails' Configuration instance is now stored, and available from all engines and plugins.
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.1.3
Chris@909: 
Chris@909: * Fixed README to show 'models' rather than 'model' class (Ticket #167)
Chris@909: * Fixed dependency loading to work with Rails 1.1.4 (Ticket #180)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.1.2
Chris@909: 
Chris@909: * Added better fix to version checking (Ticket #130, jdell@gbdev.com).
Chris@909: 
Chris@909: * Fixed generated init_engine.rb so that VERSION module doesn't cause probems (Ticket #131, japgolly@gmail.com)
Chris@909: 
Chris@909: * Fixed error with Rails 1.0 when trying to ignore the engine_schema_info table (Ticket #132, snowblink@gmail.com)
Chris@909: 
Chris@909: * Re-added old style rake tasks (Ticket #133)
Chris@909: 
Chris@909: * No longer adding all subdirectories of <engine>/app or <engine>/lib, as this can cause issues when files are grouped in modules (Ticket #149, kasatani@gmail.com)
Chris@909: 
Chris@909: * Fixed engine precidence ordering for Rails 1.1 (Ticket #146)
Chris@909: 
Chris@909: * Added new Engines.each method to assist in processing the engines in the desired order (Ticket #146)
Chris@909: 
Chris@909: * Fixed annoying error message at appears when starting the console in development mode (Ticket #134)
Chris@909: 
Chris@909: * Engines is now super-careful about loading the correct version of Rails from vendor (Ticket #154)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.1.1
Chris@909: 
Chris@909: * Fixed migration rake task failing when given a specific version (Ticket #115)
Chris@909: 
Chris@909: * Added new rake task "test:engines" which will test engines (and other plugins) but ensure that the test database is cloned from development beforehand (Ticket #125)
Chris@909: 
Chris@909: * Fixed issue where 'engine_schema_info' table was included in schema dumps (Ticket #87)
Chris@909: 
Chris@909: * Fixed multi-part emails (Ticket #121)
Chris@909: 
Chris@909: * Added an 'install.rb' file to new engines created by the bundled generator, which installs the engines plugin automatically if it doesn't already exist (Ticket #122)
Chris@909: 
Chris@909: * Added a default VERSION module to generated engines (Ticket #123)
Chris@909: 
Chris@909: * Refactored copying of engine's public files to a method of an Engine instance. You can now call Engines.get(:engine_name).copy_public_files (Ticket #108)
Chris@909: 
Chris@909: * Changed engine generator templates from .rb files to .erb files (Ticket #106)
Chris@909: 
Chris@909: * Fixed the test_helper.erb file to use the correct testing extensions and not load any schema - the schema will be cloned automatically via rake test:engines
Chris@909: 
Chris@909: * Fixed problem when running with Rails 1.1.1 where version wasn't determined correctly (Ticket #129)
Chris@909: 
Chris@909: * Fixed bug preventing engines from loading when both Rails 1.1.0 and 1.1.1 gems are installed and in use.
Chris@909: 
Chris@909: * Updated version (d'oh!)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.1.0
Chris@909: 
Chris@909: * Improved regexp matching for Rails 1.0 engines with peculiar paths
Chris@909: 
Chris@909: * Engine instance objects can be accessed via Engines[:name], an alias for Engines.get(:name) (Ticket #99)
Chris@909: 
Chris@909: * init_engine.rb is now processed as the final step in the Engine.start process, so it can access files within the lib directory, which is now in the $LOAD_PATH at that point. (Ticket #99)
Chris@909: 
Chris@909: * Clarified MIT license (Ticket #98)
Chris@909: 
Chris@909: * Updated Rake tasks to integrate smoothly with Rails 1.1 namespaces
Chris@909: 
Chris@909: * Changed the version to "1.1.0 (svn)"
Chris@909: 
Chris@909: * Added more information about using the plugin with Edge Rails to the README
Chris@909: 
Chris@909: * moved extensions into lib/engines/ directory to enable use of Engines module in extension code.
Chris@909: 
Chris@909: * Added conditional require_or_load method which attempts to detect the current Rails version. To use the Edge Rails version of the loading mechanism, add the line:
Chris@909: 
Chris@909: *   Engines.config :edge, true
Chris@909: 
Chris@909: * to your environment.rb file.
Chris@909: 
Chris@909: * Merged changes from /branches/edge and /branches/rb_1.0 into /trunk
Chris@909: 
Chris@909: * engine_schema_info now respects the prefix/suffixes set for ActiveRecord::Base (Ticket #67)
Chris@909: 
Chris@909: * added ActiveRecord::Base.wrapped_table_name(name) method to assist in determining the correct table name
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.0.6
Chris@909: 
Chris@909: * Added ability to determine version information for engines: rake engine_info
Chris@909: 
Chris@909: * Added a custom logger for the Engines module, to stop pollution of the Rails logs.
Chris@909: 
Chris@909: * Added some more tests (in particular, see rails_engines/applications/engines_test).
Chris@909: 
Chris@909: * Another attempt at solving Ticket #53 - controllers and helpers should now be loadable from modules, and if a full path (including RAILS_ROOT/ENGINES_ROOT) is given, it should be safely stripped from the require filename such that corresponding files can be located in any active engines. In other words, controller/helper overloading should now completely work, even if the controllers/helpers are in modules.
Chris@909: 
Chris@909: * Added (finally) patch from Ticket #22 - ActionMailer helpers should now load
Chris@909: 
Chris@909: * Removed support for Engines.start :engine, :engine_name => 'whatever'. It was pointless.
Chris@909: 
Chris@909: * Fixed engine name referencing; engine_stylesheet/engine_javascript can now happily use shorthand engine names (i.e. :test == :test_engine) (Ticket #45)
Chris@909: 
Chris@909: * Fixed minor documentation error ('Engine.start' ==> 'Engines.start') (Ticket #57)
Chris@909: 
Chris@909: * Fixed double inclusion of RAILS_ROOT in engine_migrate rake task (Ticket #61)
Chris@909: 
Chris@909: * Added ability to force config values even if given as a hash (Ticket #62)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.0.5
Chris@909: 
Chris@909: * Fixed bug stopping fixtures from loading with PostgreSQL
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.0.4
Chris@909: 
Chris@909: * Another attempt at loading controllers within modules (Ticket #56)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.0.3
Chris@909: 
Chris@909: * Fixed serious dependency bug stopping controllers being loaded (Ticket #56)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.0.2
Chris@909: 
Chris@909: * Fixed bug with overloading controllers in modules from /app directory
Chris@909: 
Chris@909: * Fixed exception thrown when public files couldn't be created; exception is now logged (Ticket #52)
Chris@909: 
Chris@909: * Fixed problem with generated test_helper.rb file via File.expand_path (Ticket #50)
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = 1.0.1
Chris@909: 
Chris@909: * Added engine generator for creation of new engines
Chris@909: 
Chris@909: * Fixed 'Engine' typo in README
Chris@909: 
Chris@909: * Fixed bug in fixtures extensions
Chris@909: 
Chris@909: * Fixed /lib path management bug
Chris@909: 
Chris@909: * Added method to determine public directory location from Engine object
Chris@909: 
Chris@909: * Fixed bug in the error message in get_engine_dir()
Chris@909: 
Chris@909: * Added proper component loading
Chris@909: 
Chris@909: * Added preliminary tests for the config() methods module
Chris@909: 
Chris@909: 
Chris@909: 
Chris@909: = pre-v170
Chris@909: 
Chris@909: * Fixed copyright notices to point to DHH, rather than me.
Chris@909: 
Chris@909: * Moved extension require statements into lib/engines.rb, so the will be loaded if another module/file calls require 'engines
Chris@909: 
Chris@909: * Added a CHANGELOG file (this file)