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=7025>. 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=7025 EJBJAR inconsistent behaviour between srcdir and <classpath> Summary: EJBJAR inconsistent behaviour between srcdir and <classpath> Product: Ant Version: 1.5 alpha (nightly) Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The <ejbjar> allows classes for the jar to be specified using the srcdir attribute for the location of the classes put on the jar. But it also allows the usage of a <classpath> to specify additional classes. However, if the classpath references more classes than srcdir and a class is tried to be loaded then the ask complains that it cannot copy the class from the srcdir. In the case of the <weblogic> subelement the task actually fails. This behaviour seem wrong. Either (1)we do not allow a <classpath> other than "srcdir" or (2)the task should be smart enough as to get the class definition out of the jars in the classpath or (3)the task should just use the classpath for verification but it should not complain if the class is not in the srcdir. I think the correct behaviour should be (3). Which means that in such a situation it is upto the user to add the necessary additional jars in the Class-Path of the manifest and in the ear for the application. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
