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

test.java is not part of any project

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
emacs, java
Domain
developer-experience, devtools

Research direction

Reproduce the issue by opening a generic .java file through the reported lsp-java setup and observe the project-import prompt. Trace the project detection and import flow that handles files outside large projects. Done should mean generic Java files have a defined setup path without repeatedly prompting, or the supported limitation is documented.

Written by the indexing model from the issue text.

Description

I'm new to emacs and I tried to setup lsp for java. The setup process seems to work well, but whenever I open any generic .java file I get a prompt:

test.java is not part of any project

i ==> Import project root /home/maksatr/Documents/
I ==> Import project by selecting root directory interactively
. ==> Import project at current directory /home/maksatr/Documents/
d ==> Do not ask again for the current project by adding /home/maksatr/Documents/ to lsp-session-folders-blocklist
D ==> Do not ask again for the current project by selecting ignore path interactively
n ==> Do nothing: ask again when opening other files from the current project

Select action:

is there a way to set it up so that it works with generic files as well and not only in huge projects?

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.