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

Support for gradle configuration cache and isolated projects #166

Open
MarcusDunn opened this issue Jan 16, 2025 · 0 comments
Open

Support for gradle configuration cache and isolated projects #166

MarcusDunn opened this issue Jan 16, 2025 · 0 comments

Comments

@MarcusDunn
Copy link

MarcusDunn commented Jan 16, 2025

Configuration Cache:

Currently, to have my multi-module project work with the configuration cache

I have

// build.gradle.kts
tasks.withType<LiquibaseTask> {
    notCompatibleWithConfigurationCache("invokes Task.project")
}

In all my subprojects with the liquibase plugin. This prevents this task's configuration from being cached.

Isolated Projects:

I would also like to enable isolated projects. But when enabling it across my project with

# gradle.properties
org.gradle.unsafe.isolated-projects=true

I get the following error:

40 problems were found storing the configuration cache, 1 of which seems unique.
- Plugin 'org.liquibase.gradle': Project ':database' cannot dynamically look up a property in the parent project ':'

Motivation

configuration cache is going to be default soon (gradle 9), and isolated projects will eventually follow. I think solving both at the same time would be best, but individually the features are worthwhile for the build speed improvements they permit.

I would be happy to take a stab at a PR if you'd be willing to accept it, I'm far from a plugin author though.

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

No branches or pull requests

1 participant