Am 11.04.2013 22:53, schrieb Roel Bruggink:
It seems that zc.recipe.testrunner favours released eggs over
development eggs set by either develop = . or by using mr.develop.
A workaround seems to be explicitly setting the versions block, but that
is something that will be forgotten when a new release is made. ( see
https://github.com/collective/collective.z3cform.datagridfield/blob/master/base.cfg
)
Is this expected behaviour?
How can I force bin/test to include the right eggs, without explicitly
pinning the .dev version?
I ran into the same problem trying to run Jenkins job on Plone core
packages. The only way I could make it work so far was to pin the dev
version explicitly:
https://github.com/plone/plone.app.collection/blob/master/buildout.cfg
I don't think this is how it should work, but I haven't had the time to
look into this myself. It would be great if someone could fix that or at
least give us some pointers. First question would be if this is a
mr.developer or a zc.buildout problem?
Cheers,
Timo
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
