https://bz.apache.org/bugzilla/show_bug.cgi?id=66191
--- Comment #3 from andreas.sta...@rmcon-int.de --- > Given that the compilation of the tag files is simply a means to an ends > (dependency management) I wonder if there is a simpler solution. We could write a test that scans our tag files to check that no import of a prematurely used class exists. However, the JSP compiler has info what is on the classpath, transitive dependencies etc. Thus, I argue that compilation would be the better solution. When not compiling tag files, errors will always be delayed to later projects. For example, unsupported Java language features (depends on language level configuration) or syntax errors. But yes, this is a minor issue because the error will show up eventually. -- 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
