Alright, so you have been bitten by the Spring Boot bug and want to write your Vaadin applications using Spring Boot and Gradle. How would you get started? 1. Create a Gradle Spring Boot project First off create a standard Gradle project with a build.gradle file and nothing else and add the following to build.gradle: // build.gradle buildscript { repositories { maven { url "https://plugins.gradle.org/m2/" } } dependencies { classpath("org.springframework.boot:spring-boot-gradle-plugin:1.4.0.RELEASE") classpath "fi.jasoft.plugin:gradle-vaadin-plugin:0.11.4" } } apply plugin: 'spring-boot' apply plugin: 'fi.jasoft.plugin.vaadin' repositories { maven { url "http://repo. »
Quarz Job Scheduler If you have worked with enterprise applications in the past you have most likely at some point in time needed to schedule some jobs to run at either some interval or possibly at some specific point in time. One of the go-to solutions to do this has for a long time been using the Quarz Job Scheduler. Here is an example of a typical Quarz job you might create: class MyJob implements Job { @Override void execute(JobExecutionContext context){ // Execute some code } } and then in your application you would schedule it pretty much like this class MyApp { void »
So you started out with creating a new Vaadin project in Eclipse and it created a Maven project and after a while you have noticed it isn't working out for you and want to switch to Gradle to make your life easier. The good news is that Gradle provides great tooling for upgrading your project from Maven to Gradle and with the Gradle Vaadin plugin you will be happily running with Gradle in no time. To demonstrate the approach I have taken the Vaadin Spreadsheet tutorial provided by Vaadin over at https://github.com/vaadin/spreadsheet-tutorial. It is a typical »
Gradle Vaadin Plugin 0.11 is probably the biggest release since the first version of the plugin came out nearly 4 years ago. Many things under the hood has changed and improved, mostly because of improvements in Gradle itself, but also new features have been added which will help especially those in a more enterprise project. But lets have a look at the major features this release brings. Java 8 and Gradle 2.12 required To be able to make many of the improvements made in 0.11 new features of Gradle needed to be used. That meant that the »
Changes in how dependencies are handled As you all most likely know the plug-in will inject the required vaadin dependencies into the build so you can start developing with Vaadin without any whatsoever knowledge about what dependencies are needed. The plug-in by default takes care of that for you. However, the way the dependencies were injected was never a supported solution and it had its flaws. One of the major flaws was that while it worked flawlessly if you were using the Gradle eclipse or idea plug-ins it didn't work so well if you were using the third party Eclipse »