Hello,
As you should know, I'm a everything-as-plugin developer. It does not help me but it's allways a good experience and I can really explore the borderlands of symfony and Doctrine. I encounter a big issue with the brand new sfMailer class and Swift library. In fact, for sf 1.2, I've done a plugin that include the Swift library, and some custom features like mail database logs and tasks. This plugin already include the Swift library and everything was working fine... until the day I decided to upgrade to sf 1.3. The sfFactoryConfigHandler class already include the Swift library, so I removed mine, but I was not able to use my plugin anymore because the Swift versions were not the same and it seems that my usage of Swift was exhausted. I was using Swift-4.0.4 and the current symfony version is @SWIFT_VERSION_NUMBER@ (NB: Does anybody can update this class constant to have a real version name, please?). The only quick solution I've found is to comment the "mailer" value from the available list of factories to be able to use my version of Swift that works perfectly... sorry, that does exactly what I expect. What really bothers me is that, from my point of vue, it should be a plugin (as main external library like Propel and Doctrine), and not comes from the symfony core, because in the current situation, nobody can disable this library (that is a bad thing) without changing the core of symfony (that is never a good idea). Please argue. Loops --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
