DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41594>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41594 ------- Additional Comments From [EMAIL PROTECTED] 2007-02-13 02:42 ------- Well, the setup code is from Tomcat, so it's available to be checked. See http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_9/java/org/apache/jasper/compiler/AntCompiler.java or http://fisheye5.cenqua.com/browse/glassfish/appserv-webtier/src/java/org/apache/jasper/compiler/Compiler.java?r=1.10 for the version in Glassfish v1ur1. As I noted in the bug report in Glassfish, this isn't really a bug in Ant, per se; it's incredibly unlikely that there would be null System properties under normal Ant usage. It's just that when other tools, such as Jasper, use Ant embedded, the rules can change. I used the "enhancement" priority precisely because this wasn't a bug in Ant. If the Tomcat/Glassfish guys are doing something wrong, I'd appreciate it if you can tell them what (or tell me, and I'll tell them). However, throwing an exception in the init method isn't much more helpful than the NullPointerException. (The long stack trace, BTW, is mostly due to the large number of web filters we use, plus the Webwork stack trace. It can be reproduced without all the extra guff) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
