IMHO it is a design mistake.. a missing feature that there is no real support for creating a plugin that ships with arbitrary ORM / DBAL "drivers".
To make the idea clearer: At this time we can not build a plugin providing classes for Propel AND Doctrine. This is against DRY IMHO because we need duplicate plugins like sfGuardPlugin and sfGuardDoctrinePlugin. BTW: both names are wrong.. anyone noticed that? ;-) It should be sfPropelGuardPlugin and sfDoctrineGuardPlugin.
BUT: This is a very poor concept. Why not providing to have Models for arbitrary ORMs / DBALs?
This could be achieved by these steps:
- move Propel schema location into a propel sub dir as already the case with Doctrine
- move Propel model classes into a propel sub dir as already the case with Doctrine
- make the orm setting so intelligent that autoload only searches in the appropriate model sub dir
