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

Please document the role of Active profile in Eclipse configuration

Open
#646 7 comments 5 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
documentation

Research direction

Start with the Eclipse section of README.md and reproduce the reported behavior using Eclipse's Active profile settings with the google-java-format implementation selected. Document what the formatter configuration and Active profile control, including whether profile changes affect Source / Format, so the README clearly states which profile to choose.

Written by the indexing model from the issue text.

Description

Eclipse

The README states: “The plugin adds a google-java-format formatter implementation that can be configured in Window > Preferences > Java > Code Style > Formatter > Formatter Implementation.”

It is unclear what can be configured exactly, or whether anything can be configured, considering the note in the same file: “There is no configurability as to the formatter's algorithm for formatting. This is a deliberate design decision to unify our code formatting on a single format.”

Relatedly, the role of the Active profile dialog box is not clear.

I just tested changing the number of spaces in the active profile, and this seems to have no effect on Source / Format when the google-java-format implementation is selected.

Please add some explanations about what can be configured and which Active profile should be chosen or indicate if it is supposed to have no effect.

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.