script.zcml has <include files="../+*.zcml" /> This is done to inject an out-of-tree, LOSA only accessible configuration in the tree. The use case is to put the username password of the email accounts used for incoming email.
I guess a LOSA only need to change the ZCML registration from canonical.launchpad.interfaces.IMailHandler to canonical.launchpad.interfaces.mail.IMailHandler Cheers -- Francis J. Lacoste [email protected] On November 11, 2010, Jonathan Lange wrote: > On Thu, Nov 11, 2010 at 10:35 AM, Robert Collins > > <[email protected]> wrote: > > On Thu, Nov 11, 2010 at 11:32 PM, Jonathan Lange <[email protected]> wrote: > >> On Thu, Nov 11, 2010 at 10:31 AM, Robert Collins > >> > >> <[email protected]> wrote: > >>> Sadly this has broken qastaging, and will as it propogates to staging > >>> nuke it similarly. > >> > >> I'm sorry to hear that. How could I have avoided this with local or ec2 > >> testing? > > > > Our production-configs, which are deliberately inaccessible to the > > regular development environment, happen to refer to things in our > > class paths. > > As a Canonical employee I have access to those. They don't actually > have any references that would break with either of the recent glob > changes. It turns out that the cited error comes from a file that is > neither in the Launchpad tree nor in the production-configs tree. Fun > times! Henning is investigating further. > > jml > > _______________________________________________ > Mailing list: https://launchpad.net/~launchpad-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~launchpad-dev > More help : https://help.launchpad.net/ListHelp
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
