Hi Mark, Thanks a lot for confirming this. I haven't looked at the source code yet, but I guess if I just use a wild-carded entry for jspFiles e.g.
jspFiles="*.jsp,/pages/*.jsp" it will probably not work, will it ? Kindest Regards, On 11 August 2017 at 16:09, Mark Thomas <ma...@apache.org> wrote: > On 11/08/17 13:57, M. Manna wrote: > > Hello, > > > > i am not sure if Jasper (JSPC) currently supports excluding a list of > JSP > > files using typical <exclude> or <excludes> directive. > > > > Jpsc is a directory based task so it does have pathname include/excudes > but > > i think those are classes and compile classpath options (for jars/libs > > etc.). Could somepone please point me to the right direction? > > > > All I want is to exclude certain JSP files when I am pre-compiling JSPs. > > But I am good when I deploy on tomcat (no need to exclude anything). > > > > I appreciate the help :) > > Hi, > > There is a jspFiles attribute which is a comma separated list of all the > JSPs you want to compile (paths relative to the uriroot). > > That is going to ugly if you have a lot of JSPs to compile and only a > few to exclude. > > A hack would probably to rename the files you don't want to compile to > *.jsp_skip and then rename them back after the jspc task. > > A proper fix would be to patch JspC to do 'proper' include / exclude > support. I've no idea how much work that would be or how much demand > there would be for it. Generally, when pre-compiling folks want to > pre-compile everything. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
