The Java reordering tool I wanted for years, so I finally built it
Anton Lem has developed JHarmonizer, an open-source tool for Java that automates the reordering and formatting of class members. This tool aims to improve code quality and readability by enforcing consistent coding standards across teams. The need for such a tool arose from the challenges of maintaining code conventions in larger teams, where manual adherence often leads to noisy diffs and complicates the review process.
- ▪JHarmonizer is designed to keep Java class members ordered and formatted consistently.
- ▪The tool can be integrated into Maven and CI pipelines to enforce coding standards automatically.
- ▪Inconsistent formatting can create noisy diffs, making code reviews more difficult and time-consuming.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/antonlem/the-java-reordering-tool-i-wanted-for-years-so-i-finally-built-it-2ngc |
| Publication time | Sun, 24 May 2026 22:41:29 +0000 |
| Retrieval time | 2026-05-24T23:07:34.930Z |
| Last seen | 2026-05-24T23:07:34.930Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | a_-Ffp9SOg3Y |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3948197) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Anton Lem Posted on May 24 The Java reordering tool I wanted for years, so I finally built it #java #opensource #formatter #codequality For years, I wanted one simple thing in Java projects: a reliable way to keep class members ordered and formatted consistently. Fields, constructors, methods, accessors, nested types. Not manually. Not by a team convention written in a wiki. Not by asking everyone to remember the right IDE action before committing. A real tool.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
