Thanks, Volker! I've just thumbed-up it! On Wed, Apr 28, 2021 at 5:59 PM Volker Lamp <volker.l...@gmail.com> wrote:
> If you, like me, use Spock (and perhaps Geb) specification/tests for your > Tapestry apps, please support my initiative to have Spock, or > spock-tapestry, to be precise, support Tapestry 5.7+. Indicate your support > by adding a 'thumbs up' to my contribution to the discussion of my pull > request > <https://github.com/spockframework/spock/pull/1315#discussion_r621218462>. > > The Spock specification (and test) framework has a sub-project named > 'spock-tapestry' whose purpose it is to provide a Spock extension that > knows how to deal with Tapestry's @ImportModule annotation, making it very > convenient to test modules and services written in Tapestry. Spock is great > and worth a closer look if you haven't heard of it before. The Spock > maintainers have done a good job keeping up with different versions of > Tapestry. > > As everyone on this list is probably aware, Tapestry 5.7 is not fully > backwards-compatible with previous releases. Many classes were moved to > other packages, and sometimes even to a different JAR. This was done to > avoid split packages, making them easier to be used with Java 9+ modules. > > Unfortunately, 'spock-tapestry' is affected by those backward > incompatibilities and the maintainers weren't too enthusiastic, at least > initially, about accommodating another Tapestry version (see TAP5-2668 > <https://issues.apache.org/jira/browse/TAP5-2668>). However, after > Thiago's > judgement > < > https://github.com/spockframework/spock/issues/1312#issuecomment-826810060 > > > that "another similar refactor isn't expected to happen again ever" it > looks like they are willing to consider it. > > Currently, there seems to be discord if 'spock-tapestry' should continue > supporting past verions of Tapestry (with the implication of having to > include conditional code for some of the past versions) or if, from the > next release, it should just upgrade its Tapestry dependency to 5.7+. My > take is the latter. As software evolves over time it is reasonable to > upgrade dependencies from time to time. Users of Tapestry up to release > 5.6.+ would still be able to use Spock up to release 2.0-M5. > > If you agree, again, please add a 'thumbs up' to my contribution to the > discussion of my pull request > <https://github.com/spockframework/spock/pull/1315#discussion_r621218462>. > However, I'm certainly interested in other points of view as well, so > please let me know by responding to this post. > > Thank you. > -- Thiago
