Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[WARNING] Cannot create filesystem for url target/test-classes

See original GitHub issue

liquibase: 4.1.1 -> Affected. liquibase: 3.10.3 -> Not affected.

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: C:\Maven\bin.. Java version: 11.0.8, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-11.0.8 OS name: “windows 10”, version: “10.0”, arch: “amd64”, family: “windows”

pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>com.test.liquibase</groupId>
	<artifactId>liquibase-test</artifactId>
	<version>1.0</version>

	<packaging>jar</packaging>

	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<version.compiler.plugin>3.8.1</version.compiler.plugin>
		<maven.compiler.target>1.8</maven.compiler.target>
		<maven.compiler.source>1.8</maven.compiler.source>
		<ci.headless>true</ci.headless>
		<liquibase.version>4.1.1</liquibase.version>
		<liquibase.propertyFile>target/classes/liquibase.properties</liquibase.propertyFile>
		<mssql.jdbc.version>7.4.1.jre8</mssql.jdbc.version>
	</properties>

	<build>
		<plugins>

			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>${version.compiler.plugin}</version>
				<configuration>
					<source>${maven.compiler.source}</source>
					<target>${maven.compiler.target}</target>
				</configuration>
			</plugin>

			<plugin>
				<groupId>org.liquibase</groupId>
				<artifactId>liquibase-maven-plugin</artifactId>
				<version>${liquibase.version}</version>
				<executions>
					<execution>
						<goals>
							<goal>update</goal>
						</goals>
						<configuration>
							<propertyFile>${liquibase.propertyFile}</propertyFile>
							<promptOnNonLocalDatabase>${ci.headless}</promptOnNonLocalDatabase>
						</configuration>
					</execution>
				</executions>
			</plugin>

		</plugins>
	</build>
	<profiles>
		<profile>
			<id>DEV</id>
			<build>
				<filters>
					<filter>src/main/filters/DEV/db.properties</filter>
				</filters>
				<resources>
					<resource>
						<directory>src/main/resources</directory>
						<filtering>true</filtering>
					</resource>
				</resources>
			</build>
		</profile>
	</profiles>
	<dependencies>
		<dependency>
			<groupId>com.microsoft.sqlserver</groupId>
			<artifactId>mssql-jdbc</artifactId>
			<version>${mssql.jdbc.version}</version>
		</dependency>
	</dependencies>
</project>

$ mvn liquibase:update -P DEV -X

...
[INFO] ------------------------------------------------------------------------
[DEBUG] Adding path C:\Users\Dell\Documents\workspace\liquibase to resourceAccessor liquibase.resource.FileSystemResourceAccessor
[project, pluginDescriptor]
[INFO] Parsing Liquibase Properties File
[INFO]   File: target/classes/liquibase.properties
[WARNING] Cannot create filesystem for url file:/C:/Users/Dell/Documents/workspace/liquibase/target/test-classes: C:\Users\Dell\Documents\workspace\repo-colombia\liquibase-cm\target\test-classes
java.nio.file.FileSystemNotFoundException: C:\Users\Dell\Documents\workspace\liquibase\target\test-classes
    at jdk.nio.zipfs.ZipFileSystem.<init> (ZipFileSystem.java:104)
    at jdk.nio.zipfs.ZipFileSystemProvider.newFileSystem (ZipFileSystemProvider.java:136)
    at java.nio.file.FileSystems.newFileSystem (FileSystems.java:406)
    at liquibase.resource.ClassLoaderResourceAccessor.loadRootPaths (ClassLoaderResourceAccessor.java:63)
    at liquibase.resource.ClassLoaderResourceAccessor.loadRootPaths (ClassLoaderResourceAccessor.java:79)
    at liquibase.resource.ClassLoaderResourceAccessor.init (ClassLoaderResourceAccessor.java:47)
    at liquibase.resource.ClassLoaderResourceAccessor.openStreams (ClassLoaderResourceAccessor.java:94)
    at org.liquibase.maven.plugins.MavenResourceAccessor.openStreams (MavenResourceAccessor.java:21)
    at liquibase.resource.CompositeResourceAccessor.openStreams (CompositeResourceAccessor.java:33)
    at liquibase.resource.AbstractResourceAccessor.openStream (AbstractResourceAccessor.java:17)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.handlePropertyFileInputStream (AbstractLiquibaseMojo.java:560)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.configureFieldsAndValues (AbstractLiquibaseMojo.java:530)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$null$0 (AbstractLiquibaseMojo.java:374)
    at liquibase.Scope.lambda$child$0 (Scope.java:160)
    at liquibase.Scope.child (Scope.java:169)
    at liquibase.Scope.child (Scope.java:159)
    at liquibase.Scope.child (Scope.java:138)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$execute$1 (AbstractLiquibaseMojo.java:372)
    at liquibase.Scope.lambda$child$0 (Scope.java:160)
    at liquibase.Scope.child (Scope.java:169)
    at liquibase.Scope.child (Scope.java:159)
    at liquibase.Scope.child (Scope.java:138)
    at liquibase.Scope.child (Scope.java:222)
    at liquibase.Scope.child (Scope.java:226)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute (AbstractLiquibaseMojo.java:306)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    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)

...

[INFO] Executing on Database: jdbc:sqlserver://localhost;databaseName=local
[DEBUG] Class [org.hibernate.boot.jaxb.hbm.spi.package-info] could not be found. Processing hibernate bindings will probably fail if applicable.
java.lang.ClassNotFoundException: org.hibernate.boot.jaxb.hbm.spi.package-info
    at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass (SelfFirstStrategy.java:50)
    at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass (ClassRealm.java:271)
    at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass (ClassRealm.java:247)
    at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass (ClassRealm.java:239)
    at java.lang.Class.forName0 (Native Method)
    at java.lang.Class.forName (Class.java:315)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.setupBindInfoPackage (AbstractLiquibaseMojo.java:484)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$null$0 (AbstractLiquibaseMojo.java:445)
    at liquibase.Scope.lambda$child$0 (Scope.java:160)
    at liquibase.Scope.child (Scope.java:169)
    at liquibase.Scope.child (Scope.java:159)
    at liquibase.Scope.child (Scope.java:138)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$execute$1 (AbstractLiquibaseMojo.java:372)
    at liquibase.Scope.lambda$child$0 (Scope.java:160)
    at liquibase.Scope.child (Scope.java:169)
    at liquibase.Scope.child (Scope.java:159)
    at liquibase.Scope.child (Scope.java:138)
    at liquibase.Scope.child (Scope.java:222)
    at liquibase.Scope.child (Scope.java:226)
    at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute (AbstractLiquibaseMojo.java:306)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    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)

...

[INFO] Successfully released change log lock
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.572 s
[INFO] Finished at: 2020-10-17T19:43:40-03:00
[INFO] ------------------------------------------------------------------------

Test Requirements

  • No automated test required for this ticket.
  • Verify you can reproduce the bug in 4.3.2 using Maven.
  • Verify the fix no longer outputs a warning that the test-classes directory is not found.

┆Issue is synchronized with this Jira Bug by Unito ┆Fix Versions: Community 4.x

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:15 (4 by maintainers)

github_iconTop GitHub Comments

3reactions
molivasdatcommented, Oct 23, 2020

Hi @dertin Thanks for creating this issue. We will add it to our list of issues to resolve in v4.x

2reactions
cvetancommented, Feb 19, 2021

The issue is still present in latest liquibase.

About the thing mentioned here, to avoid warning:

to avoid the warning create an empty test:

/src/test/java

package notest;

public class AppTest 
{
}

I tried this, but it doesn’t work. Perhaps I did not understand correctly. Do you mean literally create file with this content on path /src/test/java? I mean I tried that also, doesn’t work. Tried adding empty test class, on my application package doesn’t work.

Read more comments on GitHub >

github_iconTop Results From Across the Web

java - Getting WARNING [liquibase.resource] Cannot create ...
While checking liquibase code base I realise that there is a bug in liquibase. I have raised the issue here is the link ......
Read more >
[WARNING] Cannot create filesystem for url target/test-classes
[WARNING] Cannot create filesystem for url target/test-classes.
Read more >
Migrate 1.9.5 to 4.1.1 - General Discussion - Liquibase Forum
Is it the way to migrate to 4.1.1? [WARNING] Cannot create filesystem for url file:/C:/projects/workspace/myproject/target/classes: C:\projects\ ...
Read more >
Log4j User Guide (PDF) - Apache Logging Services
objects are created from Logger declarations in the configuration. ... to a location on the local file system and may contain a. URL....
Read more >
JRebel Changelog | JRebel & XRebel by Perforce
Bug fix: fixed an integration issue with Vaadin where methods annotated with @EventData could not reload correctly. JRebel for IntelliJ IDEA. Feature: added ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

Custom SQL executed not showing up in 4.x versions of Liquibase with the INFO verbosity level

Next page

Error handling long Postgres table names