Skip to content
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
merged 5 commits into from
Mar 9, 2019

Conversation

mr-archano
Copy link
Contributor

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 the java-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 the main sourceset of plugin. This project is then used by the test projects using a simple dependencySubsitution rule in their settings.gradle.

Copy link
Contributor

@tasomaniac tasomaniac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting approach. I wonder if the test plugin build is going to be cached between test runs.

@mr-archano
Copy link
Contributor Author

Yes it does, I already checked :)

@mr-archano mr-archano merged commit e55af1e into prepare_for_gradle_5 Mar 9, 2019
@mr-archano mr-archano deleted the remove_java_library_plugin branch March 9, 2019 12:32
@mr-archano mr-archano mentioned this pull request Mar 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants