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=28782>. 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=28782 Antlib & ClassLoading issues in J2EE environment ------- Additional Comments From [EMAIL PROTECTED] 2004-07-18 18:35 ------- Yes, even the patch here is very similar to that in issue 30161. Differences: - 30161's checks isParentFirst - somewhat different API method added to CollectionUtils; 30161's is simpler but 28782's is more powerful for other purposes - 30161's patch checks the case that CL.parent == ACL.parent (but still does not handle the more general problem that ACL.parent might have CL.parent as an ancestor and produce duplicate entries in the enumeration) - 28782's patch does something in Project.java to handle the case where ${java.class.path} is not set to anything relevant; this may be useful, or it may suffice for embedders to set Path.systemClassPath to a different value Neither patch includes a unit test, which may be important since the logic is fairly subtle and could easily be reverted unintentionally by a later commit. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
