Closed JohnKVision closed 7 years ago
Why am I picking up tons of jetty libraries for doing a simple gwt compilation? I could understand the need for the Jetty jars, if I was running the code server, or including the servlet library, but just for compilation ? Seems like this is coming from the gwt-dev.jar?
There's no "gwt compiler only" artifact for GWT. There could technically be one, but, well, legacy…
Feel free to exclude transitive dependencies you don't actually need (but note that gwt-codeserver
does need some of the Jetty dependencies). There's a trade-off too with backwards compatibility and having most things "just work" without the need for additional dependencies. This is debatable, but is the status quo.
Is it possible to use released tags for Jetty instead of snapshot variants ?
These are Jetty release artifacts (the timestamp is part of the version); and in case you're refering to the 3.1.M0
or 8.0.9.M3
versions, these are transitive dependencies; so if you have a problem with those, please file an issue to the Jetty project.
A workaround for compilation to get running a SpringBoot and GWT project without an desaster
Actually, the correct way to build things is to have separate classpaths for GWT (client) and non-GWT (server) compilations; and fortunately Gradle makes it easy-peasy (contrary to, say, Maven, where you're forced to use distinct Maven modules and possibly move files around).
GWT version:2.8.0 Operating System:G radle
Description
Why am I picking up tons of jetty libraries for doing a simple gwt compilation? I could understand the need for the Jetty jars, if I was running the code server, or including the servlet library, but just for compilation ? Seems like this is coming from the gwt-dev.jar? Here is what my Gradle dependency report looks like:
Is it possible to use released tags for Jetty instead of snapshot variants ? When using Gradle to crawl dependencies for Springboot and GWT it's always a desaster to get this project running.
A workaround for compilation to get running a SpringBoot and GWT project without an desaster ist to explain Gradle to exclude this dependencie:
exclude group: 'org.eclipse.jetty', module: 'apache-jsp'
Known workarounds
exclude group: 'org.eclipse.jetty', module: 'apache-jsp'