Oh, .... there were some threads in the past, why you should NOT use <jspc> ... You should use unit tests for your web app (cactus, httpunit...) and use the jsp-compiler of your container.
Jan >-----Ursprüngliche Nachricht----- >Von: Volker Hoss [mailto:[EMAIL PROTECTED] >Gesendet: Montag, 26. Februar 2007 09:49 >An: user@ant.apache.org >Betreff: JSP precompile with taglib files in a jar file > > >Hi, > >I am using the following jspC task call in a WebSphere >build environment to validate the JSP pages: > > <jspc dir="${dir.web}" tempdir="${dir.build}/temp/jspc" >classpath="${output.jar}"/> > >${dir.web} refers to a directory structure >"WebContent\WEB-INF\tlds" where >my >taglib files are located. However my JSP pages also refer to taglibs >located in a jar file and I have >not found a way to specify this file to the jspC task. >classpath parameter >obviously points to an output jar file. >It is not an option to extract the taglib file to the tlds directory. > > >Freundliche Grüsse / Kind Regards >Volker > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
