| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…ression body syntax
…ed new FulladleSettingsPlugin to manage the fulladle multi-module setup and refactored to use it
Integrated AGP 9.0.1 changes, Gradle 9.4.0 wrapper update, and develocity plugin 4.3.2 while preserving config-cache compatibility changes (defaultDependencies, argumentProviders, removed afterEvaluate wrappers).
- Use gradle.projectsEvaluated instead of afterEvaluate in FulladlePlugin so legacy path sees fully evaluated subprojects without needing evaluationDependsOnChildren (which breaks other plugins) - Move configuration creation and extension setup to apply() phase - Move automaticallyConfigureTestOrchestrator before onVariants loop - Add CC multi-module integration tests for both legacy and settings paths - Document settings plugin in multi-module-testing.md and changelog
| Back | FazBrowse Home | New Git URL |
Changes
How it works
When the settings plugin is applied, each subproject gets a FulladleModulePlugin that writes a JSON metadata file via FulladleModuleMetadataTask. The root YamlConfigWriterTask consumes these files through Gradle's dependency management — no Project references cross module boundaries.
Without the settings plugin, the legacy subprojects {} path still works. Module configuration now happens at configuration time rather than in task actions, so the configuration cache can serialize the task graph cleanly.
Test plan