DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4750 jspc flattens directory structure when translating jsp->java Summary: jspc flattens directory structure when translating jsp- >java Product: Ant Version: 1.5 alpha (nightly) Platform: Other OS/Version: Windows NT/2K Status: NEW Severity: Minor Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] so you have this directory tree for the web site, each directory having an index.jsp page set up to act as the default. And you want to use <jspc> to prevalidate or precompile your pages. So you run <jspc> over the tree using an includes="**/*.jsp" pattern :- <jspc destdir="${dir.build}/jspc/java" srcdir="${wardir}" uriroot="${wardir}" verbose="3"> <include name="**/*.jsp"/> </jspc> Only, the task flattens the tree so that all pages get output in the same destination directory: only the last index.java file generated is left around for <javac> to play with. Fixes -documentation; you must use jspc for each directory. ugly but easy -modify the task to replicate the directory heirarchy during the compile phase My preference is for the latter; -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
