[
https://issues.apache.org/jira/browse/VFS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230284#comment-14230284
]
Bernd Eckenfels commented on VFS-438:
-------------------------------------
I think if it is behind a non-automatically enabled profile and build with
that, it might be fine: it wont depend on jcifs, but support using the provider
if it is present in the classpath.
> Please promote vfs-smb currently in the sandbox
> -----------------------------------------------
>
> Key: VFS-438
> URL: https://issues.apache.org/jira/browse/VFS-438
> Project: Commons VFS
> Issue Type: New Feature
> Affects Versions: 2.0
> Environment: windows/unix
> Reporter: Dan Tran
> Fix For: 2.1
>
>
> Current smb provider in the sandbox is mature enough to proceed with
> promotion out of sandbox for general use.
> Detail discussion is here
> http://apache-commons.680414.n4.nabble.com/Promote-vfs-cift-out-of-sandbox-td4636519.html
> The sandbox also tests hookup to current test suite, all we need is to
> provide a external URI using VFS test suite instructions.
> There are currently 2 classloader specific failures
> Tests in error:
> testLoadClass(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests):
> code.ClassToLoad
> testSealing(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests):
> code.sealed.AnotherClass
> Tests run: 1745, Failures: 0, Errors: 2, Skipped: 0
> require cifs 1.3.17 with one line change at
> SmbFileObject.java line number 227 to
> if (e.getNtStatus() == SmbException.NT_STATUS_NO_SUCH_FILE)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
