As usual, my questions seem to be a bit complicated... ;-) After 4 more hours of debugging I noticed that - when I added a custom module manually, activation worked - however when it was added via Maven dependency (exact same jar), activation failed So I had to assume that there must be additional dependencies which made the difference:
- avalon-framework-4.1.3.jar - commons-beanutils-1.8.0.jar instead of commons-beanutils-1.8.3.jar - commons-lang-2.5.jar instead of commons-lang-2.4.jar - commons-logging-1.1.jar - json-lib-2.4-jdk15.jar instead of json-lib-2.3-jdk15.jar - jsp-api-2.0.jar - log4j-1.2.13.jar instead of log4j-1.2.16.jar - logkit-1.0.1.jar - ognl-2.6.9.jar - poi-scratchpad-3.6.jar instead of poi-scratchpad-3.8.jar - servlet-api-2.4.jar (which should be ignored by Tomcat if I'm not mistaken) So which of these libraries has the potential to break activation the way I described it in the initial post? Thanks! -will -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=6d78c94c-de61-44ac-93ad-50c05d73572e ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
