Hi Nathan
sorry for the late response. We upgrade Liquibase to 3.3.5 but the issue still occurs when deploy in JBoss.
Looks like Liquibase still fails if refering jar file using vfs in the classpath,
10:11:15,997 ERROR [stderr] (MSC service thread 1-8) WARNING 10/16/15 10:11 AM: liquibase: Cannot search jar file 'vfs :/C:/Windows/System32/content/MyApp.Test.With.Liquibase.with.jboss..war/WEB-INF/lib/liquibase-osgi-3.3.5.jar' for classes due to an IOException: vfs:\C:\Windows\System32\content\MyApp.Test.With.Liquibase.with.jboss..war\WEB-INF\lib\liquibase-osgi-3.3.5.jar (The filename, directory name, or volume label syntax is incorrect)
10:11:15,998 ERROR [stderr] (MSC service thread 1-8) java.io.FileNotFoundException : vfs:\C:\Windows\System32\content\MyApp.Test.With.Liquibase.with.jboss..war\WEB-INF\lib\liquibase-osgi-3.3.5.jar (The filename, directory name, or volume label syntax is incorrect)
sorry for the late response. We upgrade Liquibase to 3.3.5 but the issue still occurs when deploy in JBoss.
Looks like Liquibase still fails if refering jar file using vfs in the classpath,
10:11:15,997 ERROR [stderr] (MSC service thread 1-8) WARNING 10/16/15 10:11 AM: liquibase: Cannot search jar file 'vfs :/C:/Windows/System32/content/MyApp.Test.With.Liquibase.with.jboss..war/WEB-INF/lib/liquibase-osgi-3.3.5.jar' for classes due to an IOException: vfs:\C:\Windows\System32\content\MyApp.Test.With.Liquibase.with.jboss..war\WEB-INF\lib\liquibase-osgi-3.3.5.jar (The filename, directory name, or volume label syntax is incorrect)
10:11:15,998 ERROR [stderr] (MSC service thread 1-8) java.io.FileNotFoundException : vfs:\C:\Windows\System32\content\MyApp.Test.With.Liquibase.with.jboss..war\WEB-INF\lib\liquibase-osgi-3.3.5.jar (The filename, directory name, or volume label syntax is incorrect)