Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of costin@gmail.com designates
 64.233.162.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Da2eE8bJB4n8UbD7fcTZ306tVa+qR1b9MH0F+5k4j/K4R1QORr16+vkhl7O3ZfROs9NvZnb1u14rMb0Yvntj8jrsZZFRWzlZt8dKaOxZ7p61DL2VDpF+eYKWlszo638EvTnvkv9FkHJiaGBhZ5yFIx6zK00lBp8dPXaCqPyVM8s=
Message-ID: <96e4b5230511060917i72befe4aw69302f9fb6555cdd@mail.gmail.com>
Date: Sun, 6 Nov 2005 09:17:10 -0800
From: Costin Manolache <costin@gmail.com>
Reply-To: costin@apache.org
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: svn commit: r331062 - in /tomcat/sandbox/java/org/apache/coyote:
 ./ adapters/ standalone/
In-Reply-To: <011e01c5e2aa$3caebf10$f8ff6b47@oemcomputer>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20051106031311.12343.qmail@minotaur.apache.org>
	 <00f601c5e287$08b2e010$f8ff6b47@oemcomputer>
	 <96e4b5230511052233t5736914dx8a4fe4aa144aa8c9@mail.gmail.com>
	 <011e01c5e2aa$3caebf10$f8ff6b47@oemcomputer>

My understanding is that tomcat can't _distribute_ code that isn't
apache license compatible,
and  we shouldn't depend on such code to compile or run a functional tomcat=
.

Talking about agendas :-), I think that any code that is not required
to have a working servlet container should be in a separate add-on
module. SSL modules are excelent examples. Actually, a lot of the
things that are in the normal tomcat distro would be make good add-on
modules. Firefox is a good example.


Costin

On 11/6/05, Bill Barker <wbarker@wilshire.com> wrote:
> Actually (having spent way too much time in Gump-land recently :), Tomcat
> depends on rhino in Gump.
>
> What I'm looking for is a clear statement from the Tomcat PMC about MPL
> compatibility.  Sorry about hijacking your commit for my agenda ;-).  It
> looks like Christina can't contribute her code for BZ #36133.  However, i=
t
> looks like a fun project if I can do it myself.
>
> ----- Original Message -----
> From: "Costin Manolache" <costin@gmail.com>
> To: "Tomcat Developers List" <dev@tomcat.apache.org>
> Sent: Saturday, November 05, 2005 10:33 PM
> Subject: Re: svn commit: r331062 - in
> /tomcat/sandbox/java/org/apache/coyote: ./ adapters/ standalone/
>
>
> I think cocoon is also using rhino, and few other projects - ant is
> using it via BSF.
>
> In any case - it is just an example, not required in any way - it's
> easier to do some tests and experiments in a scripting language. The
> build.xml file will just detect if js.jar is available and skip this
> file otherwise ( nothing depends on the JsAdapter ).
>
> Costin
>
> On 11/5/05, Bill Barker <wbarker@wilshire.com> wrote:
> >
> > ----- Original Message -----
> > From: <costin@apache.org>
> > To: <tomcat-dev@jakarta.apache.org>
> > Sent: Saturday, November 05, 2005 7:13 PM
> > Subject: svn commit: r331062 - in /tomcat/sandbox/java/org/apache/coyot=
e:
> > ./
> > adapters/ standalone/
> >
> >
> > > Author: costin
> > > Date: Sat Nov  5 19:13:06 2005
> > > New Revision: 331062
> > >
> > > URL: http://svn.apache.org/viewcvs?rev=3D331062&view=3Drev
> > > Log:
> > > Code for testing ( and using ) coyote standalone.
> > <snip/>
> > > +import org.mozilla.javascript.Context;
> > > +import org.mozilla.javascript.EvaluatorException;
> > > +import org.mozilla.javascript.Function;
> > > +import org.mozilla.javascript.JavaScriptException;
> > > +import org.mozilla.javascript.Scriptable;
> > > +import org.mozilla.javascript.ScriptableObject;
> > > +import org.mozilla.javascript.WrappedException;
> >
> > I take it that MPL is compatible with ASF?  For those that don't want t=
o
> > search the archives, my vote is +1 on this issue.  I just wanted to mak=
e
> > certain that everyone is aware of this, since it is buried in a long
> > commit
> > message.
> >
> >
> >
> > This message is intended only for the use of the person(s) listed above=
 as
> > the intended recipient(s), and may contain information that is PRIVILEG=
ED
> > and CONFIDENTIAL.  If you are not an intended recipient, you may not re=
ad,
> > copy, or distribute this message or any attachment. If you received thi=
s
> > communication in error, please notify us immediately by e-mail and then
> > delete all copies of this message and any attachments.
> >
> > In addition you should be aware that ordinary (unencrypted) e-mail sent
> > through the Internet is not secure. Do not send confidential or sensiti=
ve
> > information, such as social security numbers, account numbers, personal
> > identification numbers and passwords, to us via ordinary (unencrypted)
> > e-mail.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>
>
>
> This message is intended only for the use of the person(s) listed above a=
s the intended recipient(s), and may contain information that is PRIVILEGED=
 and CONFIDENTIAL.  If you are not an intended recipient, you may not read,=
 copy, or distribute this message or any attachment. If you received this c=
ommunication in error, please notify us immediately by e-mail and then dele=
te all copies of this message and any attachments.
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent t=
hrough the Internet is not secure. Do not send confidential or sensitive in=
formation, such as social security numbers, account numbers, personal ident=
ification numbers and passwords, to us via ordinary (unencrypted) e-mail.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org