filters for 1.9 compatibility.
This also fix Merb rake install task which needs this layout to work properly.
* When running from a typical dev setup, the gem dependencies will be loaded directly from the current source instead of loading from rubygems. A typical dev setup would be clones of all repositories below github.com/merb that all reside within the same directory. * Simplified require statements in spec files * Added spec/spec.opts file for every gem
Without this change, the default password strategy is always activated because the wrong config key is used. [#1179 state:resolved]
* Fixed previously failing rake spec task due to spec order dependencies * Refactored specs to use a shared spec that can be used to test basic compliance * Use local merb-core and local merb-auth-more when running from a typical dev checkout (a git clone) * Added specs for sequel bcrypt mixin * Simplified require paths in lib and spec
If for some reason you decided to reset the salt, [#1163 state:resolved]
Reverts: ffff732093da6d300b4652616a8fa150ec758331 Reverts: 784ac7d71780d1a7cfb9152ba4cb0e18a990ab7a Reverts: 41fed477beb9d987b6dcae8ea83228bde8018e62 Reverts: 7a029f022fecf98fddc50090f3a5ee4804522877 Reverts: 7dc1cc7a93f687fc4dd3f1e6b7feefcc31fe7594 The goal is to only use active_model compliant API internally. This will render the separate gem useless.
* Fix a bug in required fields * Add an overidable option for optional fields
… in the session rather than reconstituting them.