-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Implement test for checking package-info inconsistencies #33643
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
base: master
Are you sure you want to change the base?
Conversation
tasks.register("packageInfoData", GeneratePackageInfoDataTask::class) { | ||
description = "Map packages to the list of package-info.java files that apply to them" | ||
outputFile = layout.projectDirectory.file("build/architecture/package-info.json") | ||
packageInfoFiles = provider { GeneratePackageInfoDataTask.findPackageInfoFiles(projectBaseDirs) } |
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.
❌ Let's not have a script top-level scope projectBaseDirs
variable populated far away from here but gather the list of project base dirs from architectureElements
right here instead.
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.
I've tried that approach, but there are a lot of projects that are NOT included/linked to architectureElements
. Maybe it's ok to ignore those projects (I have my doubts), but until we decide that, this solution is not viable.
18fb3d6
to
fbe283f
Compare
Context
Contributor Checklist
<subproject>/src/integTest
) to verify changes from a user perspective.<subproject>/src/test
) to verify logic../gradlew sanityCheck
../gradlew <changed-subproject>:quickTest
.Reviewing cheatsheet
Before merging the PR, comments starting with