plone.org Administrator
2011-10-06 23:07:05 UTC
A new response has been given to the issue **Adding plone.app.testing to templates**
in the tracker **Issue tracker** by **Cris Ewing**.
Response Information
--------------------
Issue
Adding plone.app.testing to templates (http://plone.org/products/zopeskel/issues/65)
- Issue state: Unconfirmed -> Postponed
**Response Details**::
well, the only one's for which it would work at all would be
plone4 stuff, right? Adding plone.app.testing to earlier versions
of plone leads to all sorts of buildout version conflict fun.
I would suggest that after we merge templer into the trunk, we can
start thinking about doing stuff like this, making the testing
infrastructure of a package depend on the version of plone for
which it is intended, etc.
* This is an automated email, please do not reply - plone.org Administrator
in the tracker **Issue tracker** by **Cris Ewing**.
Response Information
--------------------
Issue
Adding plone.app.testing to templates (http://plone.org/products/zopeskel/issues/65)
- Issue state: Unconfirmed -> Postponed
**Response Details**::
well, the only one's for which it would work at all would be
plone4 stuff, right? Adding plone.app.testing to earlier versions
of plone leads to all sorts of buildout version conflict fun.
I would suggest that after we merge templer into the trunk, we can
start thinking about doing stuff like this, making the testing
infrastructure of a package depend on the version of plone for
which it is intended, etc.
* This is an automated email, please do not reply - plone.org Administrator