redhat-developer / redhat-developer/vscode-java
Error on startup: 'overlaps the location of another project'...
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
0.8.0, Linux 14.04
- Opening up VSCode on a folder containing the devoxx sample (https://github.com/fbricon/devoxx.git) gives me the following error:
Contains: /home/aeschli/workspaces/samples/devoxx overlaps the location of another project: 'devoxx'
- the underlying problem is that the hidden Eclipe workspace can only have a single project of a given name
- looks like I already opened some other project called 'devoxx' some time (that's possible)
- it would be good if the other location would be printed so we can find out if it's a valid conflict
- conflicts like that should not be the users concern:
- a solution would be to always qualify all project names so they are unique
- an other solution would be to always delete such duplicated projects (and rebuild them if they are used again later)
[Error - 11:07:12 AM] Aug 21, 2017 11:07:11 AM Problem importing to workspace
Invalid project description.
org.eclipse.core.internal.resources.ResourceException: Invalid project description.
at org.eclipse.core.internal.resources.Project.checkDescription(Project.java:169)
at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:53)
at org.eclipse.core.internal.resources.Project.create(Project.java:263)
at org.eclipse.core.internal.resources.Project.create(Project.java:247)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.create(ProjectConfigurationManager.java:995)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:162)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:143)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133)
at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.importToWorkspace(MavenProjectImporter.java:117)
at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.initializeProjects(ProjectsManager.java:75)
at org.eclipse.jdt.ls.core.internal.handlers.InitHandler$1.run(InitHandler.java:117)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Contains: OK
Contains: /home/aeschli/workspaces/samples/devoxx overlaps the location of another project: 'devoxx'
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
Traza la ruta de inicio a través de InitHandler, ProjectsManager y MavenProjectImporter, tomando como punto de partida el fallo reportado de Project.checkDescription. Determina cómo se gestionan los nombres de proyecto duplicados y verifica que el inicio ya no deje el conflicto sin explicar ni falle sin identificar la otra ubicación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, typescript
- Área
- developer-experience, tooling
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 30/100