You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A wonderful set of all handy stuff to create a project with all the required stuffs to jump-start a spring boot project. Thanks!
I tried this running it as such on a Windows machine. The /h2/alerts_db.mv.db file must be ideally created on the first write after the start of the application. But due to some reason, the file is not getting created and hence the data is not getting persisted. Tried updating the ddl-auto: update to ddl-auto: create. Still not much joy. Not sure what got missed in the archetype generation.
Figured out the issue:
Spring Boot 2.1.x will not work out of the box with spring-cloud Finchley.RELEASE <spring-cloud.version>Finchley.RELEASE</spring-cloud.version>
Hence, change Finchley.RELEASE with Greenwitch.RELEASE <spring-cloud.version>Greenwich.RELEASE</spring-cloud.version>
and completely remove the buggy fix of HikariCP exclusion under spring-boot-starter-data-jpa
<!-- fix conflict between spring cloud config server and spring boot JPA-->
<exclusions>
<exclusion>
<groupId>com.zaxxer</groupId>
<artifactId>HikariCP</artifactId>
</exclusion>
</exclusions>
The text was updated successfully, but these errors were encountered:
A wonderful set of all handy stuff to create a project with all the required stuffs to jump-start a spring boot project. Thanks!
I tried this running it as such on a Windows machine. The /h2/alerts_db.mv.db file must be ideally created on the first write after the start of the application. But due to some reason, the file is not getting created and hence the data is not getting persisted. Tried updating the ddl-auto: update to ddl-auto: create. Still not much joy. Not sure what got missed in the archetype generation.
Figured out the issue:
Spring Boot 2.1.x will not work out of the box with spring-cloud Finchley.RELEASE
<spring-cloud.version>Finchley.RELEASE</spring-cloud.version>
Hence, change Finchley.RELEASE with Greenwitch.RELEASE
<spring-cloud.version>Greenwich.RELEASE</spring-cloud.version>
and completely remove the buggy fix of HikariCP exclusion under spring-boot-starter-data-jpa
The text was updated successfully, but these errors were encountered: