We Keep Coding

Spring Boot Properties Migrator

I'm trying to run an application(spring boot v1.5.9.0) with dependency:
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-properties-migrator</artifactId>
<scope>runtime</scope>
</dependency>
and getting this error:
org.springframework.boot.SpringApplication - Application startup failed
java.lang.NoClassDefFoundError: org/springframework/boot/context/properties/source/ConfigurationPropertySources
this error, apparently, did not occur before. How do I make the migrator work?
Do I have to change the spring-boot version to 2x before running the migrator?
If so, i don't really get the migrator usage.
As its scope is runtime - I have to make the app run before including it - which means I have to solve all the errors without migrator's advice? What do I use it for afterwards?

You've stated that you're running spring boot v1.5.9.0
It doesn't make sense to run the properties migrator with spring boot 1.5.x. Its primary intention is to "assist" in properties migrations that have changed during migration of spring boot 1.x to spring boot 2.x
As for the error, this specific class is available only since spring boot 2.0. See the comment #since in the sourcefile

In your project, application.properties or application.yml is present or not? Spring boot is auto-configuration. I think those properties will be expecting..Also check what are the annotations used in Spring boot main class..Share that Spring boot main class as well..will check

intellij spring boot run cannot load application.yml automatically

my application.yml locate
my application.yml
spring boot run server port
Intellij spring boot run configuration
Hi.
My project is Intellij spring boot 1.5.7 Gradle Project
When Intellij spring boot run cannot load application.yml automatically.
but gradle bootRun is very well run&load.
Please suggestion me.

You should specify profile configuration. From your application.yml, you have multiple configuration separated by "---", this is used for multiple profile configuration for different spring profile. Try removing "---" and specify profile as following :
Multiple configuration is used when you have different configuration for different profile, as following:

Exclude Jhipster and upgrade Spring Boot from 1.4.0 to 2.0.3

I am using spring boot 1.4.0 along with jhipster 3.6.1 in my project. I want to upgrade spring boot from 1.4.0 to 2.0.3 but I found some release notes of jhipster according to which it won't support Spring boot 2.0.3.
Can anyone help me out by letting me know if there is any easy and quick way to exclude jhipster from my project.

JHipster 3 won't be updated for Spring Boot 2, only JHipster 5 supports it.
So either you upgrade your project to JHipster 5 using jhipster upgrade command or you remove all dependencies from JHipster and you manually upgrade your project.
These dependencies can be of 3 types: BOM for maven dependencies, server library and client library (not required for your use case). For BOM and server library, the idea is to retrieve the source of the version used by your app and to integrate it into your own git repo so that you can modify it.

flowable integration break jhipster maven integration tests

I have created a jhipster micro service with maven and add some entities using import-jdl. Everything was working perfectly fine with maven integration tests automatically generated.
Now I would like to integrate flowable and after adding flowable-spring-boot-starter-basic:6.3.1.
But I get error:
org.hibernate.tool.schema.spi.SchemaManagementException:
Schema-validation: missing table
Versions:
jhipster version 5.0.1
flowable version 6.3.1
What i understand is that liquibase configuration of flowable is creating problems on jhipster liquibase configuration. Am I right?

flowable desactivate by default liquibase with spring boot.
You have to add the property liquibase.enabled = true

How to correctly create a simple Spring project running in the console using the last STS version (3.8.4.RELEASE)?

today I downloaded the last STS version (3.8.4.RELEASE) and I have some doubts because it seems to me that something is changed.
I have to create a simple batch application (running in the console).
It seems to me that to create this kind of project in this new realease I have to do:
File --> Spring Legacy Project --> Simple Spring Maven
It seems to me that there is no other way to create a simple console project. Why this kind of project are putted under the Spring Legacy Project? Can I do the same thing in a more modern way?
Another doubt is related to the Spring Version into the pom.xml file:
<spring-framework.version>3.2.3.RELEASE</spring-framework.version>
Why the default version is the 3.2.3.RELEASE? Can I replace it with the more m odern Spring 4^

As its name says "Spring Legacy Project" is a legacy functionality. It create old Spring projects.
Spring now is promoting Spring Boot applications, these applications have everything you need configured by default. You only need to add the dependencies that you need.
Now you need to use:
File -- > New -- Spring Starter Project
On the first view you configure the project. Where is located, maven or gradle, etc.
On the second view you choose the libraries that you will use in your porject. You choose if it is a web project, or if you need jdbc or jpa, or batch processing.
In your case, if you don't need a web application, you just don't added to the project.
You can see more about Spring boot here
https://projects.spring.io/spring-boot/