redhat-developer / redhat-developer/vscode-java
"No build tools" Java projects auto-import skipped due to presence of "build tools" Java projects in same workspace
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.3k
- Forks
- 546
- Merge medio
- 20 h 1 min
- PR fusionados (30 d)
- 11
Descripción
Describe the bug
Java projects without build tools are being skipped during auto-import due to the presence of Java projects with build tools in the same workspace. This results in missing imports and project configuration issues.
To Reproduce
Steps to reproduce the behavior:
- Create a workspace containing both Java projects with build tools (e.g., Maven, Gradle) and Java projects without build tools.
- Clean the Java language server workspace to trigger auto-import on startup.
- The Java projects without build tools fail to auto-import properly or are ignored/skipped by the extension, as they are not visible in the list of projects to import and do not import at all when opening any Java file in such projects.
Expected behavior
Java projects without build tools should be available as options to select in the import java projects list, allowing a non-build-tooled Java project to be imported correctly instead of skipped.
Environment
- Operating System: Windows
- JDK version: 21
- Visual Studio Code version: 1.111.0
- Java extension version: 1.53.0
Additional Information
When opening a Java file in a Java project without build tools, it will be automatically imported and added to the Java projects list, therefore auto-importing works fine as long as build tools projects aren't in the same workspace.
The best solution seems to be to add these types of projects to the list of importable Java projects and allow selection of non-build-tooled projects.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduzca el problema en Visual Studio Code con un workspace que contenga tanto proyectos de Maven o Gradle como proyectos sin herramientas de build y, a continuación, limpie el workspace del Java language server para activar la importación automática al iniciarse. Siga la lista de proyectos importables y verifique que los proyectos sin herramientas de build aparezcan en ella y puedan seleccionarse e importarse sin abrir primero un archivo Java.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, typescript, vscode
- Área
- developer-experience, tooling
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100