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? 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
