bin/instanceand bin/test now contain the '/Users/philip/.cache/buildout/eggs/plone.app.contenttypes-1.2b3-py2.7.egg', instead of the new egg.
Why is this a issue? I want to test the 4.3-compatible version of plone.app.contenttypes because I'm backporting some features (https://github.com/plone/plone.app.contenttypes/tree/backport). For this I modified to buildout to follow the best-practices of bobtemplates.plone.
But now (and I guess for quite some time travis and local tests always test the released version and the package itself is ignored. I had the same problem with plone.app.linkintegrity.
The only way to get these instances to work is to use the coredev.
I remember that used to work at some point and cannot seem to figure out what is wrong. :cry:
Steps to reproduce:
bin/instance
andbin/test
now contain the '/Users/philip/.cache/buildout/eggs/plone.app.contenttypes-1.2b3-py2.7.egg', instead of the new egg.Why is this a issue? I want to test the 4.3-compatible version of plone.app.contenttypes because I'm backporting some features (https://github.com/plone/plone.app.contenttypes/tree/backport). For this I modified to buildout to follow the best-practices of bobtemplates.plone.
But now (and I guess for quite some time travis and local tests always test the released version and the package itself is ignored. I had the same problem with plone.app.linkintegrity. The only way to get these instances to work is to use the coredev.
I remember that used to work at some point and cannot seem to figure out what is wrong. :cry: