Hi,

File jstl.jar has been checked in here:
 
http://svn.apache.org/repos/asf/tomcat/servletapi/servlet2.4-jsp2.0-tc5.x/js
r152/examples/WEB-INF/lib/
and here:
 
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/webapps/examples/WEB-IN
F/lib/

This jar is used for running example code in Tomcat.

However it isn't clear to me whether the license for this jar in fact allows
this to be checked in.
The jar has 
  Implementation-Vendor: Sun Microsystems, Inc.
and
  Implementation-Version: 1.1.0-D13

As it happens, the Apache Taglibs project's JSTL also happens to insert 
  Implementation-Vendor: Sun Microsystems, Inc.
in its builds :-(. However as far as I can tell it doesn't generate an
Implementation-Version entry like the above, so presumably this jarfile is
in fact a real Sun jar. If this is indeed the case, then does Apache
actually have the legal right to directly redistribute this jarfile?

The svn commit that added this jar doesn't state where the file was sourced
from:
<quote>
------------------------------------------------------------------------
r267015 | kinman | 2002-10-29 06:45:44 +1300 (Tue, 29 Oct 2002) | 26 lines

- Patch by Jan Leuhe

attached is a patch for the jakarta-servletapi-5 repository including
the following changes:

- TagVariableInfo.java:
  * Removed constructor that takes the name of a fragment.
  * Removed getFragment().
  * Removed private field "fragment".

- JspFragment.java:
  * Removed Map parameter from invoke().

- Updated the "simpletag" and "tagfiles" examples accordingly.

Please notice that the patch also requires adding JSTL to the
examples.war webapp. This is required because this webapp's tag files
need to use JSTL's <c:set> action to set scoped variables before
fragment invocations, now that <jsp:invoke> and <jsp:doBody> no longer
have a nested <jsp:param>.

PR:
Obtained from:
Submitted by:
Reviewed by:
</quote>


Regards,

Simon



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to