• R/O
  • HTTP
  • SSH
  • HTTPS

vaadin: Repository summary

sample


Recent Commits RSS

Rev. Time Author Message
2085d54 2016-05-14 21:18:40 cintake master add jsp-api
056e856 2016-05-13 00:35:47 cintake
7d548fd 2016-05-05 18:05:31 cintake add jsp-api
47669e5 2016-05-05 15:38:36 manager
608586d 2016-05-03 20:40:03 cintake add jsp-api
4927c8f 2016-05-03 19:30:16 cintake add jsp-api
7e64076 2016-04-29 23:07:01 cintake

Branches

Name Rev. Time Author Message
master 2085d54 2016-05-14 21:18:40 cintake add jsp-api

README.md

vaadin01

Template for a simple Vaadin application that only requires a Servlet 3.0 container to run.

Workflow

To compile the entire project, run "mvn install". To run the application, run "mvn jetty:run" and open http://localhost:8080/ .

To develop the theme, simply update the relevant theme files and reload the application. Pre-compiling a theme eliminates automatic theme updates at runtime - see below for more information.

Debugging client side code - run "mvn vaadin:run-codeserver" on a separate console while the application is running - activate Super Dev Mode in the debug window of the application

To produce a deployable production mode WAR: - change productionMode to true in the servlet class configuration (nested in the UI class) - run "mvn clean vaadin:compile-theme package" - See below for more information. Running "mvn clean" removes the pre-compiled theme. - test with "mvn jetty:run-war

Using a precompiled theme

When developing the application, Vaadin can compile the theme on the fly when needed, or the theme can be precompiled to speed up page loads.

To precompile the theme run "mvn vaadin:compile-theme". Note, though, that once the theme has been precompiled, any theme changes will not be visible until the next theme compilation or running the "mvn clean" target.

When developing the theme, running the application in the "run" mode (rather than in "debug") in the IDE can speed up consecutive on-the-fly theme compilations significantly.

Using Vaadin pre-releases

If Vaadin pre-releases are not enabled by default, use the Maven parameter "-P vaadin-prerelease" or change the activation default value of the profile in pom.xml .

Show on old repository browser