Gain insights into building scalable applications with Thymeleaf and Spring Boot. Delve into Spring Data, Spring Security, and testing methods to ensure maintainable, portfolio-worthy projects.

maven.tar.gz

13SepBackgroundPostGres

DockerCompose14Sep

OptimizedMvn-22Sep

Moving into root - 24 Sep

From GitHub Repo - 12.4 - 24 Sep

Built from Github and running directly without watcher - 30Sep

Watcher - 29 Sep

From usercode directly - Oct 1

DockerCompose14Sep-Chapter09

OptimizedMvn-22Sep-Chapter11

DockerCompose14Sep-Chapter09-copy

Chapter09-Testing

Cypress

Chapter17-Testing

Cypress-copy

Integration Testing

Initial Chapters

Initial Chapters-copy

Watcher

Initial Chapters-Watcher

Integration Testing-copy

In this course, you will learn how to build easily scalable applications with Thymeleaf and Spring Boot. More specifically, you will combine Thymeleaf and Spring Boot with Spring Data and Spring Security. In a nutshell, this course will give you all the basics you need to start developing an application using Thymeleaf and Spring Boot.

Throughout the course, you will be building an application of a fictional basketball team called Thyme Wizards. Additionally, you will also learn to use unit and integration tests to ensure the proper code functionality and build a maintainable codebase that you can expand upon.

By the end, you will have a new project to add to your portfolio and some great new skills that employers will love.

Building Scalable Applications with Thymeleaf and Spring Boot

We're not done yet, though. If we try to start the application now, the `application.css` in `target/classes/static/css` will look exactly the same as the source we wrote without any of the processing. 

We have to configure [**Maven**](https://maven.apache.org/) so that everything works nicely together.

We can observe the `pom.xml` file in the project below and observe the addition of `frontend-maven-plugin` with the following changes:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.6.2</version>
        <relativePath/>
        
    </parent>
    <groupId>com.tamingthymeleaf</groupId>
    <artifactId>taming-thymeleaf-application</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <name>Taming Thymeleaf 04.02</name>
    <description>Example application for the Taming Thymeleaf book</description>
    <properties>
		<java.version>17</java.version>
		<frontend-maven-plugin.version>1.12.0</frontend-maven-plugin.version>
		<frontend-maven-plugin.nodeVersion>v16.13.1</frontend-maven-plugin.nodeVersion>
		<frontend-maven-plugin.npmVersion>8.1.2</frontend-maven-plugin.npmVersion>
    </properties>
    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-thymeleaf</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
            <exclusions>
                <exclusion>
                    <groupId>org.junit.vintage</groupId>
                    <artifactId>junit-vintage-engine</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
    </dependencies>
    <build>
        <resources>
            <resource>
                <directory>src/main/resources</directory>
                <excludes>
                    <exclude>**/*.html</exclude>
                    <exclude>**/*.css</exclude>
                    <exclude>**/*.js</exclude>
                </excludes>
            </resource>
        </resources>
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>com.github.eirslett</groupId>
                    <artifactId>frontend-maven-plugin</artifactId>
                    <version>${frontend-maven-plugin.version}</version>
                    <executions>
                        <execution>
                            <id>install-frontend-tooling</id>
                            <goals>
                                <goal>install-node-and-npm</goal>
                            </goals>
                            <configuration>
                                <nodeVersion>${frontend-mavenplugin.
nodeVersion}</nodeVersion>
                                <npmVersion>${frontend-mavenplugin.
npmVersion}</npmVersion>
                            </configuration>
                        </execution>
                        <execution>
                            <id>run-gulp-build</id>
                            <goals>
                                <goal>gulp</goal>
                            </goals>
                            <configuration>
                                <arguments>build</arguments>
                            </configuration>
                        </execution>
                    </executions>
                </plugin>
            </plugins>
        </pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
            <plugin>
                <groupId>com.github.eirslett</groupId>
                <artifactId>frontend-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>
    <profiles>
        <profile>
            <id>release</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>com.github.eirslett</groupId>
                        <artifactId>frontend-maven-plugin</artifactId>
                        <executions>
                            <execution>
                                <id>run-gulp-build</id>
                                <goals>
                                    <goal>gulp</goal>
                                </goals>
                                <configuration>
                                    <arguments>build --env production</arguments>
                                </configuration>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>

# Configuration

Note the changes made in the existing highlighted `pom.xml` file:

1. On **line 20**, we specify the `frontend-maven-plugin` version to use in a Maven property.
2. On **line 21**, we specify the version of node to use (use `node --version` to find out your current installed version).
3. On **line 22**, we specify the version of npm to use (use `npm --version` to find out your current installed version).
4. On **line 49**, we configure excludes for all HTML, Javascript and CSS files. We will copy those to the target/classes output directory via the `frontend-maven-plugin`, so we don’t want Maven itself to copy those.
5. On **line 63**, we configure the `frontend-maven-plugin`'s first execution to install npm and node so that the build
also works without installing those tools.
6. On **line 75**, we configure the second execution of the `frontend-maven-plugin` to run the Gulp build.
7. On **line 93**, we add the `frontend-maven-plugin` to run by default (it is bound to the `generate-resources` Maven lifecycle phase by default).
8. On **line 108**, we configure Maven so that when using the `release` profile, the `gulp build --env production` is run when using the release profile so that we have our minified CSS when building a release version.

# Live reload
With this setup, we also have support for live reload of the browser when HTML, Javascript, or CSS changes.

To make that fully work, we need to disable the caching of Thymeleaf templates that is enabled by default.
Additionally, we need to implement a cache-busting mechanism using the `spring.web.resources.chain.strategy.content.*` properties.

We can add the following to the `application.properties` file:



Learn to configure the CSS incorporation by configuring Maven.

Configuring Maven

Configure Maven

Getting Started

What are Spring Boot and Thymeleaf?

Thymeleaf Introduction

Thyme Wizards

Fragments

Layouts

Controllers

Internationalization

Database Connection

Displaying Data

Forms

Data Editing

Implement Deletion of an Entity

Security

Security - Users from Database

Testing

Testing Using Cypress

Various Tips and Tricks - I

Various Tips and Tricks - II

Conclusion

Appendix

Configure Maven