Summary: | No TLD files were found in tools.jar when tools.jar is explicitly added to $CLASSPATH | ||
---|---|---|---|
Product: | Tomcat 7 | Reporter: | Konstantin Kolinko <knst.kolinko> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | minor | ||
Priority: | P2 | ||
Version: | 7.0.39 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
Konstantin Kolinko
2013-04-02 20:08:28 UTC
Why is tools.jar on the classpath in the first place? I'm very tempted to say that if Eclipse wants to add tools.jar to the classpath then Eclipse should be adding tools.jar to jarsToSkip as well and resolve this as INVALID. That said, Eclipse is widely enough used that adding tools.jar back to the default jarsToSkip is probably the better option. (In reply to comment #1) > Why is tools.jar on the classpath in the first place? I guess they are following some old docs. (Or is there anyone who actually uses JDK compiler with Jasper?) In our Tomcat 8 documentation "tools.jar" is mentioned on two pages, jasper-howto.html windows-service-howto.html (The later one should probably be corrected). > That said, Eclipse is widely enough used that adding tools.jar back to the > default jarsToSkip is probably the better option. Agreed. Fixed in trunk and 7.0.x and will be included in 7.0.40 onwards. |