This repo serves the content of the project site https://www.eclipse.org/jdt/

This is similar to the following issue:

eclipse-platform/eclipse.platform.releng.aggregator#168

Eclipse is not resolving the imports and suggests me to create class, create record, create interface, create enum and add type parameter to method and class.

I normally use for my applications the jdk17, some of the imports I use are not being resolved by eclipse, the same class suggests me create class, create registry, create interface, create enum and add type parameter to method and class and stuck at the crossroads because I don't know the import path of the class from the jdk. This is a stumbling block for me and have become critical to go ahead with the development of my projects to study develop with java. It never suggests me the import when I mouse over, it suggests me to create any kind of element for the project that java has available, but it never suggests me the one that is already developed by java. I would like the eclipse community to solve this error as soon as possible and suggest me some possible solution until the problem is definitely solved.
I use the community version of IDE 2023-03 (you download a zip file with the IDE without installing it).

Hint text when hovering the mouse over the class to import

This is the error when hovering the mouse over the class to be imported:
The scanner cannot resolve a type.
This error occurs with the great majority of classes developed by Java. For my part I do not know the vast majority of package paths to import that class, there are many classes and different packages.

Attached images of the problem

Suggestions when hovering over the class to be imported
Module project
Project libraries

All links in the attached images section of the problem are images.

There are some accessibility issues regarding DTP for blind users
utilize DTP by screen readers.

0. While navigating on the cells of a table, by pressing the up or
   down or left or right arrow keys, cell value is not reported by the
   screen-reader. cell values should be reported by the screen-reader but
   with applying following rules

1.When navigating between the columns by left or right arrow keys, the
column's  headers and column's number are not reported.
when navigating between the columns, the screen-reader should say
column number, column's header, cell value.

2. when navigating between the rows by up and down keys, the row
   number is not reported.
   when navigating between the rows, the screen-reader should say row
   number, row name, cell value.

note:

1. when navigating up and down, on a column,, it is not needed to
   report the column numbers.

2. When navigating left and right, on a row, it is not needed to
   report the row numbers.

3. When I execute a query using SQL Scrapbook, each row of the the
   result table is read by the screen-reader, similar a semicolon
   separated line of a text, .
   The result should be a table that a blind user can navigate on it
   using arrow keys as the same ordinary tables of the database.
   Thanks.

If we have a CODEOWNERS file, committers will automatically suggested for review when opening a PR.

This does not mean I'm advocating for the concept of code ownership in JDT.

Currently, when you look for information how to build JDT, you're lost in an infinite reference loop:

From https://github.com/eclipse-jdt/.github/blob/main/CONTRIBUTING.md:

Information regarding source code management, builds, coding standards, and more.

• https://projects.eclipse.org/projects/eclipse.jdt/developer

That latter page simply links back to github.

For normal development, having a working Eclipse workspace (preferably via Oomph) is of course sufficient, but should you ever need to build with maven, it's hard to find a command line that actually works (plus all the prerequisites like maven version, toolchains.xml etc. pp.).

We should add a pull request template guiding contributors through opening a well-formed PR.

I am a blind developer who use Eclipse via screen-reader NVDA.
When I execute a query in SQL Scrapbook then its result is desplayed
in sql result window, but each row of the result is read by
screen-reader such as a text line while Eclipse preferences is default
e.i. Preferences > Data Management > SQL Developer > SQL Result View
Options > Desplay Mode, is Grid.
Also it is required the result is like a table, and user able to
navigate between cells by arrow keys. In addition to cell value,
column head and row number of each cell must be read while navigating.

Hi All,
I have written below template to inject a Dependency :

${:import(org.springframework.beans.factory.annotation.Autowired)}
private final ${class_to_inject} ${var_name};

@Autowired
public ${primary_type_name}(${class_to_inject} ${var_name}){
        this.${var_name} = ${var_name};
}

When I select class_to_inject using ctrl-space. After successful import, eclipse loses the focus on other template variables. I am not able to navigate to next variable using tab key. Below are screen shot that explains the problem -

step 1: Injecting the template

step 2: Template loaded in Eclipse

step 3: Selecting the Bean

step 4: Dependency added in code

After adding the dependency now, I am unable to move to next variable var_name using tab key as IDE loses the focus on the other template variables.

Is it Bug with Eclipse?

Note - Some time it works expectedly and some time it don't. I have no idea why is it happening?

I am blind and use computers with the help of screan-reader NVDA. I
have some accessibility issues while using EGit.

1. when having merge conflicts, and resolving, in the merge tool, when
   navigating on the list of files it is not distinguishable if each of
   them is resolved or not yet.
   They should be marked by a prefix like a * till screen-readers can report.
2. To study and comparing codes is difficult for a blind user that is
   not able to study left and right editors in merge tools
   simultaneously; so I prefer to study the code in a single normal
   eclipse code editor that determines conflicts by <<< >>>.
   when I need to open a file code to resolving a conflict it is better
   to be a menu item like "open in code editor" in the context menu. I
   know, the selected file will be opened in code editor if I select
   ""open from the context menu then select "project Explorer" option and
   next I open code editor from there but this routine is too long. It
   can have a shortcut or another shorter way.)
   Thanks.

We should add an issue_template.md file to guide contributors/users on how to file a good issue.

Eclipse is not a viable IDE for projects with mixed JVM languages (Java, Groovy, Kotlin, Scala).

Don't get me wrong, I love Eclipse and have been using it since dumping IntelliJ 20+ years ago. I like that I can have over a 100 library, service, and multi-module projects open and the IDE still functions.

The problem is that we don't get to dictate the languages used for all our projects. Many of our projects have mixed languages; e.g., Java or Kotlin main and Groovy tests or Kotlin in one module and Java in another. With the flood-gates open, Kotlin is increasingly being added to the mix.

I haven't been able to get JDT, GDT, and Kotlin to coexist since Eclipse 2020-06 (4.16) and even with that version the Kotlin editor doesn't function. The Kotlin plugin has always been incomplete, buggy, and prone to causing JDT issues. The GDT plugin has to patch the JDT because apparently the JDT or Language Server teams aren't willing to make the necessary accommodations to avoid said patching. That likely causes even more issues for other plugins attempting to interface with the JDT.

Eclipse needs to own the JVM Language modules/plugins if it wants to remain viable as a JVM language IDE. Now that Kotlin has quite a bit of traction, it's pretty clear that IntelliJ doesn't care about creating a Kotlin plug-in to compete with their own IDE. Oracle doesn't provide the Java module. Apache doesn't provide the Groovy module. Why should IntelliJ provide the Kotlin module? So far, Eclipse has been lucky to have the reasonably well maintained Groovy Development Toolkit.

So for now, Eclipse is untenable as an IDE for mixed JVM language environments.

We can help contributors by providing certain files like

• CODE_OF_CONDUCT.md
• CONTRIBUTING.md
• pull_request_template.md #7
• issue_template.md #8
• CODEOWNERS #9

Like contributing, readme etc. I will push in a moment