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 Mon, 01 Dec 2014 19:38:12 GMT


Sebb commented on VFS-438:

I think optional dependencies are still downloaded automatically.
Try it and see - I think optional just means Maven won't include the jar in transitive dependencies

The point is that there should be no suprises for the user.
UNLESS they explicitly agree otherwise, users should ONLY get AL-licensed software when they
download/use ASF releases.

There are probably many ways this can be achieved.

For example, we may be able to use a 'provided' or 'system' dependency.
This will require a deliberate action by the user to pre-install the jar somewhere.

I'm sure there are other possible solutions.


> 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