Devskiller / jpa2ddl

JPA Schema Generator Plugin
Apache License 2.0
110 stars 33 forks source link

FileSystemNotFoundException on Jenkins with parallel processing #26

Closed eXsio closed 5 years ago

eXsio commented 5 years ago

Hello

I am experiencing the following exception when trying to perform a build on Jenkins, using parallel processing.

Caused by: java.nio.file.FileSystemNotFoundException
    at com.sun.nio.zipfs.ZipFileSystemProvider.getFileSystem (ZipFileSystemProvider.java:171)
    at com.sun.nio.zipfs.ZipFileSystemProvider.getPath (ZipFileSystemProvider.java:157)
    at java.nio.file.Paths.get (Paths.java:143)
    at com.devskiller.jpa2ddl.FileResolver.listClassNamesInPackage (FileResolver.java:79)
    at com.devskiller.jpa2ddl.SchemaGenerator.generate (SchemaGenerator.java:66)
    at com.devskiller.jpa2ddl.GenerateMojo.execute (GenerateMojo.java:115)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:200)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
jkubrynski commented 5 years ago

Hi,

thanks for the report. It looks like the classpath is being parsed while it's changing. However, I'm not sure why the parsing is done during the test phase. Could you provide me with more details regarding the command you use to launch Maven?

jkubrynski commented 5 years ago

Closing. Please feel free to reopen with more details needed for analysis