-
Notifications
You must be signed in to change notification settings - Fork 8
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
Dokkatoo uses typesafe Attributes, which are bugged in Gradle #214
Comments
- use `Attribute<String>` instead of typed attributes. - change the Dokkatoo attributes to be value classes, so they can still be used mostly type-safely. - Improve logging (include hashcodes) and error reporting. #214
* workaround bugged Gradle attributes - use `Attribute<String>` instead of typed attributes. - change the Dokkatoo attributes to be value classes, so they can still be used mostly type-safely. - Improve logging (include hashcodes) and error reporting. #214 * Update modules/dokkatoo-plugin/src/main/kotlin/internal/gradleUtils.kt
Do you know if this problem also applies to Dokka v2? |
No, Dokkatoo and DGPv2 now use string-based attributes, which aren't affected. |
Uh. That's strange, because I'm still seeing #170 with the latest Dokkatoo version. Once I migrate to Dokka v2, I'll recreate the issue there. |
Ah yeah, #170 won't be helped by string-based attributes. A fix requires a more significant rewrite of how DGP shares files between subprojects. I tried a workaround, but it doesn't work because of an (extremely confusing and undocumented) feature in Gradle gradle/gradle#30921 #170 will be fixed in DGP at some point. |
Gradle recommends using typesafe attributes to share files. However, these are fundamentally bugged and will not work in some situations.
I will implement a workaround, but I am opening this issue to track a real fix, dependent on whether Gradle can acknowledge and fix the issue.
This issue might be the cause of #165 and #170.
Thank you @kelvSYC for the report and reproducer! #211
The text was updated successfully, but these errors were encountered: