printStackTrace in org.apache.tools.ant.taskdefs.XSLTProcess,

[Steve Loughran <st...@apache.org>]

The IDE is complaining that there's a printStackTrace in the XSLT code.

should we keep this or cut it?

     protected XSLTLiaison getLiaison() {
         // if processor wasn't specified, see if TraX is available.  If 
not,
         // default it to xalan, depending on which is in the classpath
         if (liaison == null) {
             if (processor != null) {
                 try {
                     resolveProcessor(processor);
                 } catch (Exception e) {
                     throw new BuildException(e);
                 }
             } else {
                 try {
                     resolveProcessor(PROCESSOR_TRAX);
                 } catch (Throwable e1) {
                     e1.printStackTrace();
                     throw new BuildException(e1);
                 }
             }
         }
         return liaison;
     }

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org