Skip to content

[gazelle] Allow package-level granularity nested within module-level#421

Open
shs96c wants to merge 1 commit into
bazel-contrib:mainfrom
shs96c:pr-c-package-within-module
Open

[gazelle] Allow package-level granularity nested within module-level#421
shs96c wants to merge 1 commit into
bazel-contrib:mainfrom
shs96c:pr-c-package-within-module

Conversation

@shs96c

@shs96c shs96c commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator

Subdirectories within a module-granularity tree can now override back to package granularity by setting # gazelle:java_module_granularity package. This allows specific packages to be built independently while the rest of the module continues to aggregate into a single target.

Subdirectories within a module-granularity tree can now override back to
package granularity by setting `# gazelle:java_module_granularity package`.
This allows specific packages to be built independently while the rest
of the module continues to aggregate into a single target.
@stevebarrau

Copy link
Copy Markdown
Collaborator

We talked about this 1:1 and I think the behavior you are trying to fix is already correct. The one behavior That I think is incorrect/unsupported is a module granularity of module and package nested. I.e.

-- a M
    -- b P
        -- c M
            -- d P

I did not try this.

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

Successfully merging this pull request may close these issues.

2 participants