[
https://issues.apache.org/jira/browse/TAP5-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332235#comment-17332235
]
Thiago Henrique De Paula Figueiredo commented on TAP5-2668:
-----------------------------------------------------------
Hello, [~leonard84] and [~vlamp]!
Since the Tapestry team is small and there's no one working on it full time, we
usually avoid bring projects to inside the project so we don't have yet more
code to maintain (and, speaking for myself, I have no experience with Spock at
all).
In this specific case, there was a very rare major refactor that moved a number
of classes from one package to another so Tapestry code doesn't have split
packages, which are a headache for projects using Java 9+ modules. Otherwise,
the Tapestry's public API has changed very little since 5.4.
Another similar refactor isn't expected to happen again ever, so I believe the
best course of action here is for us or [~vlamp] provide a pull request for
getting tapestry-spock working with Tapestry 5.7.0+ so the next tapestry-spock
version supports it. Previous tapestry-spock versions cover previous versions
of Tapestry.
> Move spock-tapestry extension to tapestry-test
> ----------------------------------------------
>
> Key: TAP5-2668
> URL: https://issues.apache.org/jira/browse/TAP5-2668
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-test
> Reporter: Leonard Brünings
> Priority: Major
>
> Hi I'm the maintainer of the Spock Framework and I'd like to propose, that
> the spock-tapestry extensions is migrated to tapestry-test or tapestry-spock.
> The current implementation supports only 5.4.3 and a check with 5.7.1
> revealed some removed classes that would require another layer of reflection
> indirection to support different versions.
> In my opinion it would make more sense to move the extension to Tapestry, as
> this would simplify the code quite a bit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
