Gradle Vaadin Plugin 1.2 released

I am happy to announce a new minor version of the plugin!

Here are the most prominent changes with the 1.2 release.

Plugin id changes

The old plugin id (fi.jasoft.plugin.vaadin) has long referenced a site that has not existed in a long time so it was time to update the id.

The fi.jasoft part of the plugin name has been changed to com.devsoap and the plugin can now be applied to your project by using the following:

plugins {
  id 'com.devsoap.plugin.vaadin" version "1.2.0"

#### Spring Boot JAR packaging support

Previously the plugin has only supported WAR packaging but with 1.2 now also JAR packaging becomes supported. By default this will be used when you include the Spring Boot gradle plugin (org.springframework.boot) in your project.

To get started with building Spring Boot projects with JAR packaging add the following plugins to your build:

plugins {
    id 'org.springframework.boot' version '1.5.2.RELEASE'
    id 'com.devsoap.plugin.vaadin' version '1.2.0'

If you are currently relying on the WAR packaging then this change will break your build as by default no WAR will be generated. To re-enable WAR packaging you need to include the war plugin in your project.

plugins {
    id 'org.springframework.boot' version '1.5.2.RELEASE'
    id 'com.devsoap.plugin.vaadin' version '1.2.0'
    id 'war'

#### Improved Groovy and Kotlin support

The support for creating and running Groovy projects has been added. While previously you had to use a separate plugin for groovy projects now the standard plugin supports it out-of-the-box. The old Groovy Vaadin plugin has been deprecated and will no longer be included. To read more about how to create a Groovy project see Creating a Groovy Project wiki article.

As a new language Kotlin has now been added as an officially supported language. The plugin can now create and run Kotlin projects out-of-the-box. For more information about how to create a Kotlin project see Creating a Kotlin Project wiki article.

Gradle build cache support

With Gradle 4.0 a new feature was introduced called Gradle Build Cache. The Gradle build cache allows us to cache task artifacts in an external cache that can be used to speed up consequent builds. In this release support for caching the widgetset has been added.

For more information about taking the build cache into use see Never Compile Your Widgetset Again With Gradle Build Cache.

Other smaller changes

  • Requires Gradle 4.0
  • Version checking is now done as a task that is executed once a day. Version checking also now supports proxy settings.
  • Support for using a custom Super Development Mode port
  • IE 8 and IE 9 GWT permutations removed by default
  • Improved support for addon packaged themes
  • Improved multi-module support for projects using classpath jar
  • Removed deprecated configurations classes
  • Plugin API documentation available at