Reference Vaadin-specific plugin when generating a project with Vaadin
See original GitHub issueThe Vaadin Gradle Plugin is now available at https://github.com/vaadin/vaadin-gradle-plugin/ . The plugin will generate all files necessary for Vaadin to work properly, which will also fix spring-io/initializr#1122 .
When using Vaadin, could you please add the following line:
id 'com.vaadin' version '0.14.3.7'
tobuild.gradle
id("com.vaadin") version "0.14.3.7"
tobuild.gradle.kts
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Creating a Project in Eclipse | Framework | Vaadin 7 Docs
This section gives instructions for creating a new Eclipse project using the Vaadin Plugin. The task will include the following steps: Create a...
Read more >Starting a Vaadin Project with Gradle | Get Started - Vaadin
This tutorial describes how to create, compile, and run a Vaadin application using the Vaadin Gradle plugin. To run the application, ...
Read more >Deploying an Application | Framework | Vaadin 8 Docs - Vaadin
Creating Deployable WAR in Eclipse · Select File › Export and then Web › WAR File. Or, right-click the project in the Project...
Read more >Starting a Gradle Project | Get Started | Flow - Vaadin
This tutorial describes how to create, compile, and run a Vaadin application using the Vaadin Gradle Plugin. For running the application, ...
Read more >Creating a Project in Eclipse | Framework | Vaadin 8 Docs
This section gives instructions for creating a new Eclipse project using the Vaadin Plugin. The task will include the following steps:
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
🥳 Works like a charm! Tested both Maven and Gradle projects.
If we find out time to incorporate our Gradle plugin build to our “platform build” in the next quarter, we can probably start doing the same as Spring Boot Gradle plugin does: define the library versions there and cut a new version of the plugin on every library release. Then we can get the rid of the separate Vaadin version declaration that we currently have for both Spring Initialzr projects and in the base-starter example in our GitHub. This is what we could remove after this change: