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
Set virtual project directories for :bom
, :version-catalog
#5664
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified with the warning message with ./gradlew publishToMavenLocal --parallel --warning-mode all
.
A warning message for dependencyManagement
is also printed, but I prefer that it be handled when we actually upgrade the gradle version. Thanks @sh-cho 👍 👍 👍
settings.gradle
Outdated
// Published version catalog projects | ||
includeWithFlags ':version-catalog', 'version-catalog' | ||
project(':version-catalog').projectDir.mkdirs() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Should we create these projects under
gradle/virtual-projects
? - Add
gradle/virtual-projects/
to.gitignore
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe gradle/scripts/.virtual-projects/
? I wonder if it makes sense to use build/virtual-projects
as well.. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
build/virtual-projects
sounds good because build/
is already excluded from git and is automatically cleaned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. I'll try to move generated projects under build/virtual-projects
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done :)
Please take a look
d57fff3
to
12edadf
Compare
:bom
, :version-catalog
:bom
, :version-catalog
:bom
, :version-catalog
:bom
, :version-catalog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot! 👍 👍 👍
Let me merge this after build with Gradle 9.0, which isn't release yet, to make sure if we don't miss anything.
Motivation: Starting with Gradle 9.0, Gradle will not run builds if a project directory is missing or read-only. (ref: https://docs.gradle.org/8.7/userguide/upgrading_version_8.html#deprecated_missing_project_directory) Modification: - Create project directories - `:bom`, `:version-catalog` - `:dependencyManagement` will be handled via line/gradle-scripts#177 Result: - Deprecation for Gradle 9.0 is prepared for this behavior
This will creates project directory under there, not under Root.
12edadf
to
9dc8494
Compare
Motivation:
Starting with Gradle 9.0, Gradle will not run builds if a project directory is missing or read-only.
(ref:
https://docs.gradle.org/8.7/userguide/upgrading_version_8.html#deprecated_missing_project_directory)
Modification:
build/virtual-projects
:bom
,:version-catalog
:dependencyManagement
will be handled via Prepare Gradle 9.0 deprecations gradle-scripts#177Result: