[jira] [Commented] (VFS-761) Dynamically Load File Systems From Classpath

[David Mollitor (Jira)]

[ 
https://issues.apache.org/jira/browse/VFS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041361#comment-17041361
 ] 

David Mollitor commented on VFS-761:


[~b.eckenfels] Having worked with HDFS quite a bit, I know the dependencies 
there can be very heavy.  That should probably become its own project.

I took a look at how SLF4J does it and they use the JDK {{ServiceLoader}}.  
Seems like it could be applied here.

https://docs.oracle.com/javase/9/docs/api/java/util/ServiceLoader.html

> Dynamically Load File Systems From Classpath
> 
>
> Key: VFS-761
> URL: https://issues.apache.org/jira/browse/VFS-761
> Project: Commons VFS
>  Issue Type: Wish
>Reporter: David Mollitor
>Priority: Minor
>
> I would like to see each File System separated into its own project.
> To setup my project, I would like to import a single VFS Binder project which 
> will then load all File Systems that are included on the class path.  
> Thereby, I can include only the File Systems I want by including them in the 
> Maven POM as dependencies and not have to include the code for every single 
> File System.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (VFS-761) Dynamically Load File Systems From Classpath

[Bernd Eckenfels (Jira)]

[ 
https://issues.apache.org/jira/browse/VFS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041324#comment-17041324
 ] 

Bernd Eckenfels commented on VFS-761:
-

We do that for new provides if they have specific dependencies, but I don't 
think it's worth the effort for the existing providers. You normally don't 
interact with the provided directly, and if you use a custom FileSystemManager 
you can decide for yourself which schemes are loaded. It is also no problem to 
not provide dependencies for the providers you don't need (you could even skip 
the packages when you want to minimize the footprint, but those few bytes saved 
are certainly not worth the maintenance overhead.

If anybody wants to do that I strongly recommend to discuss it on commons-dev 
first. I veto all changes which just duplicates the test suite (as it currently 
is not good for that modularisation).

> Dynamically Load File Systems From Classpath
> 
>
> Key: VFS-761
> URL: https://issues.apache.org/jira/browse/VFS-761
> Project: Commons VFS
>  Issue Type: Wish
>Reporter: David Mollitor
>Priority: Minor
>
> I would like to see each File System separated into its own project.
> To setup my project, I would like to import a single VFS Binder project which 
> will then load all File Systems that are included on the class path.  
> Thereby, I can include only the File Systems I want by including them in the 
> Maven POM as dependencies and not have to include the code for every single 
> File System.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)