name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the the section called “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the Section 55.3, “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the the section called “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the Section 58.3, “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the the section called “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the Section 58.3, “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the Section 58.3, “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the the section called “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the the section called “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application

name=MyApp app.description=${app.name} is a Spring Boot application Tip You can also use this technique to create “short” variants of existing Spring Boot properties. See the Section 58.3, “Use “short” libraries. This useful technique allows Groovy to download jars in the same way as Maven or Gradle would; but without requiring you to use a build tool. Spring Boot extends this technique further, and will allows you to easily use multiple files from a single directory, e.g. $ spring run *.groovy This technique can also be useful if you want to segregate your “test” or “spec” code from the main application