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

classPathFile should not use exposed in configuration #56

Closed
szpak opened this issue Feb 13, 2017 · 4 comments
Closed

classPathFile should not use exposed in configuration #56

szpak opened this issue Feb 13, 2017 · 4 comments
Milestone

Comments

@szpak
Copy link
Owner

szpak commented Feb 13, 2017

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 oversight classPathFile has been exposed directly in the plugin configuration. It should be enough to have a useClassPathFile boolean configuration switch to pass a classpath to PIT using an automatically generated file instead of a classpath command line parameter.

@szpak
Copy link
Owner Author

szpak commented Sep 6, 2017

Available in 1.2.2 - useClasspathFile = true has to be added to the plugin configuration.

@szpak szpak closed this as completed Sep 6, 2017
@ninjubohra
Copy link

You should document this on the README.md file, as it took me 2 days to scour the Internet to find this plugin option 😄

@szpak
Copy link
Owner Author

szpak commented Nov 13, 2018

I'm glad you finally found it :).

However, in the README file there is:

 - useClasspathFile - enables passing additional classpath as a file content
 (useful for Windows users with lots of classpath elements, disabled by default - since 1.2.2)

Nevertheless, feel free to provide a PR with improvements :).

@ninjubohra
Copy link

You think I would read the entire documentation before announcing my ignorance to the whole world 😢
Thanks for a great plugin!

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

2 participants