I'm trying to migrate to commons-vfs2 now severial things I found not quite right / amazing.
1. I tested version 2.6.0 and 2.5.0, and I just start at VSF.getManager() (of cause I have no additional contfigure or something) It said class not found:org.apache.commons.vfs2.provider.webdav.WebdavFileProvider And I looked into your binary jars I get from maven central (2.6.0). they really do not have that class WebdavFileProvider. (even not found that package org.apache.commons.vfs2.provider.webdav) And after I downgrade to 2.3 (I really wonder why 2.3 not 2.3.0 but that is not important) It can run now.(and never tell me class not found again) I dont't want to try 2.4.0. Really bad connection here(I'm in a villige now). All I get is: 2.6.0, broken. 2.5.0, broken. 2.3, fine. According to the file on github, it said it might be deprecated, so I wonder if you already deprecate d it and you just forgotten it? btw, according to your webpage https://commons.apache.org/proper/commons-vfs/ there even do not exist 2.6.0 But there be a 2.6.0 in maven central. really make me confused. 2. for using commons-vfs2 I downgrade slf4j from 2.0.0alpha to 1.7.30 We all know slf4j's author really do not care about backward maintenance or something. His codes are never able to migrate. even though, will there be some plan about using reflect or something to make vfs2 CAN suit slf4j 2.0? 3. for some reason I need to deal with relative file path. Is there any guide about using relative file path in vfs2? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
