DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6931>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6931 ejbjar/weblogic classpath element ignored Summary: ejbjar/weblogic classpath element ignored Product: Ant Version: 1.4.1 Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Minor Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In WebLogic 6.1, you get warnings about the home and remote and other classes appearing on the system CLASSPATH if put those classes in the wlclasspath-- that's well documented. Supposedly one should be able to specify a separate <classpath> element alongside <wlclasspath> that supplies these classes and just put the weblogic JAR files in wlclasspath and eliminate these errors, but my experience has been that it is ignored--you have a choice of getting the warnings or of it not working at all. Consulting the source bears this out: there is no place that the -classpath argument to weblogic.ejbc is added to the javaTask object. The wlclasspath eventually ends up as the SYSTEM classpath, as intended: javaTask.setFork(true); if (classpath != null) { javaTask.setClasspath(classpath); } but the generic classpath does not have a corresponding javaTask.createArg().setValue("-classpath"); javaTask.createArg().setLine(classpath); to add the argument to weblogic.ejbc. Also, it seems classpath is overwritten by the value of wlClasspath, so even if that did happen, you'd get the system classpath instead of the <classpath> path value. --kd -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
