Name = C:\Users\nms.tester\AppData\Roaming\gauge\plugins\java\0.3.4\libs\hamcrest-core-1.3.jar,Īt $1.nextElement(ZipFile.java:503)Īt $1.nextElement(ZipFile.java:481)Īt $1.nextElement(JarFile.java:242)Īt $1.nextElement(JarFile.java:237)Īt $1$1.computeNext(ZipDir.java:31)Īt $1$1.computeNext(ZipDir.java:26)Īt .yToComputeNext(AbstractIterator.java:143)Īt .AbstractIterator.hasNext(AbstractIterator.java:138)Īt (Reflections.java:240)Īt .main(GaugeRuntime. TopicNewVirtualFileSystem changes, offenderclass .newvfs.AsyncEventSupport1, messageafter, time208ms 13:57:59,232 252698 INFO - Generating new Device ID 13:57:59,234 252700 INFO - eventLog. Answer (1 of 2): Assuming you do not have access to the real sources of that existing JAR file: IntelliJ contains a decent Java decompiler, so it is possible to somewhat reconstruct the sources of that JAR file. : could not create Vfs.Dir from url, no matching UrlType was found Įither use fromURL(final URL url, final List urlTypes) or use the static setDefaultURLTypes(final List urlTypes) or addDefaultURLTypes(UrlType urlType) with your specialized UrlType.Īt .fromURL(Vfs.java:109)Įxception in thread "main" : jzentry = 0, In Eclipse I was able to just do export, runnable jar, and it seemed to work perfectly fine, but I very much prefer IntelliJ, and the create artifacts thing has been a nightmare. 14:06:43,248 INFO ServerInfo Java version: 1.7.003,Oracle Corporation 14:06:43,248 INFO ServerInfo Java VM: Java HotSpot(TM) 64-Bit Server VM 22. So, I am very frustrated right now because for multiple days I have been trying over and over to create a jar that can be run just by double clicking on it. skipping.Īt $DefaultUrlTypes$3.matches(Vfs.java:239)Īt .fromURL(Vfs.java:98)ģ9 WARN - could not create Vfs.Dir from url. 14:06:42,248 INFO ZipEntr圜ontext VFS force nested jars copy-mode is enabled. To all those having problems, I finally figured out why IntelliJ can fail at making a working executable jar: In my case, it was because IntelliJ was extracting all my dependencies into the output jar (good), which ended up overwritting the /META-INF/MANIFEST.MF file with something from one of my dependencies (bad).
![what is vfs intellij jar what is vfs intellij jar](https://aws1.discourse-cdn.com/business5/uploads/kotlinlang/original/2X/d/d1b086e906e5e424725bacac1c52e950ade4bc4d.png)
skipping.Īt .ClasspathScanner$1.createDir(ClasspathScanner.java:53)Īt .fromURL(Vfs.java:99)Īt .fromURL(Vfs.java:91)Īt (Reflections.java:237)Īt (Reflections.java:204)Īt .(Reflections.java:129)Īt .ClasspathScanner.createReflections(ClasspathScanner.java:60)Īt .ClasspathScanner.scan(ClasspathScanner.java:37)Īt .main(GaugeRuntime.java:36)ģ9 WARN - could not create Dir using directory from url file:/C:/Users/nms.tester/AppData/Roaming/gauge/plugins/java/0.3.4/*. WARN - could not create Dir using from url file:/C:/Users/nms.tester/AppData/Roaming/gauge/plugins/java/0.3.4/*.