@jonathan-m-phillips maybe this is the reason that you saw a large number of "symbol not found" errors: when I ran ./gradlew clean followed by ./gradlew test, I found that it fails the first time. This is surprising (and bad) behavior from Specimin's build system.
This PR fixes that sequence of commands by explicitly naming the source sets for the test target. Similar problems might exist for other targets, but I haven't found any yet. For example, running ./gradlew clean before running the command that I mentioned in this comment doesn't cause Specimin to behave any differently.
@jonathan-m-phillips maybe this is the reason that you saw a large number of "symbol not found" errors: when I ran
./gradlew cleanfollowed by./gradlew test, I found that it fails the first time. This is surprising (and bad) behavior from Specimin's build system.This PR fixes that sequence of commands by explicitly naming the source sets for the test target. Similar problems might exist for other targets, but I haven't found any yet. For example, running
./gradlew cleanbefore running the command that I mentioned in this comment doesn't cause Specimin to behave any differently.