[Zope-CMF] SVN: Products.CMFDefault/trunk/setup.py - dependency cleanup

Tres Seaver tseaver at palladion.com
Mon Feb 16 12:40:14 EST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jens Vagelpohl wrote:
> 
> On Feb 16, 2009, at 17:44 , Tres Seaver wrote:
> 
>> Can somebody explain the dependency on DCWorkflow's ZCML getting
>> loaded?
>> This seems like it should be ripped out:  no tests should need to get
>> actaul DCWrolfow instances configured.  Or are we trying to run
>> functional tests against a site configured from a profile which uses
>> DCWorkflow?
> 
> Well, the use of the DCWorkflow profile is indirect.
> CMFDefault.testing defines a functional test layer that instantiates a
> portal using the CMFDefault default profile. Without loading the
> DCWorkflow profile, workflow creation fails with the traceback below.

Thanks, I had just chased that down myself.  I have the sense that
CMFDefault is probably ripe for a split:  all the code which backs
persistent objects (content types, the site itself, the tools) should
stay, but the part which actually provides the default baseline profile
should maybe be split out.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJmaT9+gerLs4ltQ4RAkr1AJ4yo2tW6q9juSZ8qntz2TLVS488IACeJaaN
GZXjUslc1Gf/bWkUog4iJek=
=gVze
-----END PGP SIGNATURE-----



More information about the Zope-CMF mailing list