Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Define a module manifest

Open
#755 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

No file, test, or entry point is named. Start by inspecting the project's build and packaging configuration for Java 17 module support, then determine how a module manifest could limit exports to ALL-UNNAMED. Done means the project defines the manifest and its resulting export scope is verified.

Written by the indexing model from the issue text.

Description

It would be helpful if this project would define a module manifest, so that I could avoid exporting java module internals to ALL-UNNAMED in Java 17+. I understand I would still need to add those exports, but the reduced scope would be helpful.

Dominant language
Java
Stars
6.2k
Forks
936
Avg merge
6m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/google-java-format

All issues in google/google-java-format

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.