I have spent the better part of today trying to figure out why propel-build-model fails if a plugin is not named sfSomething as the folder name.
For instances, I have had a plugin for some time named "contractor", that until today, never had any problems with. As of upgrading today, it seems that if I don't change the folder name of the plugin to atleast sfContractor it fails with the message... ---------------------------------------------------- [propel-om] Processing: generated-schema.xml Execution of target "om-template" failed for the following reason: C:\web\xampp\php\pear\symfony\vendor\propel-generator\build-pro pel.xml:436:1: No package found for database "" in generated-schema.xml. The propel.packageObjectModel property requires the packa ge attribute to be set for each database. [phingcall] C:\web\xampp\php\pear\symfony\vendor\propel-generator\build-propel.xml:436:1: No package found for database "" in gene rated-schema.xml. The propel.packageObjectModel property requires the package attribute to be set for each database. BUILD FINISHED -------------------------------------------------- By simply adding a prefix of "sf", to the folder name alone it executes fine. Is it now required that folders for plugins have a prefix of sf not found in the schema file? Sorry I've tried to figure out why this happens but I haven't spent much time with regards to the pake stuff so I'm not familiar. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs -~----------~----~----~----~------~----~------~--~---