Embedding Liquibase in a Jar Using Spring

Question

I am getting a pretty specific error when trying to inject a pure Spring (not Spring Boot) application with lipibase into uberbar. As soon as the SpringLiquibase bean is initialized, it starts looking for something that I don't understand:

WARNING 7/16/15 3:22 PM: liquibase: No Liquibase-Packages entry found in MANIFEST.MF. Using fallback of entire 'liquibase' package WARNING 7/16/15 3:28 PM: liquibase: Error initializing SpringLiquibase java.io.FileNotFoundException: ServletContext resource [/liquibase] cannot be resolved to URL because it does not exist at org.springframework.web.context.support.ServletContextResource.getURL(ServletContextResource.java:156) at liquibase.integration.spring.SpringLiquibase$SpringResourceOpener.init(SpringLiquibase.java:117) at liquibase.resource.AbstractResourceAccessor.<init>(AbstractResourceAccessor.java:22) at liquibase.resource.ClassLoaderResourceAccessor.<init>(ClassLoaderResourceAccessor.java:19) at liquibase.integration.spring.SpringLiquibase$SpringResourceOpener.<init>(SpringLiquibase.java:74) at liquibase.integration.spring.SpringLiquibase.createResourceOpener(SpringLiquibase.java:489) at liquibase.integration.spring.SpringLiquibase.createLiquibase(SpringLiquibase.java:439) at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:389) WARNING 7/16/15 3:28 PM: liquibase: Error initializing SpringLiquibase java.io.FileNotFoundException: ServletContext resource [/liquibase] cannot be resolved to URL because it does not exist (stacktrace again) 

I know the Liquibase-Package entry in MANIFEST.MF and fill it with the shadow plugin (although I don’t understand what it has) and putting it with the shadow plugin, but it doesn’t have any effect, What is the search base and how am I can I overcome these mistakes?

Answer 1

According to this problem, this problem will be fixed if you create the src / main / webapp folder:

By the way, the main reason is that the src / main / webapp folder does not exist. At run time, you can create one or set a value in @WebAppConfiguration, which points to an existing classpath: folder.