Plugin incompatible with Gradle's Isolated Projects

[3flex]

This plugin applies configuration from the root project using allprojects which breaks project isolation.

Errors from report on Gradle 8.8:

⨉Project : cannot access Project.extensions functionality on subprojects via allprojects
⨉Project : cannot access Project.plugins functionality on subprojects via allprojects
⨉Project : cannot access Project.tasks functionality on subprojects via allprojects

Related to #81 but this may be fixable without fixing the other (and vice versa) so I'm opening this to track.

Keep an eye on upstream Gradle issue: gradle/gradle#25179. When that's closed there may be convenient ways to address the issues in this plugin in new Gradle versions.

[koppor]

Longer discussion: #81

[szpak]

Thanks for pointing it out @koppor. Closing in favor of #81.

[3flex]

I did say in the issue description:

Related to #81 but this may be fixable without fixing the other (and vice versa) so I'm opening this to track.

But that's fine if it will be fixed in #81.

[szpak]

Sorry, I didn't re-read the original message...

[neboskreb]

Is there any plan to address this issue?

My project produces several artefacts (each defined in the own sub-project) which have different release cycles, hence different version numbers. The current lack of isolation described in this ticket, prevents the effective use of this, otherwise great, plugin.

I would gladly contribute to this plugin if such fix was desired. @szpak Please come back to me if interested.