Where is the license problem? With JavaSVN or SVN? According to tigris.org, svn is using an apache compatible license.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Tuesday, May 16, 2006 2:47 PM To: Maven Developers List Subject: Fwd: javasvn license FYI seems that we won't be able of having a java implementation of svn. In fact I think we have to remove it from apache ---------- Forwarded message ---------- From: Justin Erenkrantz <[EMAIL PROTECTED]> Date: May 16, 2006 12:28 PM Subject: Re: javasvn license To: Mario Ivankovits <[EMAIL PROTECTED]> Cc: legal-discuss@apache.org On 5/16/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > I would like to know if the JavaSVN license [1] if compatible with ASF > so that I can add it as dependency for the jakarta commons VFS project. No - it's a Category X in Cliff's policy. It requires source distribution of changes (clause 3). -- justin --------------------------------------------------------------------- DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See <http://www.apache.org/licenses/> for official ASF policies and documents. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- 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]
