«
»

Release 0.0.6

Get it while it’s hot! Of course, you’ll probably want to wait a bit for it to propagate to all the gem mirrors. If you really can’t wait, you can find it here.

$ sudo gem install mack

From the CHANGELOG:

  • rake generate:<generator_name>
  • rake generate:plugin – will generate the stub of a plugin in the vendor/plugins directory.
  • rake dump:config – prints out the configuration information for the specified environment.
  • redirect_to now takes an optional Hash as a second parameter, instead of a fixnum.
  • redirect_to will now do server side redirects if passed :server_side => true as part of the optional second argument Hash.
  • plugin in support. plugins get loaded before the ‘app’ directory. each plugins ‘lib’ directory is added to the global load path and then each plugins ‘init.rb’ file is called, which is responsible for loading the necessary files. The ‘lib’ directories are finally removed from the global load path.
  • renamed initialize directory to initialization. moved logging, orm_support, and plugins to a subfolder called initializers.

Tags: , , , , , ,

This entry was posted on Thursday, February 28th, 2008 at 3:25 pm and is filed under News, Releases, Updates. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

2 Responses to “Release 0.0.6”

  1. Matt Todd Says:
    February 29th, 2008 at 11:33 am

    Just to cover my bases, I’m posting here too.

    I tried sending an email to bugs@mackframework.com but it returned undeliverable because the virtual user is unknown to alias table (or something similar to that).

    There’s a bug in the module core extension… the new_level param is completely ignored/unused.

    I also added some bugs in the RubyForge tracker, including this bug mentioned above.

    I’d recommend adding a bit of contact information so we know who to contact (with actually-working contact information) and who owns/runs this project.

    Cheers,

    Matt Todd

  2. Mark Bates Says:
    February 29th, 2008 at 2:33 pm

    Thanks Matt, for the heads up. I’ve fixed the email problem.

    I’ve also fixed the bug you refer to. It’ll be in the next release of the gem.

    Keep `em coming!