This repository has been archived by the owner on Feb 11, 2022. It is now read-only.
Make test-projects runnable without test-kit #177
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When a test-project fails is not possible at the moment just running that single project again, because of the way
GradleRunner
is using thejava-gradle-plugin
to inject the plugin into the classpath of the build.Solution
Simply get rid of
java-gradle-plugin
and use composite builds instead. In order to achieve that I have introduced a Gradle project including themain
sourceset ofplugin
. This project is then used by the test projects using a simpledependencySubsitution
rule in theirsettings.gradle
.