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

Is there a way to configure the import order to have the same order than the default for IntelliJ?

Open
  • Is something wrong?
#485 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
emacs, java
Domain
developer-experience, tooling

Research direction

Start with the documentation for lsp-java-completion-import-order and the XML formatting configuration mentioned in the issue. Check whether static-import grouping and ordering are supported, comparing the available configuration with the IntelliJ-style order described; done means documenting the configuration or clearly identifying the missing capability.

Written by the indexing model from the issue text.

Description

I see that the documentation here mentions:
lsp-java-completion-import-order
and also mentions the possibility to import an XML file to specify a lot of formatting options.

But I couldn't find any mention of the group ordering of static imports vs. the rest of imports.
Does lsp-java support the configuration of this?

All my team-mates use IntelliJ, but I would love to use Emacs lsp-java instead, but I see that import ordering (by default) is different, and the code standard in the company is very strict :(
I think the default order that IntelliJ uses is somewhat like:

import all other imports
<blank line>
import static all other imports

if lsp-java-completion-import-order supports this, how can I specify "static" imports at the end (or at the beginning if that would be necessary)?

Dominant language
Emacs Lisp
Stars
696
Forks
97
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 emacs-lsp/lsp-java

All issues in emacs-lsp/lsp-java

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.