Hi Hans, There aren't any plans to remove commons-beanutils at the moment, but that's only because no-one has requested it (until now ;)).
Please open a Jira feature request. However, unless someone contributes this themselves, it probably won't be a high priority. 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. Again, I think it would be great to remove the beanutils dependency, but I'd really like to see some community effort behind this! Cheers, -- Les Hazlewood | @lhazlewood CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282 On Sun, Aug 18, 2013 at 2:33 PM, hans <[email protected]> wrote: > Are there any plans to ditch commons-beanutils? > > The persisting dependency to this day to commons-logging is worrisome. > To avoid problems, it was removed/prohibited in most projects I had the > chance to work with. > > I know that there's jcl-over-slf4j that might help for some scenarios, but > a > "clean" solution would be preferred. > > http://stackoverflow.com/questions/3939849/commons-beanutils-alternative > > regards. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Ditch-commons-beanutils-tp7579044.html > Sent from the Shiro User mailing list archive at Nabble.com. >
