Hi All, I want us to decide what we want for 2.0 with the classes BeanUtilsBean2 vs BeanUtilsBean, and ConvertUtilsBean2 vs ConvertUtilsBean.
For your convenience: - https://github.com/apache/commons-beanutils/blob/master/src/main/java/org/apache/commons/beanutils2/BeanUtilsBean2.java - https://github.com/apache/commons-beanutils/blob/master/src/main/java/org/apache/commons/beanutils2/BeanUtilsBean.java - https://github.com/apache/commons-beanutils/blob/master/src/main/java/org/apache/commons/beanutils2/ConvertUtilsBean2.java - https://github.com/apache/commons-beanutils/blob/master/src/main/java/org/apache/commons/beanutils2/ConvertUtilsBean.java I plan on doing a 2.0.0-M1 release in mid-September if we can resolve this and put the new package out in the wild. Possible solutions: 1) Do nothing, keep both classes and explain when to use one vs. the other 2) The "simplest" change is to pull up the "2" classes's method into their respective supertype and adjust the tests to make the "2" behavior the _only_ behavior What needs addressing no matter what IMO is to remove the global variable BeanUtilsBean.BEANS_BY_CLASSLOADER. Even with class loader independence, you can still have multiple libraries and your app competing for setting and using the default. Thoughts? Gary --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
