It is likely the commons-collections one originated in Velocity (or Turbine) or else vice versa. I believe that is the case with a number of such classes.
I have no objections to using the Commons-Collections version and dropping ours eventually, though we should deprecate ours (and perhaps have it extend the other with any necessary api adjustments to keep backwards compatibility) and stop using it internally. Any patch to do this would also have to update the build process for the dep jar to make sure that the Collections' version is included therein. On 9/17/07, Christopher Schultz <[EMAIL PROTECTED]> wrote: > All, > > I answering another poster's question today, I noticed the use of the > velocity.util.ArrayIterator class in Velocity. That seemed like the kind > of class that would be very useful in other collections-oriented code so > I checked, and commons-collections includes such a class. > > Given that commons-collections is already a dependency of Velocity, is > there any reason not to use the commons-collections version of this > class? It appears that the implementation is compatible (and it's so > simple... how could it have not been?). > > Just a thought. > > -chris > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
