I have a custom plugin which references 3rd party jar xmlsec-2.0.1.jar. I have thttps://community.appian.com/discussions/f/plug-ins/6090/i-have-a-custom-plugin-which-references-3rd-party-jar-xmlsec-2-0-1-jar-i-have-tI have a custom plugin which references 3rd party jar xmlsec-2.0.1.jar. I have this jar included in the META-INF/lib directory. When this plugin is executed on Appian 7.10, it uses the xmlsec-1.4.6.jar in ear/suite.ear/lib instead of the one that I includeden-USTelligent Community 12RE: I have a custom plugin which references 3rd party jar xmlsec-2.0.1.jar. I have thttps://community.appian.com/thread/23648?ContentTypeID=1Wed, 14 Oct 2015 02:48:37 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:bac72fd9-50dc-4eb3-9df3-21a89ac4bc3aEduardo FuentesAppian Support will assist you in a ticket.<div style="clear:both;"></div>RE: I have a custom plugin which references 3rd party jar xmlsec-2.0.1.jar. I have thttps://community.appian.com/thread/23643?ContentTypeID=1Wed, 14 Oct 2015 01:41:53 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d534408d-1e36-4c32-9b60-19170113e9bcKTThe conflicting class is not in the Appian jars but in the xmlsec-1.4.6.jar which is included as part of the Appian 7.10 install in the ear/suite.ear/lib directory.<div style="clear:both;"></div>RE: I have a custom plugin which references 3rd party jar xmlsec-2.0.1.jar. I have thttps://community.appian.com/thread/23614?ContentTypeID=1Tue, 13 Oct 2015 02:58:07 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:81fe73e6-edbf-4617-ae6c-ec475c31219eTom RyanYou might be able to get around this by placing the version you want to use before the Appian classpath.jar in the build path order. If you are using Eclipse, you can configure this at Project Properties -&gt; Java Build Path -&gt; Order and Export<div style="clear:both;"></div>