Red Hat SummitChapter 3. Spring Boot Maven Plugin
The Spring Boot Maven Plugin provides Spring Boot support in Apache Maven. You must have Maven 3.6.3 or later to use it
The Spring Boot Maven Plugin allows you to package executable jar or war archives, run Spring Boot applications, generate build information and start your Spring Boot application prior to running integration tests.
3.1. Getting Started
To use the Spring Boot Maven Plugin, include the appropriate XML in the plugins section of your pom.xml, as shown in the following example:
<project>
<modelVersion>4.14.0</modelVersion>
<artifactId>getting-started</artifactId>
<!-- ... -->
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
</project>3.2. Using the Plugin
Maven users can inherit from the spring-boot-starter-parent project to obtain sensible defaults. The parent project provides the following features:
- Java 17 as the default compiler level.
- UTF-8 source encoding.
-
Compilation with
-parameters. -
A dependency management section, inherited from the
spring-boot-dependenciesPOM, that manages the versions of common dependencies. This dependency management lets you omit<version>tags for those dependencies when used in your own POM. -
An execution of the
repackagegoal with arepackageexecution id. -
A
nativeprofile that configures the build to be able to generate a Native image. - Sensible resource filtering.
-
Sensible plugin configuration ({url-git-commit-id-maven-plugin}[
Git Commit Id Plugin], and shade). -
Sensible resource filtering for
application.propertiesandapplication.ymlincluding profile-specific files (for example,application-dev.propertiesandapplication-dev.yml)
Since the application.properties and application.yml files accept Spring style placeholders (${…}), the Maven filtering is changed to use @..@ placeholders.
(You can override that by setting a Maven property called resource.delimiter.)
The spring-boot-starter-parent sets the maven.compiler.release property, which restricts the --add-exports, --add-reads, and --patch-module options if they modify system modules. In case you need to use those options, unset maven.compiler.release:
<maven.compiler.release></maven.compiler.release>and then configure the source and the target options instead:
<maven.compiler.source>${java.version}</maven.compiler.source>
<maven.compiler.target>${java.version}</maven.compiler.target>3.2.1. Inheriting the Starter Parent POM
To configure your project to inherit from the spring-boot-starter-parent, set the parent as follows:
<!-- Inherit defaults from Spring Boot -->
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>3.5.11</version>
</parent>You only need to specify the Spring Boot version number on this dependency.
If you import additional starters, you can safely omit the version number.
With that setup, you can also override individual dependencies by overriding a property in your own project. For instance, to use a different version of the SLF4J library and the Spring Data release train, you would add the following to your pom.xml:
<properties>
<slf4j.version>2.0.17</slf4j.version>
<spring-data-bom.version>2025.0.5</spring-data-bom.version>
</properties>Browse the Dependency Versions Properties section in the Spring Boot reference for a complete list of dependency version properties.
Each Spring Boot release is designed and tested against a specific set of third-party dependencies. Overriding versions may cause compatibility issues and should be done with care.
3.2.2. Using Spring Boot without the Parent POM
There may be reasons for you not to inherit from the spring-boot-starter-parent POM. You may have your own corporate standard parent that you need to use or you may prefer to explicitly declare all your Maven configuration.
If you do not want to use the spring-boot-starter-parent, you can still keep the benefit of the dependency management (but not the plugin management) by using an import scoped dependency, as follows:
<dependencyManagement>
<dependencies>
<dependency>
<!-- Import dependency management from Spring Boot -->
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>3.5.11</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
The preceding sample setup does not let you override individual dependencies by using properties, as explained above. To achieve the same result, you need to add entries in the dependencyManagement section of your project before the spring-boot-dependencies entry. For instance, to use a different version of the SLF4J library and the Spring Data release train, you could add the following elements to your pom.xml:
<dependencyManagement>
<dependencies>
<!-- Override SLF4J provided by Spring Boot -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.30</version>
</dependency>
<!-- Override Spring Data release train provided by Spring Boot -->
<dependency>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-bom</artifactId>
<version>2024.1.10</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>3.5.11</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>3.2.3. Overriding Settings on the Command Line
The plugin offers a number of user properties, starting with spring-boot, to let you customize the configuration from the command line.
For instance, you could tune the profiles to enable when running the application as follows:
$ mvn spring-boot:run -Dspring-boot.run.profiles=dev,localIf you want to both have a default while allowing it to be overridden on the command line, you should use a combination of a user-provided project property and MOJO configuration.
<project>
<properties>
<app.profiles>local,dev</app.profiles>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<profiles>${app.profiles}</profiles>
</configuration>
</plugin>
</plugins>
</build>
</project>
The above makes sure that local and dev are enabled by default. Now a dedicated property has been exposed, this can be overridden on the command line as well:
$ mvn spring-boot:run -Dapp.profiles=test3.3. Goals
The Spring Boot Plugin has the following goals:
| Goal | Description |
|---|---|
| spring-boot:build-image | Package an application into an OCI image using a buildpack, forking the lifecycle to make sure that package ran. This goal is suitable for command-line invocation. If you need to configure a goal execution in your build, use build-image-no-fork instead. |
| spring-boot:build-image-no-fork | Package an application into an OCI image using a buildpack, but without forking the lifecycle. This goal should be used when configuring a goal execution in your build. To invoke the goal on the command-line, use build-image instead. |
| spring-boot:build-info | Generate a build-info.properties file based on the content of the current MavenProject. |
| spring-boot:help | Display help information on spring-boot-maven-plugin. Call mvn spring-boot:help -Ddetail=true -Dgoal=<goal-name> to display parameter details. |
| spring-boot:process-aot | Invoke the AOT engine on the application. |
| spring-boot:process-test-aot | Invoke the AOT engine on tests. |
| spring-boot:repackage | Repackage existing JAR and WAR archives so that they can be executed from the command line using java -jar. With layout=NONE can also be used simply to package a JAR with nested dependencies (and no main class, so not executable). |
| spring-boot:run | Run an application in place. |
| spring-boot:start | Start a spring application. Contrary to the run goal, this does not block and allows other goals to operate on the application. This goal is typically used in integration test scenario where the application is started before a test suite and stopped after. |
| spring-boot:stop | Stop an application that has been started by the "start" goal. Typically invoked once a test suite has completed. |
| spring-boot:test-run | Run an application in place using the test runtime classpath. The main class that will be used to launch the application is determined as follows: The configured main class, if any. Then the main class found in the test classes directory, if any. Then the main class found in the classes directory, if any. |
3.4. Running your Application with Maven
The plugin includes a run goal which can be used to launch your application from the command line, as shown in the following example:
$ mvn spring-boot:run
Application arguments can be specified using the arguments parameter.
The application is executed in a forked process and setting properties on the command-line will not affect the application. If you need to specify some JVM arguments (that is for debugging purposes), you can use the jvmArguments parameter, see Debug the application for more details. There is also explicit support for system properties and environment variables.
As enabling a profile is quite common, there is dedicated profiles property that offers a shortcut for -Dspring-boot.run.jvmArguments="-Dspring.profiles.active=dev", see Specify active profiles.
Spring Boot devtools is a module to improve the development-time experience when working on Spring Boot applications. To enable it, just add the following dependency to your project:
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<optional>true</optional>
</dependency>
</dependencies>
When devtools is running, it detects changes when you recompile your application and automatically refreshes it. This works for not only resources but code as well. It also provides a LiveReload server so that it can automatically trigger a browser refresh whenever things change.
Devtools can also be configured to only refresh the browser whenever a static resource has changed (and ignore any change in the code). Just include the following property in your project:
spring.devtools.remote.restart.enabled=false
Prior to devtools, the plugin supported hot refreshing of resources by default which has now been disabled in favour of the solution described above. You can restore it at any time by configuring your project:
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<addResources>true</addResources>
</configuration>
</plugin>
</plugins>
</build>
When addResources is enabled, any src/main/resources directory will be added to the application classpath when you run the application and any duplicate found in the classes output will be removed. This allows hot refreshing of resources which can be very useful when developing web applications. For example, you can work on HTML, CSS or JavaScript files and see your changes immediately without recompiling your application. It is also a helpful way of allowing your front end developers to work without needing to download and install a Java IDE.
A side effect of using this feature is that filtering of resources at build time will not work.
In order to be consistent with the repackage goal, the run goal builds the classpath in such a way that any dependency that is excluded in the plugin’s configuration gets excluded from the classpath as well.
Sometimes it is useful to run a test variant of your application.
Use the test-run goal with many of the same features and configuration options as run for this purpose.
3.4.1. spring-boot:run
org.springframework.boot:spring-boot-maven-plugin:3.5.6
Run an application in place.
3.4.1.1. Required parameters
| Name | Type | Default |
|---|---|---|
| classesDirectory |
|
|
3.4.1.2. Optional parameters
| Name | Type | Default |
|---|---|---|
| addResources |
|
|
| additionalClasspathElements |
| |
| arguments |
| |
| commandlineArguments |
| |
| environmentVariables |
| |
| excludeGroupIds |
| |
| excludes |
| |
| includes |
| |
| jvmArguments |
| |
| mainClass |
| |
| noverify |
| |
| optimizedLaunch |
|
|
| skip |
|
|
| systemPropertyVariables |
| |
| useTestClasspath |
|
|
| workingDirectory |
|
3.4.1.3. Parameter details
3.4.1.3.1. addResources
Add maven resources to the classpath directly, this allows live in-place editing of resources. Duplicate resources are removed from target/classes to prevent them from appearing twice if ClassLoader.getResources() is called. Please consider adding spring-boot-devtools to your project instead as it provides this feature and many more.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
|
3.4.1.3.2. additionalClasspathElements
Additional classpath elements that should be added to the classpath. An element can be a directory with classes and resources or a jar file.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.3. agents
Path to agent jars.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.4. arguments
Arguments that should be passed to the application.
| Name |
|
| Type |
|
| Default value | |
| User property | |
| Since |
|
3.4.1.3.5. classesDirectory
Directory containing the classes and resource files that should be used to run the application.
| Name |
|
| Type |
|
| Default value |
|
| User property | |
| Since |
|
3.4.1.3.6. commandlineArguments
Arguments from the command line that should be passed to the application. Use spaces to separate multiple arguments and make sure to wrap multiple values between quotes. When specified, takes precedence over #arguments.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.7. environmentVariables
List of Environment variables that should be associated with the forked process used to run the application.
| Name |
|
| Type |
|
| Default value | |
| User property | |
| Since |
|
3.4.1.3.8. excludeGroupIds
Comma separated list of groupId names to exclude (exact match).
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.9. excludes
Collection of artifact definitions to exclude. The Exclude element defines mandatory groupId and artifactId components and an optional classifier component. When configured as a property, values should be comma-separated with colon-separated components: groupId:artifactId,groupId:artifactId:classifier
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.10. includes
Collection of artifact definitions to include. The Include element defines mandatory groupId and artifactId components and an optional classifier component. When configured as a property, values should be comma-separated with colon-separated components: groupId:artifactId,groupId:artifactId:classifier
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.11. jvmArguments
JVM arguments that should be associated with the forked process used to run the application. On command line, make sure to wrap multiple values between quotes.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.12. mainClass
The name of the main class. If not specified the first compiled class found that contains a 'main' method will be used.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.13. noverify
Flag to say that the agent requires -noverify.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.14. optimizedLaunch
Whether the JVM’s launch should be optimized.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
|
3.4.1.3.15. profiles
The spring profiles to activate. Convenience shortcut of specifying the 'spring.profiles.active' argument. On command line use commas to separate multiple profiles.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.1.3.16. skip
Skip the execution.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
|
3.4.1.3.17. systemPropertyVariables
List of JVM system properties to pass to the process.
| Name |
|
| Type |
|
| Default value | |
| User property | |
| Since |
|
3.4.1.3.18. useTestClasspath
Flag to include the test classpath when running.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
|
3.4.1.3.19. workingDirectory
Current working directory to use for the application. If not specified, basedir will be used.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2. spring-boot:test-run
org.springframework.boot:spring-boot-maven-plugin:3.5.6
Run an application in place using the test runtime classpath. The main class that will be used to launch the application is determined as follows: The configured main class, if any. Then the main class found in the test classes directory, if any. Then the main class found in the classes directory, if any.
3.4.2.1. Required parameters
| Name | Type | Default |
|---|---|---|
| classesDirectory |
|
|
| testClassesDirectory |
|
|
3.4.2.2. Optional parameters
| Name | Type | Default |
|---|---|---|
| addResources |
|
|
| additionalClasspathElements |
| |
| arguments |
| |
| commandlineArguments |
| |
| environmentVariables |
| |
| excludeGroupIds |
| |
| excludes |
| |
| includes |
| |
| jvmArguments |
| |
| mainClass |
| |
| noverify |
| |
| optimizedLaunch |
|
|
| profiles |
| |
| skip |
|
|
| systemPropertyVariables |
| |
| workingDirectory |
|
3.4.2.3. Parameter details
3.4.2.3.1. addResources
Add maven resources to the classpath directly, this allows live in-place editing of resources. Duplicate resources are removed from target/classes to prevent them from appearing twice if ClassLoader.getResources() is called. Please consider adding spring-boot-devtools to your project instead as it provides this feature and many more.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
|
3.4.2.3.2. additionalClasspathElements
Additional classpath elements that should be added to the classpath. An element can be a directory with classes and resources or a jar file.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.3. agents
Path to agent jars.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.4. arguments
Arguments that should be passed to the application.
| Name |
|
| Type |
|
| Default value | |
| User property | |
| Since |
|
3.4.2.3.5. classesDirectory
Directory containing the classes and resource files that should be used to run the application.
| Name |
|
| Type |
|
| Default value |
|
| User property | |
| Since |
|
3.4.2.3.6. commandlineArguments
Arguments from the command line that should be passed to the application. Use spaces to separate multiple arguments and make sure to wrap multiple values between quotes. When specified, takes precedence over #arguments.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.7. environmentVariables
List of Environment variables that should be associated with the forked process used to run the application.
| Name |
|
| Type |
|
| Default value | |
| User property | |
| Since |
|
3.4.2.3.8. excludeGroupIds
Comma separated list of groupId names to exclude (exact match).
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.9. excludes
Collection of artifact definitions to exclude. The Exclude element defines mandatory groupId and artifactId components and an optional classifier component. When configured as a property, values should be comma-separated with colon-separated components: groupId:artifactId,groupId:artifactId:classifier
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.10. includes
Collection of artifact definitions to include. The Include element defines mandatory groupId and artifactId components and an optional classifier component. When configured as a property, values should be comma-separated with colon-separated components: groupId:artifactId,groupId:artifactId:classifier
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.11. jvmArguments
JVM arguments that should be associated with the forked process used to run the application. On command line, make sure to wrap multiple values between quotes.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.12. mainClass
The name of the main class. If not specified the first compiled class found that contains a 'main' method will be used.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.13. noverify
Flag to say that the agent requires -noverify.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.14. optimizedLaunch
Whether the JVM’s launch should be optimized.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
3.4.2.3.15. profiles
The spring profiles to activate. Convenience shortcut of specifying the 'spring.profiles.active' argument. On command line use commas to separate multiple profiles.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.2.3.16. skip
Skip the execution.
| Name |
|
| Type |
|
| Default value |
|
| User property |
|
| Since |
|
3.4.2.3.17. systemPropertyVariables
List of JVM system properties to pass to the process.
| Name |
|
| Type |
|
| Default value | |
| User property | |
| Since |
|
3.4.2.3.18. testClassesDirectory
Directory containing the test classes and resource files that should be used to run the application.
| Name |
|
| Type |
|
| Default value |
|
| User property | |
| Since |
3.4.2.3.19. workingDirectory
Current working directory to use for the application. If not specified, basedir will be used.
| Name |
|
| Type |
|
| Default value | |
| User property |
|
| Since |
|
3.4.3. Examples
3.4.3.1. Debug the Application
The run and test-run goals run your application in a forked process. If you need to debug it, you should add the necessary JVM arguments to enable remote debugging. The following configuration suspend the process until a debugger has joined on port 5005:
<project>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<jvmArguments>
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005
</jvmArguments>
</configuration>
</plugin>
</plugins>
</build>
</project>These arguments can be specified on the command line as well:
$ mvn spring-boot:run -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:50053.4.3.2. Using System Properties
System properties can be specified using the systemPropertyVariables attribute. The following example sets property1 to test and property2 to 42:
<project>
<build>
<properties>
<my.value>42</my.value>
</properties>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<systemPropertyVariables>
<property1>test</property1>
<property2>${my.value}</property2>
</systemPropertyVariables>
</configuration>
</plugin>
</plugins>
</build>
</project>
If the value is empty or not defined (that is <my-property/>), the system property is set with an empty String as the value. Maven trims values specified in the pom, so it is not possible to specify a System property which needs to start or end with a space through this mechanism: consider using jvmArguments instead.
Any String typed Maven variable can be passed as system properties. Any attempt to pass any other Maven variable type (for example a List or a URL variable) will cause the variable expression to be passed literally (unevaluated).
The jvmArguments parameter takes precedence over system properties defined with the mechanism above. In the following example, the value for property1 is overridden:
$ mvn spring-boot:run -Dspring-boot.run.jvmArguments="-Dproperty1=overridden"3.4.3.3. Using Environment Variables
Environment variables can be specified using the environmentVariables attribute. The following example sets the 'ENV1', 'ENV2', 'ENV3', 'ENV4' env variables:
<project>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<environmentVariables>
<ENV1>5000</ENV1>
<ENV2>Some Text</ENV2>
<ENV3/>
<ENV4></ENV4>
</environmentVariables>
</configuration>
</plugin>
</plugins>
</build>
</project>
If the value is empty or not defined (that is <MY_ENV/>), the env variable is set with an empty String as the value. Maven trims values specified in the pom so it is not possible to specify an env variable which needs to start or end with a space.
Any String typed Maven variable can be passed as system properties. Any attempt to pass any other Maven variable type (for example a List or a URL variable) will cause the variable expression to be passed literally (unevaluated).
Environment variables defined this way take precedence over existing values.
3.4.3.4. Using Application Arguments
Application arguments can be specified using the arguments attribute. The following example sets two arguments: property1 and property2=42:
<project>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<arguments>
<argument>property1</argument>
<argument>property2=${my.value}</argument>
</arguments>
</configuration>
</plugin>
</plugins>
</build>
</project>
On the command-line, arguments are separated by a space the same way jvmArguments are. If an argument contains a space, make sure to quote it. In the following example, two arguments are available: property1 and property2=Hello World:
$ mvn spring-boot:run -Dspring-boot.run.arguments="property1 'property2=Hello World'"3.4.3.5. Specify Active Profiles
The active profiles to use for a particular application can be specified using the profiles argument.
The following configuration enables the local and dev profiles:
<project>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<profiles>
<profile>local</profile>
<profile>dev</profile>
</profiles>
</configuration>
</plugin>
</plugins>
</build>
</project>The profiles to enable can be specified on the command line as well, make sure to separate them with a comma, as shown in the following example:
$ mvn spring-boot:run -Dspring-boot.run.profiles=local,dev
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}