Though commons-collections 3.2 fixes this issue, can dbunit migrate to using commons-collections4 ? A new project that wants to use commons-collections will use the commons-collections4 artficat and not the older one. This causes both the old and the new artifacts to be present in the classpath and causes confusion.