-
Notifications
You must be signed in to change notification settings - Fork 44
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
Gradle 4 Warning - Separate output directories #72
Comments
So it has been removed, which breaks compatibility of this plugin with Gradle 5: |
I'm having issues building my project due to this with Gradle 5.4.1. I get the following error Could not find matching constructor for: org.gradle.process.internal.DefaultJavaForkOptions(org.gradle.api.internal.file.BaseDirFileResolver) How could I resolve this? Any leads? Should I downngrade to Gradle 4? Would be grateful for the suggestions/support. Thank you |
Hi @Ravinderkaur04 - v0.9 (the latest version of this plugin) is not supported on Gradle 5. Work is ongoing to address this. I suggest downgrading to the latest Gradle 4 in the meantime. Personally, I use 4.10.2. |
Thanks for the quick reply. I downgraded to Gradle 4.10.2. This time project is built successfully but while trying to run tests I get the same error again.
|
I use the same version of Gradle and the same version of the plugin. So the only difference between my project and yours is your build.gradle. Would you be able to provide this file for me to look at? Also a full stack trace? |
Sure.
StackTrace:
|
I have created a new project containing your build.gradle. I don't get the error that you are experiencing. So it must be something in your environment that is causing a problem. Do you have a gradle.properties file in your gradle user home directory (usually a '.gradle' directory in your home directory) or your project directory? Can you provide the output of the 'properties' task and also this task:
Also, how are you running gradle? Are you certain that you're running 4.10.2? I notice that you don't have any configuration for the wrapper task in your build.gradle, so I presume you aren't using the gradle wrapper. This means you are accessing gradle via your system path. If you have multiple versions of gradle installed, are you sure you're using the right one? |
Thanks a lot for the reply. It was still using Gradle 5. I had to delete the .gradle directory from the my home directory and in my project the gradle-wrapper.properties was also pointing to gradle 5. Here from the project directory as well I removed gradle directory and gradle 5 from .gradle. |
Any update if there will be support with Gradle 5+? |
Thank you @kmaterka , I noticed that, but there's a slightly different implementation. Have you been using this other plugin ? |
@BertCC yes, I used that and even contributed few fixes. Unfortunately it was more than a year ago and I don't remember what changed and how to migrate. Anyway, it should be pretty straightforward - just follow instructions from README. |
Getting this warning when using the plugin with gradle 4.x
I think it must be coming from this plugin as otherwise my build is fairly simple. Is this a known issue?
Seems like a common cause of this is when the classesDir property is used, however I can't see any reference to it in the plugin: https://docs.gradle.org/current/dsl/org.gradle.api.tasks.SourceSetOutput.html#org.gradle.api.tasks.SourceSetOutput:classesDir
Thanks,
Ivan
The text was updated successfully, but these errors were encountered: