Plugin not compatible with the isolated projects #107

Activity

1. skydoves commented on Feb 10, 2026

   

   skydoves

   on Feb 10, 2026

   Owner

   More actions

   The collectProjectDependencies() function iterates project.rootProject.allprojects to gather package names from sibling modules. This information is passed to the compiler plugin so it can detect cross-module types; when a composable parameter's type comes from a different Gradle module, the compiler plugin needs to know that (see #18, #84), because types from other modules without @Stable/@Immutable/@StabilityInferred annotations should be treated as unstable (the plugin can't see their implementation details).

   That said, this cross-project access (rootProject.allprojects) is indeed incompatible with Gradle's Isolated Projects feature. I'll look into replacing it with a configuration-time-safe approach — for example, resolving the information from the compile classpath's module metadata instead of scanning sibling projects directly, or allowing users to declare cross-module packages explicitly via the extension DSL.

   👍React with 👍2Reacted by Matej Drobnič and Stefan Breetveld
2. wezley98 commented on Aug 13, 2026

   

   wezley98

   on Aug 13, 2026

   More actions

   Would be great to have support for this, isolated-projects has moved to incubating in gradle v9.7.0

   https://docs.gradle.org/current/release-notes.html#isolated-projects-is-now-incubating
3. skydoves

   added a commit that references this issue on Aug 21, 2026

   Support Gradle Isolated Projects (#107) (#201)

   ...

   6a94ff3
4. skydoves

   closed this as completedin #201on Aug 21, 2026