Closed StefanHirche closed 10 months ago
Do you have the following into your project's gradle.properties
file or machine's ~/.gradle/gradle.properties
file?
org.gradle.configureondemand=true
Which Gradle version are you using?
Can you link a reproducing project?
Also, do you believe it is related to your other issue, #700
- Do you have the following into your project's
gradle.properties
file or machine's~/.gradle/gradle.properties
file?org.gradle.configureondemand=true
No, I don't. But I can check if this changes anything.
- Which Gradle version are you using? 7.6.2
- Can you link a reproducing project? I will try
- Also, do you believe it is related to your other issue, Dependencies in the classpath configuration in the buildscript block of build.gradle are marked unused #700 I'm not sure, as I found several similar issues in refreshVersion's issues list, but all only mentioning a destinct artifact dependency, so I just added my problem artifact, as all others are working fine. And this problem occurs in a normal dependency block.
Can you try with version 0.60.2-SNAPSHOT
and let me know if the issue is fixed?
You'll need to add the snapshots repo. Instructions here: https://splitties.github.io/refreshVersions/setup/#if-you-want-to-use-a-snapshot-version
I plan to release 0.60.2 this Tuesday, after a good night of sleep.
I just tested the snapshot and it looks good. No "unused" entries anymore, at least no unexpected ones. Thanks.
Great, releasing in several minutes.
🐛 Describe the bug
I just changed to 0.60.0, and now the runtimeOnly dependecy to jaxb-runtime is marked as unused, although it is used in 3 projects. The strange thing is, if i remove the line from version.properties, it is added again with the refreshVersions task, but marked as unused
⚠️ Current behavior
The dependecy is marked as unused
✅ Expected behavior
It is not marked as unused.
💣 Steps to reproduce
Don't know, maybe using jaxb-runtime is enough.
📱 Tech info