|
1 | 1 | [[release-notes]] |
2 | 2 | = Release Notes |
3 | | - |
4 | 3 | include::include.adoc[] |
| 4 | +:SpecClassFileSelector: https://github.com/spockframework/spock/blob/03818ed010f4b4ca1136a292e214f79d518c4abe/spock-core/src/main/java/org/spockframework/buildsupport/ant/SpecClassFileSelector.java |
| 5 | +:scriptselector: {spock-example-project}/blob/963fd34d1609b7025ba92502483ce31b2c6d9d0a/build.xml#L167-L176 |
5 | 6 |
|
6 | 7 | == 2.4 (tbd) |
7 | 8 |
|
@@ -671,9 +672,17 @@ It can be set back to the old pre Spock 2.0 behaviour by setting |
671 | 672 | will be thrown at runtime. |
672 | 673 |
|
673 | 674 | // tag::breaking-change-removed-ant-support[] |
674 | | -==== Ant support removed |
675 | | -`SpecClassFileSelector` was removed, which was the only class that required `ant`. |
676 | | -If you are still using spock with `ant`, then you can just copy the class from the spock source code into your build. |
| 675 | +==== Ant custom selector removed |
| 676 | +The class `SpecClassFileSelector` that could be used to only select actual Spock specification classes when testing |
| 677 | +and creating a test report was removed. It was the only class that required `ant` and was basically just a one-line |
| 678 | +forward to the `SpecClassFileFinder` which is still available. |
| 679 | + |
| 680 | +If you are still using Spock with `ant`, then you can just copy {SpecClassFileSelector}[the class from the spock source code] |
| 681 | +into your build, or you simply use a {scriptselector}[`<scriptselector>`] that does this forwarding as shown in the |
| 682 | +{spock-example-project}[Spock Example Project]. |
| 683 | + |
| 684 | +Alternatively, you can also use a naming convention to find the classes that are actual specifications and not helper |
| 685 | +or base classes, or you live with a bit of wasted time and some meaningless entries in the test reports. |
677 | 686 | // end::breaking-change-removed-ant-support[] |
678 | 687 |
|
679 | 688 | === Misc |
@@ -1229,7 +1238,7 @@ Howard M. Lewis Ship, Ken Sipe, Venkat Subramaniam, Russel Winder. |
1229 | 1238 | * Improved and restyled reference documentation at https://docs.spockframework.org. Generated with |
1230 | 1239 | https://asciidoctor.org/[Asciidoctor] (what else?). |
1231 | 1240 | * Maven plugin removed. Just let Maven Surefire run your Spock specs like your JUnit tests |
1232 | | - (see https://examples.spockframework.org[spock-example] project). |
| 1241 | + (see {spock-example-project}[spock-example] project). |
1233 | 1242 | * Official support for Java 1.8, Groovy 2.3 and Groovy 2.4. Make sure to pick the `groovy-2.0` binaries for Groovy |
1234 | 1243 | 2.0/2.1/2.2, `groovy-2.3` binaries for Groovy 2.3, and `groovy-2.4` binaries for Groovy 2.4 and higher. |
1235 | 1244 | * Improved infrastructure to allow for easier community involvement: Switch to |
@@ -1787,7 +1796,7 @@ their types inferred from the values in the table (!). |
1787 | 1796 | === GitHub Repository |
1788 | 1797 |
|
1789 | 1798 | All source code has moved to https://github.spockframework.org/. The https://github.spockframework.org/spock-grails[Grails Spock plugin], |
1790 | | -https://github.spockframework.org/spock-example[Spock Example] project, and |
| 1799 | +{spock-example-project}[Spock Example] project, and |
1791 | 1800 | https://github.spockframework.org/spockwebconsole[Spock Web Console] now have their own GitHub projects. |
1792 | 1801 | Also available are slides and code for various Spock presentations (such as |
1793 | 1802 | https://github.spockframework.org/smarter-testing-with-spock[this one]). |
|
0 commit comments