eclipse-xtext / eclipse-xtext/xtext

JdtBasedProcessorProvider should be able to deal with non-default EFS file system

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

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
831
Forks
330
Avg merge
3d 7h
Merged PRs (30d)
12

Description

JdtBasedProcessorProvider should be able to deal with non-default EFS file system
e.g. when using Kotlin

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.

Research direction

Start by locating JdtBasedProcessorProvider and tracing how it obtains the default EFS file system. Reproduce the Kotlin scenario with a non-default EFS and identify the expected provider behavior; done means the provider handles that file system without regressing default EFS support.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kotlin
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.