https://issues.apache.org/bugzilla/show_bug.cgi?id=53012
Bug #: 53012 Summary: Ant Jasper task does not name including file when included file has compile error Product: Tomcat 6 Version: 6.0.35 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: dev@tomcat.apache.org ReportedBy: nicho...@nicholaswilliams.net Classification: Unclassified If fileA.jsp includes fileB.jspf, and the Jasper Ant task attempts to compile fileA.jsp but encounters an error in fileB.jspf, the error it outputs ONLY mentions fileB.jspf. It does not mention fileA.jsp. This can be extremely confusing, especially when fileB.jspf is included by dozens or hundreds of JSPs. The compile error in fileB.jspf may be caused by only one of those files, because it doesn't declare some variable that the rest of the files declare. When Jasper outputs the compile error, it should include a "stacktrace" of sorts, except that it's really an include trace. It shows where the error occurred (fileB.jspf, like it already does), but then which file included that file, and which file included that file, and so on until it gets to the file that the compiler is actually trying to compile (fileA.jsp). Thoughts? I am interested in possibly contributing code for this feature. I will email the developers' list later about it. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org