Issue when using jOOQ generator with Liquibase script which refers to changeset files using classpath: prefix #16333

marinusgeuze · 2024-02-23T11:01:01Z

marinusgeuze
Feb 23, 2024

Hi,

We want to use the JOOQ generator in combination with our Liquibase scripts. We bumped into an issue that we get this error:

java.nio.file.InvalidPathException: Illegal char <:> at index 9: classpath:db\changelog\changeset\2023-08-24#001_create_xxx_table.xml

This is how our changelog.yaml file looks like:

databaseChangeLog:
  - include:
      file: classpath:db/changelog/changeset/2023-08-24#001_create_xxx_table.xml

We use this classpath: prefix so that our Spring Boot application can load the changeset files.

We use maven. See below our configuration of the generator.

How can we solve this issue?

Thanks in advance for your help.


<plugin>
  <groupId>org.jooq</groupId>
  <artifactId>jooq-codegen-maven</artifactId>
  <version>${jooq.version}</version>
  <configuration>
    <generator>
      <database>
        <name>org.jooq.meta.extensions.liquibase.LiquibaseDatabase</name>
        <properties>
          <property>
            <key>rootPath</key>
            <value>${basedir}/src/main/resources</value>
          </property>
          <property>
            <key>scripts</key>
            <value>db/changelog/changelog.yaml</value>
          </property>
        </properties>
      </database>
    </generator>
  </configuration>
  <executions>
    <execution>
      <id>jooq-codegen</id>
      <goals>
        <goal>generate</goal>
      </goals>
      <phase>generate-sources</phase>
    </execution>
  </executions>
</plugin>

Answered by lukaseder

Mar 4, 2024

I created this bug for your case:

#16402

View full answer

lukaseder · 2024-02-23T12:37:50Z

lukaseder
Feb 23, 2024
Maintainer

Thanks for your message. Can you provide the complete stack trace, please?

0 replies

marinusgeuze · 2024-02-29T10:24:30Z

marinusgeuze
Feb 29, 2024
Author

Dear Lukas,

When I run: mvn clean package -DskipTests

I get:

[INFO]
[INFO] --- jooq-codegen:3.19.4:generate (jooq-codegen) @ ros-tax ---
[INFO] 

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@  @@        @@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@        @@@@@@@@@@
@@@@@@@@@@@@@@@@  @@  @@    @@@@@@@@@@
@@@@@@@@@@  @@@@  @@  @@    @@@@@@@@@@
@@@@@@@@@@        @@        @@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@        @@        @@@@@@@@@@
@@@@@@@@@@    @@  @@  @@@@  @@@@@@@@@@
@@@@@@@@@@    @@  @@  @@@@  @@@@@@@@@@
@@@@@@@@@@        @@  @  @  @@@@@@@@@@
@@@@@@@@@@        @@        @@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@  @@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@  Thank you for using jOOQ 3.19.4 (Build date: 2024-02-20T08:54:34Z)

[INFO]

jOOQ tip of the day: Multi tenancy is best implemented in jOOQ using runtime schema and table mapping: https://www.jooq.org/doc/latest/manual/sql-building/dsl-context/custom-settings
/settings-render-mapping/

[INFO] No <inputCatalog/> was provided. Generating ALL available catalogs instead.
feb. 29, 2024 11:23:08 A.M. liquibase.database
INFO: Set default schema name to PUBLIC
feb. 29, 2024 11:23:09 A.M. liquibase.resource
WARNING: Failed to standardize path classpath:db/changelog/changeset/2023-08-24#001_create_xxx_table.xml
java.nio.file.InvalidPathException: Illegal char <:> at index 9: classpath:db\changelog\changeset\2023-08-24#001_create_xxx_table.xml
        at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
        at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
        at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
        at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92)
        at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:232)
        at java.base/java.io.File.toPath(File.java:2387)
        at liquibase.resource.AbstractPathResourceAccessor.standardizePath(AbstractPathResourceAccessor.java:56)
        at liquibase.resource.AbstractPathResourceAccessor.getAll(AbstractPathResourceAccessor.java:34)
        at liquibase.resource.ResourceAccessor.get(ResourceAccessor.java:234)
        at liquibase.changelog.DatabaseChangeLog.include(DatabaseChangeLog.java:941)
        at liquibase.changelog.DatabaseChangeLog.handleChildNode(DatabaseChangeLog.java:455)
        at liquibase.changelog.DatabaseChangeLog.load(DatabaseChangeLog.java:390)
        at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:88)
        at liquibase.command.core.helpers.DatabaseChangelogCommandStep.lambda$getDatabaseChangeLog$0(DatabaseChangelogCommandStep.java:129)
        at liquibase.Scope.child(Scope.java:195)
        at liquibase.Scope.child(Scope.java:171)
        at liquibase.command.core.helpers.DatabaseChangelogCommandStep.getDatabaseChangeLog(DatabaseChangelogCommandStep.java:128)
        at liquibase.command.core.helpers.DatabaseChangelogCommandStep.run(DatabaseChangelogCommandStep.java:87)
        at liquibase.command.CommandScope.execute(CommandScope.java:217)
        at liquibase.Liquibase.lambda$update$0(Liquibase.java:245)
        at liquibase.Scope.lambda$child$0(Scope.java:186)
        at liquibase.Scope.child(Scope.java:195)
        at liquibase.Scope.child(Scope.java:185)
        at liquibase.Scope.child(Scope.java:164)
        at liquibase.Liquibase.runInScope(Liquibase.java:1419)
        at liquibase.Liquibase.update(Liquibase.java:234)
        at liquibase.Liquibase.update(Liquibase.java:212)
        at liquibase.Liquibase.update(Liquibase.java:194)
        at liquibase.Liquibase.update(Liquibase.java:179)
        at org.jooq.meta.extensions.liquibase.LiquibaseDatabase.export(LiquibaseDatabase.java:164)
        at org.jooq.meta.extensions.AbstractInterpretingDatabase.connection(AbstractInterpretingDatabase.java:100)
        at org.jooq.meta.extensions.AbstractInterpretingDatabase.create0(AbstractInterpretingDatabase.java:77)
        at org.jooq.meta.AbstractDatabase.create(AbstractDatabase.java:408)
        at org.jooq.meta.AbstractDatabase.create(AbstractDatabase.java:398)
        at org.jooq.meta.AbstractDatabase.setConnection(AbstractDatabase.java:376)
        at org.jooq.codegen.GenerationTool.run0(GenerationTool.java:566)
        at org.jooq.codegen.GenerationTool.run(GenerationTool.java:246)
        at org.jooq.codegen.GenerationTool.generate(GenerationTool.java:241)
        at org.jooq.codegen.maven.Plugin.execute(Plugin.java:216)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:126)
        at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:342)
        at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:330)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:175)
        at org.apache.maven.lifecycle.internal.MojoExecutor.access$000(MojoExecutor.java:76)
        at org.apache.maven.lifecycle.internal.MojoExecutor$1.run(MojoExecutor.java:163)
        at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute(DefaultMojosExecutionStrategy.java:39)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:160)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:105)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:73)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:53)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:118)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:260)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:172)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:100)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:821)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:270)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

feb. 29, 2024 11:23:09 A.M. liquibase.command
INFO: Logging exception.
ERROR: Exception Details
ERROR: Exception Primary Class:  InvalidPathException
ERROR: Exception Primary Reason: Illegal char <:> at index 9: classpath:db/changelog/changeset/2023-08-24#001_create_xxx_table.xml
ERROR: Exception Primary Source: H2 2.2.224 (2023-09-17)
feb. 29, 2024 11:23:09 A.M. liquibase.command

2 replies

lukaseder Mar 4, 2024
Maintainer

I see now. The decision of whether we use a ClassLoaderResourceAccessor or a DirectoryResourceAccessor is made based on whether there is a rootPath configuration, see also:

It should probably be possible to mix the 2 styles, but perhaps this information helps to work around the problem on your end? Do you really need the rootPath property?

marinusgeuze Mar 5, 2024
Author

Hi,

I really need the rootPath property because otherwise maven does not find the db.changelog-master.yaml file.

ERROR: Exception Primary Reason: /src/main/resources/db/changelog/db.changelog-master.yaml does not exist

Thanks for creating the bug.

lukaseder · 2024-03-04T10:31:02Z

lukaseder
Mar 4, 2024
Maintainer

I created this bug for your case:

LiquibaseDatabase should support classpath: prefixed inclusions even with rootPath being specified #16402

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Issue when using jOOQ generator with Liquibase script which refers to changeset files using classpath: prefix #16333

{{title}}

Replies: 3 comments 2 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Issue when using jOOQ generator with Liquibase script which refers to changeset files using classpath: prefix #16333

marinusgeuze Feb 23, 2024

Replies: 3 comments · 2 replies

lukaseder Feb 23, 2024 Maintainer

marinusgeuze Feb 29, 2024 Author

lukaseder Mar 4, 2024 Maintainer

marinusgeuze Mar 5, 2024 Author

lukaseder Mar 4, 2024 Maintainer

marinusgeuze
Feb 23, 2024

Replies: 3 comments 2 replies

lukaseder
Feb 23, 2024
Maintainer

marinusgeuze
Feb 29, 2024
Author

lukaseder Mar 4, 2024
Maintainer

marinusgeuze Mar 5, 2024
Author

lukaseder
Mar 4, 2024
Maintainer