Repository files navigation

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

To compile the entire project, run "mvn install".

To run the application, run "mvn jetty:run" and openhttp://localhost:8080/ .

To produce a deployable production mode WAR:

• change productionMode to true in the servlet class configuration (nested in the UI class)
• run "mvn clean package"
• test the war file with "mvn jetty:run-war"

The generated maven project is using an automatically generated widgetset by default.When you add a dependency that needs client-side compilation, the maven plugin willautomatically generate it for you. Your own client-side customizations can be added intopackage "client".

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

When developing the theme, Vaadin can be configured to compile the SASS basedtheme at runtime in the server. This way you can just modify the scss files inyour IDE and reload the browser to see changes.

To use the runtime compilation, open pom.xml and comment out the compile-themegoal from vaadin-maven-plugin configuration. To remove a possibly existingpre-compiled theme, run "mvn clean package" once.

When using the runtime compiler, running the application in the "run" mode(rather than in "debug" mode) can speed up consecutive theme compilationssignificantly.

It is highly recommended to disable runtime compilation for production WAR files.

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 .