Would it be a better solution to rather create a CIFS provider outside
of apache-commons (and outside of ASF), which then needs to be
downloaded separately?
The VFS website can have a list of known external providers.
This will remove the onus from commons developers to maintain the CIFS
code and leave no dilemma.
On 24/05/2014 16:19, sebb wrote:
On 23 May 2014 17:59, Dan Tran <[email protected]> wrote:
I think we just need to promote vfs-cifs and mark jcifs optional. That
complies with Apache's policy
ASF policy requires that downstream consumers should not be forced to
use non-compatible depenendencies.
Such dependencies are allowed if the product is still usable without.
ASF policy does not allow us to bundle such a dependency with VFS.
The ASF policy of "no surprises" means that non-compatible
dependencies must not be automatically downloaded either.
The consumer must be made aware that the dependency is not available
under the ALv2.
I suspect it will be necessary to use something other than 'optional'
to achieve that - for example 'provided'.
-D
On Fri, May 23, 2014 at 7:57 AM, Gary Gregory <[email protected]>wrote:
Moved.
Gary
<div>-------- Original message --------</div><div>From: sebb <
[email protected]> </div><div>Date:05/23/2014 10:27 (GMT-05:00)
</div><div>To: Commons Users List <[email protected]>
</div><div>Subject: Re: [vfs] support JCIFS </div><div>
</div>On 23 May 2014 15:24, Gary Gregory <[email protected]> wrote:
Also wondering... why can't we deliver our code even if the jar we depend
in the POM on has an incompatible license? I can understand that it is
undesirable philosophically, but is it disallowed?
Should we create a separate module for these providers? What would it be
called?
This is really a conversation for the dev list ...
Gary
On Fri, May 23, 2014 at 6:57 AM, Bernd Eckenfels <[email protected]
wrote:
I Wonder if we should add the sandbox providers to the normal
providers.xml with a existence condition, so you get it preconfigured as
soon as the JAR is on the classpath.
(i noticed there is some Service discovery plugin stuff in the
StandardfileSystemManager, but I guess this will not pick up the sandbox
Lib?)
Am 23.05.2014 um 06:42 schrieb Gary Gregory <[email protected]>:
It's up to you ;-) is not included in the main project because of the
license IIRC.
Gary
<div>-------- Original message --------</div><div>From: Sandhya
Rajagopalan <[email protected]>
</div><div>Date:05/22/2014
18:30 (GMT-05:00) </div><div>To: [email protected]</div><div>Subject:
[vfs] support JCIFS </div><div>
</div>Hi,
When are you going to support JCIFS? I see this is your sandbox. Can I
add jcifs in providers.xml to start using it?
-Sandhya
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition<
http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Schalk W. Cronjé
@ysb33r
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
