Packaging a Theme for Reuse
A custom theme can be packaged into a JAR file for use in multiple applications as follows:
-
Create a new Maven project with the following structure and add your theme files to the theme folder (1):
[project root] ├── src │ └── main │ └── resources │ └── META-INF │ └── resources │ └── themes │ └── my-theme (1) └── pom.xml
ImportantDo not include generated theme fileDo not include the automatically generated<theme-name>.generated.js
file inside the packaged theme artifact. The file is automatically created in an application project that uses the theme. Including it in the theme can cause errors for such a project. -
Update
pom.xml
as follows:-
Add the Vaadin version property:
<vaadin.version>14.6.0</vaadin.version>
-
Add dependency management:
<dependencyManagement> <dependencies> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-bom</artifactId> <version>${vaadin.version}</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement>
-
Update dependencies to only contain the following:
<dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin</artifactId> <scope>provided</scope> </dependency>
-
-
If the theme uses npm assets, as described in Style Sheets From npm Packages, add a
Dependencies.java
class (1) with the corresponding@NpmPackage
annotations:[project root] └── src └── main └── java └── com └── vaadin └── flow └── theme └── Dependencies.java (1)
NoteDependency class packageThe package in which the java class is placed does not have to becom.vaadin.flow.theme
package as in the example above, but it is recommended for themes that are going to be used in Vaadin Spring Boot applications, as it is always automatically scanned. Other recommended packages arecom.vaadin.flow.component
andcom.vaadin.shrinkwrap
. See Vaadin’s Spring package scanning documentation for using other custom packages. -
Create the JAR with
mvn install
.
To use the packaged theme in an application, add the JAR as a dependency and apply the theme using the @Theme annotation.
4D77CF3D-9096-4659-A6E1-90E138353EE7