https://github.com/manolo/vaadin-demo-gwt
Compile a Vaadin maven app using gwt-compiler 2.8 instead of vaadin-compiler. SDM uses jetty-9.
https://github.com/manolo/vaadin-demo-gwt
Last synced: 4 months ago
JSON representation
Compile a Vaadin maven app using gwt-compiler 2.8 instead of vaadin-compiler. SDM uses jetty-9.
- Host: GitHub
- URL: https://github.com/manolo/vaadin-demo-gwt
- Owner: manolo
- Created: 2016-01-30T20:35:59.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-04-15T10:34:25.000Z (about 9 years ago)
- Last Synced: 2024-12-30T18:38:24.857Z (5 months ago)
- Language: CSS
- Size: 1.26 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
### Introduction
This project is a starter vaadin application replacing vaadin-client-compiler by GWT one, therefore you can use new features in the compiler like jsInterop.
It also uses new `net.ltgt.gwt-maven-plugin` for the compilation.
This version has customised `JettyLauncher` so as Jetty reads servlet 3.0 annotations in vaadin projects and hot-reloads whenever any object in the classpath changes.
### How it works
The trick is not depend on vaadin-client bundle in compilation because they override stuff in the gwt jars, but we extract all the needed vaadin classes to the `generated-sources` folder instead in the appropriate maven phase.
### Building
To build the app usage:
$ mvn clean package (to create the app)
To debug in SuperDevMode:
$ mvn gwt:devmode (to run the app in superdev mode)
### Issues
1. For some reason Vaadin bootstrap does not load the theme styles, or they are removed in some point. I'm facing the problem injecting some JS from server in order to add the style tag to the header, and add the appropriate theme class to the body.
2. A patched version of `LayoutManager` (line 265) is needed in order to avoid an assertion in SDM