FYI - I didn't see this until I tried to package a turbine 5.0 app into
a war and deploy to tomcat... class loader confusion.  Simple patch to
pom.xml in the archetype to exclude the older commons-beanutils-core
from being loaded.

Another incentive to migrate to torque-4.1?

https://github.com/jlpainter/turbine-webapp-5.0/commit/01b9e293cb23997f66353ca146ccf3dcf423a7b5


-- 
Jeff Painter


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to