Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class the @SpringBootApplication annotation if your main class is in the root package. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 232 Using a custom layout ..................................................................................... 232 67.8. Understanding BUILD-SNAPSHOT Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 232 Using a custom layout ..................................................................................... 232 67.8. Understanding RELEASE Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 232 Using a custom layout ..................................................................................... 232 67.8. Understanding RELEASE Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 230 Using a custom layout ..................................................................................... 230 67.8. Understanding RELEASE Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When the @SpringBootApplication annotation if your main class is in the root package. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class the @SpringBootApplication annotation if your main class is in the root package. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 232 Using a custom layout ..................................................................................... 232 67.8. Understanding RELEASE Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain