-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Codenarc] aggregateCodenarc causes gradle warnings after upgrading to v0.45.0 #469
Comments
Could you provide more details on your current environment? |
Here it is:
|
I've cloned the klokwrk-project repository and updated the build to use
|
Thank you for looking into this. Which Gradle command did you use? I'm using
|
I used |
It looks like |
Wiped the build cache. Cleaned the project. Gave it another no. No warnings.
|
Still, it looks like there are some warnings present :-) There is
at the end of the output. If you run (without any cleaning) |
Indeed. I can verify that the warnings only occur when It may be the case that the |
Yes, very unexpected that it depends on |
I don't see a significant change in |
Here is what I was able to find:
To my understanding, when running in parallel mode, any request from the root project for configuration resolving in child modules
This branch will be entered for submodules when running in parallel mode, but will not when running in serial mode. |
Task 'aggregateCodenarc' is excluded as it causes Gradle warnings during parallel execution. Related to kordamp/kordamp-gradle-plugins#469 Problem is not reported to Gradle yet.
After upgrading to kordamp 0.45.0, I start getting a warning from the
aggregateCodenarc
task when it is executed as part of thecheck
task:If
aggregateCodenarc
is executed standalone, warnings do not appear.If I revert back to the 0.44.0 version, warnings also disappear.
Tnx.
The text was updated successfully, but these errors were encountered: