If Role object respond to system? then we do not delete the role even if nobody else is using it (as is the default behavior)
You can simply add a boolean system field to the migration or implement your own def system? inside the Role object.
removed a stray debug line
made readme example consistent with API. (otherwise roles_users is the default association name)
More correct generation of join table name in acts_as_auth_object

Should fix #28
perform action check first
Fixed show_to for Rails 3
There are major changes in the way the unit testing is done, so I wasn't able to fix the tests.  Project for another day...
Added some checks for objects when subject can be null.
 Added some checks for objects when subject can be null.
Now functions returns false if called with nil subject.
Make the show_to helper return nil instead of ''
Depend on freshly baked be9-context
Bring in a gemspec
Allows the model to override the join table name
Merge pull request #38 from d2kagw/master

Allow the user to supply a custom join_table name for authorization objects
Update install instructions
Merge pull request #41 from cloverinteractive/master

Update the install instructions
Added join_table_name from rails 3.1 to fix a deprecated / removed version from 3.0.9.
This will make the gem backward compatible again by just using acts_as_authorization_subject
Inlined join_table_name to prevent any kind of version conflict
Merge pull request #45 from Narnach/master

Backwards compatible fix for rails 3.1.x (inlined version)
Add Gemfile
Remove bin/ and .bundle/