2011/1/25 Jason van Zyl <ja...@maven.org> > > On Jan 25, 2011, at 11:03 AM, Stephen Connolly wrote: > > > EPL is more restrictive than ASLv2, therefore it is OK for EPL licensed > > projects to consume ASLv2 code... on the other hand it is not so > acceptible > > for ASLv2 licensed projects to consume EPL licensed projects. > > That is completely not true. Read the actual document you linked to. An > Apache project can consume EPL binaries.
Yes and my next sentence hints at that. I was not saying that we cannot consume EPL licensed code, I was putting Ralph's veto into context. > > > There are > > ways for an Apache project to consume and distribute EPL licensed code, > > Yes, it's documented in the link you provided. Correct. The PMC is tasked with ensuring that the project complies with the linked document. The change was only in the dependency and there is a need to assess whether changing the dependency version puts the project in breach of the distribution rules for Apache projects. Also there is the policy that the PMC is working on. All I am doing is putting things into context. If you don't like the context, then you don't like it! > > > however given that the PMC is currently working on the policy for Maven's > > core dependencies, Ralph has decided to temporarily veto any change of a > > dependency in maven-core to a non-Category A license. > > > > My understanding is that once the policy has been approved the veto will > > either be removed, or the policy will make clear what is to be done. > > > > I can appreciate that for somebody who has resigned from the PMC and the > > Apache foundation it may appear that the veto has come out of thin air. > > > > -Stephen > > > > Thanks, > > Jason --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
