Skip to content

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

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

jbartok
Copy link
Member

@jbartok jbartok commented May 28, 2025

Context

Contributor Checklist

  • Review Contribution Guidelines.
  • Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
  • Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
  • Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
  • Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
  • Provide unit tests (under <subproject>/src/test) to verify logic.
  • Update User Guide, DSL Reference, and Javadoc for public-facing changes.
  • Ensure that tests pass sanity check: ./gradlew sanityCheck.
  • Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet

Before merging the PR, comments starting with

  • ❌ ❓must be fixed
  • 🤔 💅 should be fixed
  • 💭 may be fixed
  • 🎉 celebrate happy things

@jbartok jbartok self-assigned this May 28, 2025
@jbartok jbartok added this to the 9.0.0 RC1 milestone May 28, 2025
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) }
Copy link
Member

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.

Copy link
Member Author

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.

@eskatos eskatos added a:chore Minor issue without significant impact in:building-gradle gradle/gradle build labels May 28, 2025
@jbartok jbartok force-pushed the jb/package-info branch 2 times, most recently from 18fb3d6 to fbe283f Compare May 29, 2025 07:39
@jbartok jbartok force-pushed the jb/package-info branch from fbe283f to cc18f0a Compare May 29, 2025 07:41
@jbartok jbartok marked this pull request as ready for review May 29, 2025 09:51
@jbartok jbartok requested review from a team as code owners May 29, 2025 09:51
@jbartok jbartok requested review from a team as code owners May 29, 2025 09:51
@jbartok jbartok requested review from donat, jvandort, abstratt and alllex and removed request for a team May 29, 2025 09:51
@alllex alllex removed their request for review May 30, 2025 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:chore Minor issue without significant impact in:building-gradle gradle/gradle build
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy