Loop dependency in SBT with span, jooq and compilation

This is the problem I have. Flyway applies the schema to the database, and jOOq generates code from that schema. Compilation compiles the code. This is how it looks:

Flyway runs -> jooq runs -> compilation

      

        
        
        
      

    

The problem is that flyway

for some reason depends on runtime:fullClasspath

, which in turn depends on compile:compile

. I understand it flyway

depends on compile

for any Java porting, but we don't have a Java migration. Is there a way to flyway

only depend on runtime:dependencyClasspath

and not on fullClasspath

, so that I can determine that

(codegen in jOOQ) dependsOn flywayMigrate
compile dependsOn (codegen in jOOQ)

      

        
        
        
      

    

For some projects we faced similar issues with gradle plugin and it was resolved with Flyway gradle plugin - circular dependency

I don't know what to do with sbt

.