commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (VFS-438) Please promote vfs-smb currently in the sandbox
Date Tue, 02 Dec 2014 11:24:12 GMT


Sebb commented on VFS-438:

Yes, optional may solve the issue for run-time users of the binary artifacts.
But that is not the only issue here.

The ASF publishes source.
It must be possible for users to download and build the VFS source without pulling in code
that is not AL licensed.
This needs to be the default behaviour.
It is vital that the build does not incorporate non-AL code unless the builder specifically
agrees to it.

> Please promote vfs-smb currently in the sandbox
> -----------------------------------------------
>                 Key: VFS-438
>                 URL:
>             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
> 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 
> line number 227 to 
> if (e.getNtStatus() == SmbException.NT_STATUS_NO_SUCH_FILE)

This message was sent by Atlassian JIRA

View raw message