You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/06 15:05:28 UTC
DO NOT REPLY [Bug 31562] New: -
Add excludes parameter to JspC
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31562>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31562
Add excludes parameter to JspC
Summary: Add excludes parameter to JspC
Product: Tomcat 5
Version: 5.0.28
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: andrew.chapman@clicktools.com
The lack of an "excludes" parameter in JspC was a major factor in delaying our
migration to TC 5.0. Our app build relies on being able to exclude certain jsp
files (reusable static include files) which do not compile out of their
intended context. Whilst we could get the app to compile by ignoring the
failures, the resulting web.xml, as well as being twice the size was also full
of incorrect mappings.
I've attached the JspC.java patch I use which adds support for an "excludes"
parameter for consideration.
The "excludes" parameter is an ant style comma separated list of paths
including "*" and "**" wildcards e.g. **/test.jsp,/do_not_include.jsp. This is
parsed and compiled into a org.apache.regexp.RE which is used to determine
whether an individual file is excluded.
All diffs are against the 5.0.28 release code.
It creates a dependency with jakarta-regexp and my nieve patch to the
jasper/build.xml is also attached and patches to jasper/resources files in
English, Spanish and French.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org