classpath scanner does not find db.migration package or resources #1261

pabl0rg · 2016-03-29T21:21:34Z

What version of Flyway are you using?

4.0

What operating system are you using?

MacOS

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
If i run the following (kotlin) class from a jar file (the db.migration package & resources are part of the same jar):

            val flyway = Flyway()
            flyway.baselineDescription = "Initialize Flyway (${Version.getVersion()})"
            flyway.setBaselineVersionAsString("1.9.30")
            val (url, user, password) = DBUser.getConnectionInfo("web")
            flyway.setDataSource(url, user, password)
            flyway.target = MigrationVersion.fromVersion(Version.getShortVersion())
            flyway.isBaselineOnMigrate = true
            flyway.migrate()

I get the following, confusing log messages:

INFO [org.flywaydb.core.internal.util.VersionPrinter] Flyway 4.0 by Boxfuse
INFO [org.flywaydb.core.internal.dbsupport.DbSupportFactory] Database: jdbc:postgresql://127.0.0.1:5432/fms (PostgreSQL 9.3)
DEBUG [org.flywaydb.core.Flyway] DDL Transactions Supported: true
DEBUG [org.flywaydb.core.Flyway] Schema: public
DEBUG [org.flywaydb.core.internal.util.FeatureDetector] Spring Jdbc available: false
DEBUG [org.flywaydb.core.internal.callback.SqlScriptFlywayCallback] Scanning for SQL callbacks ...
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classpath resources at 'classpath:db/migration' (Prefix: '', Suffix: '.sql')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Determining location urls for classpath:db/migration using ClassLoader sun.misc.Launcher$AppClassLoader@4e0e2f2a ...
WARN [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Unable to resolve location classpath:db/migration
DEBUG [org.flywaydb.core.internal.command.DbValidate] Validating migrations ...
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classpath resources at 'classpath:db/migration' (Prefix: 'V', Suffix: '.sql')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classpath resources at 'classpath:db/migration' (Prefix: 'R', Suffix: '.sql')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classes at 'classpath:db/migration' (Implementing: 'org.flywaydb.core.api.migration.jdbc.JdbcMigration')
INFO [org.flywaydb.core.internal.command.DbValidate] Successfully validated 1 migration (execution time 00:00.042s)
DEBUG [org.flywaydb.core.internal.command.DbSchemas] Schema "public" already exists. Skipping schema creation.
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Locking table "public"."schema_version"...
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Lock acquired for table "public"."schema_version"
INFO [org.flywaydb.core.internal.command.DbMigrate] Current version of schema "public": 1.9.30
INFO [org.flywaydb.core.internal.command.DbMigrate] Schema "public" is up to date. No migration necessary.

The messages are very confusing because first there's a WARN saying the location of db/migration could not be found, and later an INFO message saying 2 migrations were validated. Either way, no migrations run.

If i unzip the jar file and then run the same class, the log messages are different and the migrations actually get run

INFO [org.flywaydb.core.internal.util.VersionPrinter] Flyway 4.0 by Boxfuse
INFO [org.flywaydb.core.internal.dbsupport.DbSupportFactory] Database: jdbc:postgresql://127.0.0.1:5432/fms (PostgreSQL 9.3)
DEBUG [org.flywaydb.core.Flyway] DDL Transactions Supported: true
DEBUG [org.flywaydb.core.Flyway] Schema: public
DEBUG [org.flywaydb.core.internal.util.FeatureDetector] Spring Jdbc available: false
DEBUG [org.flywaydb.core.internal.callback.SqlScriptFlywayCallback] Scanning for SQL callbacks ...
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classpath resources at 'classpath:db/migration' (Prefix: '', Suffix: '.sql')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Determining location urls for classpath:db/migration using ClassLoader sun.misc.Launcher$AppClassLoader@73d16e93 ...
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning URL: file:/Users/juanliska/Documents/startrack/test/tmp/db/migration
DEBUG [org.flywaydb.core.internal.util.FeatureDetector] JBoss VFS v2 available: false
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.FileSystemClassPathLocationScanner] Scanning starting at classpath root in filesystem: /Users/juanliska/Documents/startrack/test/tmp/
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.FileSystemClassPathLocationScanner] Scanning for resources in path: /Users/juanliska/Documents/startrack/test/tmp/db/migration (db/migration)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/R__New_perm_refpoint_groups.class (filename: R__New_perm_refpoint_groups.class)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Found resource: db/migration/R__Log_something.sql
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Found resource: db/migration/V1.11__Add_geofence_group_tables.sql
DEBUG [org.flywaydb.core.internal.command.DbValidate] Validating migrations ...
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classpath resources at 'classpath:db/migration' (Prefix: 'V', Suffix: '.sql')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning URL: file:/Users/juanliska/Documents/startrack/test/tmp/db/migration
DEBUG [org.flywaydb.core.internal.util.FeatureDetector] JBoss VFS v2 available: false
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/R__Log_something.sql (filename: R__Log_something.sql)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/R__New_perm_refpoint_groups.class (filename: R__New_perm_refpoint_groups.class)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Found resource: db/migration/V1.11__Add_geofence_group_tables.sql
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classpath resources at 'classpath:db/migration' (Prefix: 'R', Suffix: '.sql')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning URL: file:/Users/juanliska/Documents/startrack/test/tmp/db/migration
DEBUG [org.flywaydb.core.internal.util.FeatureDetector] JBoss VFS v2 available: false
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/R__New_perm_refpoint_groups.class (filename: R__New_perm_refpoint_groups.class)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/V1.11__Add_geofence_group_tables.sql (filename: V1.11__Add_geofence_group_tables.sql)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Found resource: db/migration/R__Log_something.sql
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning for classes at 'classpath:db/migration' (Implementing: 'org.flywaydb.core.api.migration.jdbc.JdbcMigration')
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Scanning URL: file:/Users/juanliska/Documents/startrack/test/tmp/db/migration
DEBUG [org.flywaydb.core.internal.util.FeatureDetector] JBoss VFS v2 available: false
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/R__Log_something.sql (filename: R__Log_something.sql)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Filtering out resource: db/migration/V1.11__Add_geofence_group_tables.sql (filename: V1.11__Add_geofence_group_tables.sql)
DEBUG [org.flywaydb.core.internal.util.scanner.classpath.ClassPathScanner] Found class: db.migration.R__New_perm_refpoint_groups
INFO [org.flywaydb.core.internal.command.DbValidate] Successfully validated 4 migrations (execution time 00:00.064s)
DEBUG [org.flywaydb.core.internal.command.DbSchemas] Schema "public" already exists. Skipping schema creation.
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Locking table "public"."schema_version"...
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Lock acquired for table "public"."schema_version"
INFO [org.flywaydb.core.internal.command.DbMigrate] Current version of schema "public": 1.9.30
INFO [org.flywaydb.core.internal.command.DbMigrate] Migrating schema "public" with repeatable migration Log something
DEBUG [org.flywaydb.core.internal.dbsupport.SqlScript] Found statement at line 1: INSERT into al_log (message) values ('Hello v1.9.30')
DEBUG [org.flywaydb.core.internal.dbsupport.SqlScript] Executing SQL: INSERT into al_log (message) values ('Hello v1.9.30')
DEBUG [org.flywaydb.core.internal.dbsupport.JdbcTemplate] Update Count: 1
DEBUG [org.flywaydb.core.internal.command.DbMigrate] Successfully completed migration of schema "public" with repeatable migration Log something
DEBUG [org.flywaydb.core.internal.metadatatable.MetaDataTableImpl] MetaData table "public"."schema_version" successfully updated to reflect changes
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Locking table "public"."schema_version"...
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Lock acquired for table "public"."schema_version"
INFO [org.flywaydb.core.internal.command.DbMigrate] Migrating schema "public" with repeatable migration New perm refpoint groups
...
DEBUG [org.flywaydb.core.internal.command.DbMigrate] Successfully completed migration of schema "public" with repeatable migration New perm refpoint groups
DEBUG [org.flywaydb.core.internal.metadatatable.MetaDataTableImpl] MetaData table "public"."schema_version" successfully updated to reflect changes
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Locking table "public"."schema_version"...
DEBUG [org.flywaydb.core.internal.dbsupport.Table] Lock acquired for table "public"."schema_version"
INFO [org.flywaydb.core.internal.command.DbMigrate] Successfully applied 2 migrations to schema "public" (execution time 00:00.176s).

The text was updated successfully, but these errors were encountered:

axelfontaine · 2016-03-29T22:10:50Z

Thanks for reporting. Please post a GitHub repo to reproduce this.

pabl0rg · 2016-04-09T18:11:22Z

Hi. You can find an example here https://github.com/pabl0rg/kobalt-mixed-example/

Steps:

produce jar
./kobaltw assemble
run from jar
java -cp :./kobaltBuild/libs/mixed-example-0.1.jar com.guatec.KExample
message will say validated 0 migrations.
unzip the jar into tmp folder, then run
java -cp :tmp com.guatec.KExample
message will say validated 2 migrations and will have run them

pabl0rg · 2016-04-27T12:54:30Z

Hello, has anyone been able to run the example project to reproduce the error?

In another project, i've used this library which does a good job of scanning inside jars.
https://github.com/lukehutch/fast-classpath-scanner

pabl0rg · 2016-06-30T01:34:21Z

Hello this is still marked as waiting for feedback but i provided the feedback and an example almost three months ago. Has anyone been able to check out the example?

thanks!

wagnerma · 2016-08-25T19:00:51Z

I observe a similar problem. I work on a java application with an in memory database. Flyway finds only the migration sql scripts in the filesystem or in the classpath of the application startet from eclipse. If the application is packaged into jars with the sql files included, flyway don't find them. As a workaround I copy the sql scripts from the jar to a temporary folder in the filesystem and all it fine. There seems a bug in the loading from the classpath from jar files. (I use version 4.0.3)

pabl0rg · 2016-08-25T19:04:50Z

Would you be interested in sharing the cost of sponsoring this fix?

sandokandias · 2016-10-14T14:32:16Z

Same problem here, only works by filesystem.
SO: OS X El Capitan and archlinux.
Versions: 4.0, 4.0.1, 4.0.2, 4.0.3
Database: Postgresql 9.5
Application: Spring Boot

pabl0rg · 2016-10-14T14:37:35Z

My company has sponsored a fix for this and the last snapshot we got is working. So, hold tight for the next release which will finally have this fixed.

EmilDafinov · 2016-12-12T18:49:25Z

@pabl0rg Just out of curiosity, what is the structure of your jar like? I just had a similar problem with a Spring Boot app, turned out to be because Spring Boot structures its fat jars in a non-standard way.

pabl0rg · 2016-12-12T20:39:01Z

The jar was a standard maven jar. The jar could have been modified to work with flyway but the flyway guys actually found there was a slight issue in how they were searching the classpath. They haven't released a new flyway due to lack of time, but they have this fixed in git.

axelfontaine · 2017-01-31T13:44:52Z

@pabl0rg Thanks again for sponsoring. Fixed.

tasosz · 2017-05-25T10:08:03Z

Hi,
Has this fix been applied to any releases?

Thanks

derabbink · 2017-05-25T19:35:04Z

I'm intermittently seeing - what looks to be - this issue with org.flywaydb:flyway-gradle-plugin:4.2.0.

teixeluis · 2020-06-22T10:01:49Z

Hi, have this issue been actually fixed? In what release in that case?

urbaez22 · 2020-09-22T21:07:12Z

It seems like they haven't fixed the issue. I'm recently using Flyway v6.5.7 and is still happening, Flyway can't find the migrations inside the Spring Boot JAR.. Maybe it doesn't recognize the way Maven packs Spring Boot binary, mine are located in the route path BOOT-INF/classes/db/migration inside the JAR..
The key question is, why they closed the issue if it's not resolved..?

teixeluis · 2020-09-22T21:11:24Z

Cheers @pabl0rg what is your take on this?

Best regards

urbaez22 · 2020-09-22T21:32:32Z

Well, finally I found a workaround..

I simply put:
flyway.locations=classpath:BOOT-INF/classes/db/migration

And Flyway was able to find and execute the migrations.

Hope this can help somebody else..

Cheers..

neelam-007 · 2021-01-04T21:52:29Z

In my case, the migration scripts are within another jar file within the main jar file. How can I set the location in such a case?

axelfontaine added the s: waiting for feedback label Mar 29, 2016

axelfontaine added t: bug and removed s: waiting for feedback labels Jan 31, 2017

axelfontaine added this to the Flyway 4.1 milestone Jan 31, 2017

axelfontaine closed this as completed Jan 31, 2017

axelfontaine pushed a commit to flyway/flywaydb.org that referenced this issue Jan 31, 2017

Added notes for flyway/flyway#1261

60a9848

sreekanthsnair mentioned this issue Apr 27, 2017

Migration scripts are sometimes skipped during concurrent Flyway runs across multiple schemas #1616

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

classpath scanner does not find db.migration package or resources #1261

classpath scanner does not find db.migration package or resources #1261

pabl0rg commented Mar 29, 2016

axelfontaine commented Mar 29, 2016

pabl0rg commented Apr 9, 2016

pabl0rg commented Apr 27, 2016

pabl0rg commented Jun 30, 2016 •

edited

Loading

wagnerma commented Aug 25, 2016

pabl0rg commented Aug 25, 2016

sandokandias commented Oct 14, 2016

pabl0rg commented Oct 14, 2016

EmilDafinov commented Dec 12, 2016

pabl0rg commented Dec 12, 2016

axelfontaine commented Jan 31, 2017

tasosz commented May 25, 2017

derabbink commented May 25, 2017

teixeluis commented Jun 22, 2020

urbaez22 commented Sep 22, 2020

teixeluis commented Sep 22, 2020

urbaez22 commented Sep 22, 2020

neelam-007 commented Jan 4, 2021

classpath scanner does not find db.migration package or resources #1261

classpath scanner does not find db.migration package or resources #1261

Comments

pabl0rg commented Mar 29, 2016

What version of Flyway are you using?

What operating system are you using?

What did you do?

axelfontaine commented Mar 29, 2016

pabl0rg commented Apr 9, 2016

pabl0rg commented Apr 27, 2016

pabl0rg commented Jun 30, 2016 • edited Loading

wagnerma commented Aug 25, 2016

pabl0rg commented Aug 25, 2016

sandokandias commented Oct 14, 2016

pabl0rg commented Oct 14, 2016

EmilDafinov commented Dec 12, 2016

pabl0rg commented Dec 12, 2016

axelfontaine commented Jan 31, 2017

tasosz commented May 25, 2017

derabbink commented May 25, 2017

teixeluis commented Jun 22, 2020

urbaez22 commented Sep 22, 2020

teixeluis commented Sep 22, 2020

urbaez22 commented Sep 22, 2020

neelam-007 commented Jan 4, 2021

pabl0rg commented Jun 30, 2016 •

edited

Loading