On 18 July 2012 16:50, Gary Gregory <garydgreg...@gmail.com> wrote: > On Jul 18, 2012, at 9:37, sebb <seb...@gmail.com> wrote: > >> On 18 July 2012 13:28, Gary Gregory <garydgreg...@gmail.com> wrote: >>> On Wed, Jul 18, 2012 at 7:53 AM, sebb <seb...@gmail.com> wrote: >>> >>>> On 18 July 2012 12:49, Gary Gregory <garydgreg...@gmail.com> wrote: >>>>> Ideally: >>>>> >>>>> - Implement the test case such that it starts and stops an embedded Samba >>>>> server, like other tests do (see HTTP, FTP, and so on.) This will require >>>>> using someone's Smb server. >>>>> >>>>> Once that is in place: >>>>> >>>>> - Migrate to the current version of JCIFS. >>>> >>>> JCIFS is LGPL, so is that permissible? >>>> >>> >>> >>> It's not OK to distribute but OK to depend on? >>> >>> "The LGPL v2.1 is ineligible from being a Category B >>> license<http://www.apache.org/legal/3party.html#category-b>(a category >>> that includes the MPL, CPL, EPL, and CDDL) primarily due to the >>> restrictions it places on larger works, violating the third license >>> criterion <http://www.apache.org/legal/3party.html#criterion3>. Therefore, >>> LGPL v2.1-licensed works must not be included in Apache products, although >>> they may be listed as system >>> requirements<http://www.apache.org/legal/3party.html#options-systemrequirements>or >>> distributed elsewhere as optional >>> works <http://www.apache.org/legal/3party.html#options-optional>." from >>> www.apache.org/legal/3party.html >>> >>> Can the above be read as follows for VFS and JCIFS: you cannot copy the >>> JCIFS jar into VFS (which we do not) but the VFS POM can point to it (which >>> we do). >> >> The above document is only proposed, not actual policy. >> >> The following is the resolved list of questions: >> >> http://www.apache.org/legal/resolved.html >> >> In particular: >> >> http://www.apache.org/legal/resolved.html#optional >> >> "Will the majority of users want to use my product without adding the >> optional components? > > I do not see how this helps. It's yes or no: Can the VFS POM point to > a set of artifacts that are LGPL?
Whether the answer is yes or no depends on the answer to the above question. > VFS will not include the artifacts. Good, because that is forbidden. > Gary > >> >> >>> ? >>> >>> Gary >>> >>> >>>>> Then: >>>>> >>>>> - Fill in holes in tests (if any) >>>>> - Fill in holes in features (if any as your needs dictate) >>>>> >>>>> Gary >>>>> >>>>> On Tue, Jul 17, 2012 at 11:12 PM, Dan Tran <dant...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have a forked a copy of vfs-cift to codehaus [1] to test it out. It >>>>>> works so far for me. >>>>>> >>>>>> What would it take to promote the current VFS's CIFT out of sandbox to >>>>>> be released with VFS-2.x? >>>>>> >>>>>> Thanks >>>>>> >>>>>> -Dan >>>>>> >>>>>> [1] https://svn.codehaus.org/mojo/trunk/sandbox/vfs/vfs-smb/ >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>>>> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 >>>>> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK >>>>> Blog: http://garygregory.wordpress.com >>>>> Home: http://garygregory.com/ >>>>> Tweet! http://twitter.com/GaryGregory >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> >>> >>> -- >>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 >>> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
