Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java.nio.file.FileSystemNotFoundException #252

Closed
Aquazus opened this issue Nov 25, 2018 · 11 comments
Closed

java.nio.file.FileSystemNotFoundException #252

Aquazus opened this issue Nov 25, 2018 · 11 comments

Comments

@Aquazus
Copy link

Aquazus commented Nov 25, 2018

Hello, here's the code for my project :
https://github.com/Aquazus/D1Proxy

With the exact same program, exact same jar plugin, using 2.3.0 everything works perfectly, but if you change the version to 2.4.0 I get this error :

09:15:18 ERROR o.p.CompoundPluginDescriptorFinder - /plugins/exampleplugin-1.0.0-plugin.jar
java.nio.file.FileSystemNotFoundException: /plugins/exampleplugin-1.0.0-plugin.jar
	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.<init>(ZipFileSystem.java:104)
	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.newFileSystem(ZipFileSystemProvider.java:106)
	at java.base/java.nio.file.FileSystems.newFileSystem(FileSystems.java:344)
	at java.base/java.nio.file.FileSystems.newFileSystem(FileSystems.java:293)
	at org.pf4j.util.FileUtils.getFileSystem(FileUtils.java:259)
	at org.pf4j.util.FileUtils.getPath(FileUtils.java:232)
	at org.pf4j.util.FileUtils.getPath(FileUtils.java:228)
	at org.pf4j.PropertiesPluginDescriptorFinder.getPropertiesPath(PropertiesPluginDescriptorFinder.java:90)
	at org.pf4j.PropertiesPluginDescriptorFinder.readProperties(PropertiesPluginDescriptorFinder.java:64)
	at org.pf4j.PropertiesPluginDescriptorFinder.find(PropertiesPluginDescriptorFinder.java:58)
	at org.pf4j.CompoundPluginDescriptorFinder.find(CompoundPluginDescriptorFinder.java:65)
	at org.pf4j.AbstractPluginManager.loadPluginFromPath(AbstractPluginManager.java:826)
	at org.pf4j.DefaultPluginManager.loadPluginFromPath(DefaultPluginManager.java:141)
	at org.pf4j.AbstractPluginManager.loadPlugins(AbstractPluginManager.java:222)
	at fr.aquazus.d1proxy.plugins.ProxyPluginManager.loadPlugins(ProxyPluginManager.java:30)
	at fr.aquazus.d1proxy.Proxy.init(Proxy.java:73)
	at fr.aquazus.d1proxy.Proxy.main(Proxy.java:28)

My computer is running Linux Mint 19 tara and OpenJDK "11.0.1" 2018-10-16

@Aquazus
Copy link
Author

Aquazus commented Nov 25, 2018

Seems like it's related to this answer : #251 (comment)

@Aquazus
Copy link
Author

Aquazus commented Nov 25, 2018

Got a workaround as I'm only using jar files as plugins, but this error may happen if you are using a plugin.properties file... Aquazus/D1Proxy@520d436

@decebals
Copy link
Member

I will take a look and I will come with a solution asap.

@decebals
Copy link
Member

@Aquazus
I released a new SNAPSHOT version that contains this fix. Can you try it and give me a feedback?

@Aquazus
Copy link
Author

Aquazus commented Nov 25, 2018

@Aquazus
I released a new SNAPSHOT version that contains this fix. Can you try it and give me a feedback?

Work like a charm now!

@decebals
Copy link
Member

@Aquazus
Thanks! I will release a new version in few days.

@decebals
Copy link
Member

@Aquazus

My computer is running Linux Mint 19 tara and OpenJDK "11.0.1" 2018-10-16

Some people (see #251) ask if PF4J supports OpenJDK 11? Can you confirm or infirm that PF4J works with OpenJDK 11?

@Aquazus
Copy link
Author

Aquazus commented Nov 26, 2018

@Aquazus

My computer is running Linux Mint 19 tara and OpenJDK "11.0.1" 2018-10-16

Some people (see #251) ask if PF4J supports OpenJDK 11? Can you confirm or infirm that PF4J works with OpenJDK 11?

PF4J works perfectly with OpenJDK 11.

@ramafasa
Copy link

ramafasa commented Dec 6, 2018

@decebals, Finally the issue was on my side. I used old version of PF4J. Of course I managed to upgrade it after moving to Java 11, however I didn't notice new groupId - "org.pf4j". After upgrading to the 2.4.0 it works perfectly with Java 11.

Thanks!

@decebals
Copy link
Member

decebals commented Dec 6, 2018

@ramafasa
Perfect.

So, we can close the issue?

@ramafasa
Copy link

ramafasa commented Dec 7, 2018

@decebals,

Yes, it's ok for me :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants