# Liquibase command-line issues with Spring Boot fat jar **URL:** \ **Category:** General Discussion\ **Created:** [September 20, 2024, 8:53pm UTC](https://forum.liquibase.org/t/liquibase-command-line-issues-with-spring-boot-fat-jar/9771 "2024-09-20T20:53:09Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![pards](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@pards](https://forum.liquibase.org/u/pards)\ **Post date:** [September 20, 2024, 8:53pm UTC](https://forum.liquibase.org/t/liquibase-command-line-issues-with-spring-boot-fat-jar/9771/1 "2024-09-20T20:53:09Z")
I’m trying to use the liquibase command-line to generate SQL to send to our DBAs. It works fine for regular JAR files - I drop them into the liquibase\_libs folder, run the CLI, and everything works. However, this process doesn’t work for Spring Boot fat JARs because they have a different folder structure so Liquibase is unable to locate the changelog. If I extract the changelog and specify it directly, then Liquibase can’t find the migration scripts because they’re not in the root of the JAR - they’re under the BOOT-INF/classes folder. I tried add “–search-path BOOT-INF/classes” to the Liquibase command-line but it seems that is only for disk locations, not directories inside the JAR file. Is there a workaround for this? ---
**Author:** ![pards](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@pards](https://forum.liquibase.org/u/pards)\ **Post date:** [September 25, 2024, 6:10pm UTC](https://forum.liquibase.org/t/liquibase-command-line-issues-with-spring-boot-fat-jar/9771/2 "2024-09-25T18:10:03Z")
I have created a sample project demonstrating the issue > **[GitHub - pards/liquibase-defect: Code to demo Liquibase defect with Spring fat jars](https://github.com/pards/liquibase-defect)** > > Code to demo Liquibase defect with Spring fat jars