gwt-plugins / gwt-plugins/gwt-eclipse-plugin
Make it possible to use a relative path to GWT installation
- Lenguaje dominante
- Java
- Estrellas
- 117
- Forks
- 49
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Currently it is only possible to create an absolute path to the GWT installation.
This is causing problems because some of our developers have macs, and others have windows pc's.
When selecting the GWT installation in the plugin, it will modify the .classpath files with absolute paths like c:\.... Offcourse the mac pc's don't have a clue what c:\ is.
Without the plugin we solved this by creating an Eclipse project structure as followed
Project
|-imp
--|-src
--|-war
|-vendorlibraries
--|-gwt-codeserver
--|-gwt-dev.jar
--|-gwt-user.jar
--|-validation-api-1.0.0.GA-sources.jar
--|-validation-api-1.0.0.GA
When you then add those gwt jars to your classpath, they are relative in your .classpath file.
I actuallly managed to fix this problem, by editing the .classpath file by hand.
I replaced the lines as followed created by the plugin (multiple lines exist, this is just 1 example) :
with :
Note the / before vendorlibraries. This is the way Eclipse needs this to be (all your relative jars start with a /)
Now all is working, but Eclipse now gives the following error message :
- The GWT SDK JAR gwt-servlet.jar is missing in the WEB-INF/lib directory
This is because the plugin can't find the gwt-servlet.jar. I think because it is looking in c::\vendorlibraries instead of in the relative vendorlibraries directory.
Actually, this is not a problem for us because we don't use gwt-servlet.jar because we are talking with a C#.NET backend and are not using any servlets.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Comienza con la selección de la instalación de GWT en el plugin de Eclipse e inspecciona cómo escribe las entradas de .classpath y localiza gwt-servlet.jar. Reproduce la configuración con la ruta relativa /vendorlibraries/gwt-user.jar y verifica después que los proyectos puedan usar las rutas relativas en Windows y macOS sin advertencias incorrectas sobre JARs ausentes.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100