Issue in spring-boot war startup in external tomcat due to unwanted spring jar
I am trying to run an spring-boot web application war file in external tomcat where many other applications (Spring and not spring-boot) are already running. There are some dependencies at some shared location on same server which is loaded into application at runtime which is configured in catalina.properties file common.loader
Issue in spring-boot war startup in external tomcat due to unwanted spring jar
I am trying to run an spring-boot web application war file in external tomcat where many other applications (Spring and not spring-boot) are already running. There are some dependencies at some shared location on same server which is loaded into application at runtime which is configured in catalina.properties file common.loader
Import Beans from custom library to springbootAplication from a different project
I have been struggling trying to create a library with the use of the beans from it to a different project and call a method from it
Publishing a Spring Boot application on a production server and managing updates
I would like to ask about the experience of a production run of a Spring Boot web application, with embeded Tomcat, based on Maven or Gradle. So far I have been working with a vanilla Spring application, deployed on Tomcat, without dependencies manager, with all external jars collected in /WEB-INF/lib/
.