Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <40520ED2.2030201@vafer.org>
Date: Fri, 12 Mar 2004 20:26:10 +0100
From: Torsten Curdt <tcurdt@vafer.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20030925
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Using Maven (or something similar) for dependencies? (Was: Co
  coon's Rhino+continuations fork)
References: <31DF72A980E5D511B48C000102BD8685061DB29A@calexc01.diginsite.com>
In-Reply-To: <31DF72A980E5D511B48C000102BD8685061DB29A@calexc01.diginsite.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

> Lets take this to the extreme.  Pretend that Rhino was a GPL license.  Sure
> I could download Rhino and get a running Cocoon.  But I could never sell a
> product based on Cocoon unless I make my customers also download Rhino (and
> I'm not sure even that would be legal).  Since so many parts of Cocoon want
> to leverage Flow these days this would make the situation impossible.   

Well, since you put it to the extreme - you got a point

> And although Rhino isn't GPL, from what I read of the Mozilla license it
> also has the requirement that anything that it is packaged with must also be
> under the Mozilla license, which makes it just as bad as the GPL from a
> commercial standpoint.

I guess the problem is that "packaging with" is a bit blurry.

What are we talking about? What a about a RH CD which
comes with Mozilla, which is under MPL. Does all packages
on the CD have to be under MPL?

I personally don't think downloading-on-demand is
really that bad at all. (If done nicely!) But let's wait
what the board comes up with. It may or may not expose
this discussion being a waste of time ;)
--
Torsten