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

Differences in imports order in IntelliJ and Eclipse.

Open
#1,007 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the differing import order with the Eclipse and IntelliJ plugins described in the issue, using the supplied import examples and v1.18.1 settings. Compare how each IDE integration applies import ordering and identify the relevant plugin entry points. Done means both integrations produce the same ordering for the reported imports.

Written by the indexing model from the issue text.

Description

Using v1.18.1 plugins for Eclipse and IntelliJ, but there is difference in imports order for both IDEs.
Imports layouts for Eclipse:
eclipse_import_layout
Imports layouts for IntelliJ:
idea_import_layout

Imports in IntelliJ:

import com.domain.sap.IF.helper.DocumentHelper;
import com.domain.sap.SapUtility;
import com.domain.sap.SyncDocument;

Imports in Eclipse:

import com.domain.sap.SapUtility;
import com.domain.sap.SyncDocument;
import com.domain.sap.IF.helper.DocumentHelper;

For me it looks like IntelliJ uses a Code Formatter also for Imports formatting and Eclipse uses it's own mechanism.
How to make it common?

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

Contributor guide

Open the contributing guide

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.