I have a tomcat instance with a custom lifecycle listener (mule), and a complex application (jira). Mule have several jars as dependencies, and they are loaded by
common.loader. Jira also have a lot of dependencies, the jars are loaded from its
WEB-INF/lib. The only problem is that the versions of the dependencies are different. This produces conflicts when I try to load jira.
I guess these conflicts could be avoided if I could somehow tell tomcat that the mule dependencies should only be loaded for the lifecycle listener.
Is there a way to do that?