I agree that Engines are great ways to share functionality as well. In my case, first I'm running an app that isn't Rails 2.3 yet which leaves Engines support out at least for now.
Second, I think that Engines serve best for loosely coupled functionality that isn't really a central part of the application. In this case the functionality that I'm sharing is tightly coupled and critical in both Rails apps, so I felt that a plugin approach wasn't quite right.
Additionally, even in an Engines setup the custom test setups and indeed most of the same arguments would need to apply, just in the vendor/plugins/plugin-name directory instead of shared.
I agree that Engines are great ways to share functionality as well. In my case, first I'm running an app that isn't Rails 2.3 yet which leaves Engines support out at least for now.
Second, I think that Engines serve best for loosely coupled functionality that isn't really a central part of the application. In this case the functionality that I'm sharing is tightly coupled and critical in both Rails apps, so I felt that a plugin approach wasn't quite right.
Additionally, even in an Engines setup the custom test setups and indeed most of the same arguments would need to apply, just in the vendor/plugins/plugin-name directory instead of shared.