Hi Juan,
please, skim through the discussion about z3c.autoinclude:
http://plone.293351.n2.nabble.com/Let-s-get-rid-of-z3c-autoinclude-td7561158.html
<includePlugins package="plone" /> is already called in CMFPlone and it
makes no sense to use it outside CMFPlone. You could simply use <include
package="Products.CMFPlone" /> instead, but it would still include only
those plugins that have z3c.autoinclude.plugin-entrypoint for Plone in
their setup.py.
Best Regards,
Asko
Juan Pablo Giménez wrote:
2013/3/25 Asko Soukka <asko.sou...@iki.fi <mailto:asko.sou...@iki.fi>>
Héctor Velarde wrote:
On 25/03/13 11:55, Asko Soukka wrote:
By replacing <includeDependencies package="." /> with explicit
<include />s
HV> for all packages or only for this one?
Only for those packages that would like to directly depend on
zope.i18n, I think.
And, of course, you would NOT <include package="zope.i18n" />,
because that would include the utility registration, which
conflicts with ZPublisher's one (as seen in your paste).
I found another possible solution, maybe not the best but is
working... c.z3cform.widgets works only with plone, is not a pure zope
package as zope.i18n, thats why declares itself as a autoinclude
plugin for plone, right?... our problem arise when we autoinclude
zope.18n but we can avoid that autoincluding only the right ones, and
the right ones are clever packages than declare itself as autoinclude
plugins for plone too... so is that simple as
https://github.com/collective/collective.z3cform.widgets/commit/94323dc8e8bdde46ab31e89ff490898f21a9a653
thoughts?
--
Juan Pablo Giménez
skype & twitter: jpggimenez
Simples Consultoria <http://simplesconsultoria.com.br/>
_______________________________________________
Product-Developers mailing list
product-develop...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plone-product-developers
