Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose binding of an assertj-core dependency automatically to all "touched" test tasks #3

Open
Nava2 opened this issue May 30, 2017 · 1 comment

Comments

@Nava2
Copy link
Collaborator

Nava2 commented May 30, 2017

Associating the AssertJ dependency is done via the test configuration, i.e:

dependencies {                
    // https://mvnrepository.com/artifact/org.assertj/assertj-core
    testCompile group: 'org.assertj', name: 'assertj-core', version: '3.8.0'
}

It would be great to be able to assign this once and have it assigned to all targets that have generated sources. Probably via a "global scope" property or via the assertJ configuration.

@Nava2
Copy link
Collaborator Author

Nava2 commented Apr 30, 2023

Alternately, have a check in the plugin that tries to verify that the assertJ dependency is satisfied. We shouldn't be installing it by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant