Les Hazlewood-2 wrote > but that's only because no-one has requested it (until now ;)).
because there are so many frameworks, people who evaluate them won't take the time to report to each one why wasn't adopted :). Les Hazlewood-2 wrote > Adding jcl-over-slf4j takes a couple of minutes at most, and this is a > reasonable > alternative (that only has to be done once) compared to the much larger > effort in replicating BeanUtils's PropertyUtils functionality. Unfortunately jcl-over-slf4j doesn't seem to fix the problems in many situations, so many teams simply avoid commons-logging like pest. Of course, it would be nicer if beanutils would ditch this dependency itself, but I'm not sure how realistic would be such and endeavor. Les Hazlewood-2 wrote > Again, I think it would be great to remove the beanutils dependency, but > I'd really like to see some community effort behind this! This is a chicken egg problem: since this is a KO issue, people that might contribute, won't because they can't adopt Shiro. regards. -- View this message in context: http://shiro-user.582556.n2.nabble.com/Ditch-commons-beanutils-tp7579044p7579074.html Sent from the Shiro User mailing list archive at Nabble.com.
