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

Gradle plugin: findProperty causes "Project <x> cannot dynamically look up a property in the parent project" when Isolated Projects enabled #3656

Open
3flex opened this issue Jun 23, 2024 · 0 comments
Labels

Comments

@3flex
Copy link
Contributor

3flex commented Jun 23, 2024

Describe the bug
Using Gradle's Isolated Projects mode flags an issue caused by this plugin.

dokka uses findProperty to check whether the org.jetbrains.dokka.experimental.tryK2 property has been enabled or not. This is problematic as one of its behaviours is to "Search up through this project's ancestor projects" which causes the IP violation.

Expected behaviour
It should be possible to use dokka with Isolated Projects enabled.

Screenshots

To Reproduce

  1. Checkout https://github.com/detekt/detekt
  2. Run ./gradlew build -Dorg.gradle.unsafe.isolated-projects=true

Dokka configuration
Run dokka with Gradle runner with org.jetbrains.dokka.experimental.tryK2 property unset.

Installation

  • Operating system: Windows
  • Build tool: Gradle v8.8
  • Dokka version: 1.9.20

Additional context
Possibly dokka support should be added & tracked in YouTrack under https://youtrack.jetbrains.com/issue/KT-64575.

A fix is likely as simple as using gradleProperty instead on Gradle 6.2 and up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant