-
Notifications
You must be signed in to change notification settings - Fork 58
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
classPathFile should not use exposed in configuration #56
Comments
Available in 1.2.2 - |
You should document this on the README.md file, as it took me 2 days to scour the Internet to find this plugin option 😄 |
I'm glad you finally found it :). However, in the README file there is:
Nevertheless, feel free to provide a PR with improvements :). |
You think I would read the entire documentation before announcing my ignorance to the whole world 😢 |
The Gradle plugin itself doesn't provide a direct way to specify a
classpath
passed to PIT - it is based on the project configuration. Due to an oversightclassPathFile
has been exposed directly in the plugin configuration. It should be enough to have auseClassPathFile
boolean configuration switch to pass a classpath to PIT using an automatically generated file instead of aclasspath
command line parameter.The text was updated successfully, but these errors were encountered: