/ Vaadin

What is new with Gradle Vaadin Plugin 0.10

Here are some of the most prominent features of the release:

Widgetset CDN support

The biggest new feature of 0.10 must be the new support for using pre-built widgetsets provided by http://cdn.virit.in instead of building the widgetset locally.

To use this feature there are a few requirements you need to be aware of before using it:

  1. You will need to set vaadin.widgetsetCDN=true in your build.gradle. This is to tell the plugin that you want to use the CDN instead of building the widgetset locally.

  2. You need to name your widgetset without any package prefix. 'mywidgetset' or 'widgetset01234' are okay, 'com.example.MyWidgetset' is not.

  3. Your widgetset can only contain addons provided by the Vaadin directory or Maven central. The way the CDN works is that if the widgetset you are requesting for your applicaiton does not previously exist in the CDN it will be built on-the-fly by using the addons from the directory or Maven central.

  4. You cannot have custom client side widgets inside your application. The reasoning here is the same as above, the CDN needs to have access to all client side logic when building the widgetset.

If your application meets these requirements turning on the widgetset CDN will speed up your build considerably as well as save you some CPU cycles on the build server.

Classpath Jar used by default on Windows

Many Windows users have hit the issue (#188) where the classpath has become too long for the project to be passed on the command line when compiling the widgetset. This is inherently a limitation on Windows where there is an upper bound of how long an argument can be (https://support.microsoft.com/en-us/kb/830473).

To resolve this issue the plugin will now by default on Windows use a so called "classpath jar", a jar with the manifest classpath set to the project classpath, to work around that issue. If you however feel you do not need it you can turn it off by using the vaadin.plugin.useClassPathJar = false.

Providing options as task parameters

The vaadinCreateProject-task now allows you to provide the name, package and widgetset parametes as command line options.

Example:

gradle vaadinCreateProject --name=HelloWorld --package=com.example --widgetset=com.example.HelloWorldWidgetset

The vaadinAddons-task also now allows you to use command line options instead of using the -P parameter.

Example:

gradle vaadinAddons --search=cdi --sort=rating --verbose

Other minor changes

Thanks to @epijnve's contribution you can now set the output directory of the GWT compiler with the project.vaadin.gwt.outputDirectory property.

The embedded Jetty version got updated from 9.2 to 9.3.