Previously Wichert Akkerman wrote:
Previously yuppie wrote:
But I agree there should be a way to remove obsolete and broken local
steps. A method that removes local duplicates of global steps and a
method that removes broken steps would be useful. Not sure if they
should be run
yuppie wrote:
GenericSetup trunk has global step registries. I propose to use the new
ZCML directive for registering all GenericSetup and CMF import and
export steps globally. And to remove the import_steps.xml and
export_steps.xml files from the profiles shipped with CMF.
This also requires
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
yuppie wrote:
GenericSetup trunk has global step registries. I propose to use the new
ZCML directive for registering all GenericSetup and CMF import and
export steps globally. And to remove the import_steps.xml and
Tres Seaver wrote:
Worse, an import is potentially destructive. I am now of the opinion
that content import / export should be treated as a separate
application, not built into the profile.
From a design perspective, I'd tend to agree. I've always felt that the
'structure' import step sat a
Previously yuppie wrote:
Hi!
Wichert Akkerman wrote:
Previously yuppie wrote:
GenericSetup trunk has global step registries. I propose to use the new
ZCML directive for registering all GenericSetup and CMF import and
export steps globally. And to remove the import_steps.xml and
Hi!
Wichert Akkerman wrote:
Previously yuppie wrote:
GenericSetup trunk has global step registries. I propose to use the new
ZCML directive for registering all GenericSetup and CMF import and
export steps globally. And to remove the import_steps.xml and
export_steps.xml files from the
yuppie wrote:
GenericSetup trunk has global step registries. I propose to use the new
ZCML directive for registering all GenericSetup and CMF import and
export steps globally. And to remove the import_steps.xml and
export_steps.xml files from the profiles shipped with CMF.
This also
